# HG changeset patch
# User Nick <nick@somerandomnick.ano>
# Date 1301670549 0
# Node ID 3672ac7dae881d28d2a59ca13a028521af65d042
# Parent  70ad1bedb1dda20c0e64092af386fa5f231d5872# Parent  3a26ef01c0fb404db6c89c9f9cabedad33725b06
Merge commit 'a9174299de600bba04763487767b821a638ea184'

diff -r 70ad1bedb1dd -r 3672ac7dae88 doc/ucis.ano/bgp_graph/readme.txt
--- a/doc/ucis.ano/bgp_graph/readme.txt	Thu Mar 31 03:48:51 2011 +0200
+++ b/doc/ucis.ano/bgp_graph/readme.txt	Fri Apr 01 15:09:09 2011 +0000
@@ -3,7 +3,7 @@
 Some of the scripts will communicate with the BGP software, another script can be used to export the obtained information to a .dot file, which can then be converted to a graph file using graphviz. The scripts can run on different machines, and it is recommended to use routing information from multiple routes, to obtain an accurate view of the network.
 
 Depending on the BGP software, one of the following scripts must be used to acquire the data:
-- bgp_path_list_birg.sh (or .php) for the bird routing daemon
+- bgp_path_list_bird.sh (or .php) for the bird routing daemon
 - bgp_path_list_quagga.sh (or .php) for the quagga/zebra routing daemon
 - bgp_path_list_xml.php to convert existing dn42/diac42 .xml data
 
@@ -43,4 +43,4 @@
 You can also use inetd/xinetd on the server side for a more permanent solution.
 
 
-Be creative!
\ No newline at end of file
+Be creative!