docs: better docs, mv doxygen to sphinx

[vpp.git] / docs / developer / corefeatures / fib / routes.rst

diff --git a/docs/gettingstarted/developers/fib20/routes.rst b/docs/developer/corefeatures/fib/routes.rst
similarity index 98%
rename from docs/gettingstarted/developers/fib20/routes.rst
rename to docs/developer/corefeatures/fib/routes.rst
index 313a86c..a43cbd1 100644 (file)
--- a/docs/gettingstarted/developers/fib20/routes.rst
+++ b/docs/developer/corefeatures/fib/routes.rst
@@ -97,7 +97,7 @@ The route data is decomposed into three parts; entry, path-list and paths;
       whose next-hop is the all zeros address and describes the only
       peer on the link.
 
-    * Recursive: The path is described only via the next-hop and table-id. 
+    * Recursive: The path is described only via the next-hop and table-id.
 
     * De-aggregate: The path is described only via the special all
       zeros address and a table-id. This implies a subsequent lookup
@@ -127,7 +127,7 @@ the routes also shown. The graph nature of these relationships is evident; child
 are displayed at the top of the diagram, their parents below them. Forward walks are
 thus from top to bottom, back walks bottom to top. The diagram shows the objects
 that are shared, the path-list and adjacency. Sharing objects is critical to fast
-convergence (see section :ref:`fastconvergence`). 
+convergence (see section :ref:`fastconvergence`).
 
 FIB sources
 """""""""""
@@ -148,7 +148,7 @@ The following configuration:
 
 .. code-block:: console
 
-   $ set interface ip address GigabitEthernet0/8/0 192.168.1.1/24 
+   $ set interface ip address GigabitEthernet0/8/0 192.168.1.1/24
 
 results in the addition of two FIB entries; 192.168.1.0/24 which is connected and
 attached, and 192.168.1.1/32 which is connected and local (a.k.a.
@@ -157,7 +157,7 @@ Both prefixes are *interface* sourced. The interface source has a high priority,
 the accidental or nefarious addition of identical prefixes does not prevent the
 router from correctly forwarding. Packets matching a connected prefix will
 generate an ARP request for the packets destination address, this process is known
-as a *glean*. 
+as a *glean*.
 
 An *attached* prefix also results in a glean, but the router does not have its own
 address in that sub-net. The following configuration will result in an attached
@@ -251,8 +251,8 @@ event of a change or update of the cover, and the source can take the necessary
 
 The RR sourced FIB entry becomes the parent of the *fib_path_t* and will contribute its
 forwarding information to that path, so that the child's FIB entry can construct its own
-forwarding information. 
- 
+forwarding information.
+
 Figure 5 shows the object instances created to represent the recursive route and
 its resolving route also shown.
 
@@ -319,7 +319,7 @@ when the forwarding for that prefix changes.
 
 FIB tracking sources a host-prefix entry in the FIB using the 'recusive
 resolution (RR)' source, it exactly the same way that a recursive path
-does. If the entry did not previsouly exist, then the RR source will
+does. If the entry did not previously exist, then the RR source will
 inherit (and track) forwarding from its covering prefix, therefore all
 packets that match this entry are forwarded in the same way as if the
 entry did not exist. The tunnel that is tracking this FIB entry will
@@ -330,7 +330,7 @@ the tunnel.
 
 FIB provides a wrapper to the sourcing of the host-prefix using a
 delegate attached to the entry, and the entry is RR sourced only once.
-. The benefit of this aproach is that each time a new client tracks
+. The benefit of this approach is that each time a new client tracks
 the entry it doesn't RR source it. When an entry is sourced all its
 children are updated. Thus, new clients tracking an entry is
 O(n^2). With the tracker as indirection, the entry is sourced only once.