2003-08-12 Paul Jakma <paul@dishone.st>

	* doc/: GNU Zebra -> Quagga, in most places. Update Url and list URL
	  to quagga.net. zebra.texi -> quagga.texi.

1 files changed, 9 insertions, 9 deletions

diff --git a/doc/ripd.texi b/doc/ripd.texi
index 2257ec16..060b2474 100644
--- a/doc/ripd.texi
+++ b/doc/ripd.texi
@@ -1,5 +1,5 @@
 @c -*-texinfo-*-
-@c This is part of the GNU Zebra Manual.
+@c This is part of the Quagga Manual.
 @c Copyright (C) 1999, 2000 Kunihiro Ishiguro
 @c See file zebra.texi for copying conditions.
 @node RIP
@@ -99,7 +99,7 @@ to the packet on the basis of the interface that received the packet.
 Version 2 of RIP supports a variable length subnet mask (VLSM).  By
 extending the subnet mask, the mask can be divided and reused.  Each
 subnet can be used for different purposes such as large to middle size
-LANs and WAN links.  Zebra @command{ripd} does not support the non-sequential
+LANs and WAN links.  Quagga @command{ripd} does not support the non-sequential
 netmasks that are included in RIP Version 2.
 
 In a case of similar information with the same prefix and metric, the
@@ -277,10 +277,10 @@ If you want to specify RIP only static routes:
 
 @deffn {RIP command} {route @var{a.b.c.d/m}} {}
 @deffnx {RIP command} {no route @var{a.b.c.d/m}} {}
-This command is specific to Zebra.  The @code{route} command makes a static
+This command is specific to Quagga.  The @code{route} command makes a static
 route only inside RIP. This command should be used only by advanced
 users who are particularly knowledgeable about the RIP protocol.  In
-most cases, we recommend creating a static route in Zebra and
+most cases, we recommend creating a static route in Quagga and
 redistributing it in RIP using @code{redistribute static}.
 @end deffn
 
@@ -386,11 +386,11 @@ redistribute connected [route-map MAP_NAME]
 .....
 @end example
 
-Cisco applies route-map _before_ routes will exported to rip route
-table.  In current Zebra's test implementation, @command{ripd} applies route-map
-after routes are listed in the route table and before routes will be announced
-to an interface (something like output filter). I think it is not so clear,
-but it is draft and it may be changed at future.
+Cisco applies route-map _before_ routes will exported to rip route table. 
+In current Quagga's test implementation, @command{ripd} applies route-map
+after routes are listed in the route table and before routes will be
+announced to an interface (something like output filter). I think it is not
+so clear, but it is draft and it may be changed at future.
 
 Route-map statement (@pxref{Route Map}) is needed to use route-map
 functionality.