# HG changeset patch
# User Nick <nick@somerandomnick.ano>
# Date 1301850784 0
# Node ID 819fe00acc10578c55ffcde5c503c2176733dc07
# Parent  3672ac7dae881d28d2a59ca13a028521af65d042# Parent  c55ba2def77e9dfdb2010cda39c8b0cd999d2500
Merge commit '2d2ae16579f8cddc20ce151b410501ad5af8beee'

diff -r c55ba2def77e -r 819fe00acc10 doc/ucis.ano/bgp_graph/readme.txt
--- a/doc/ucis.ano/bgp_graph/readme.txt	Sat Apr 02 08:22:07 2011 +0200
+++ b/doc/ucis.ano/bgp_graph/readme.txt	Sun Apr 03 17:13:04 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!