docs: better docs, mv doxygen to sphinx

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

diff --git a/docs/gettingstarted/developers/fib20/neighbors.rst b/docs/developer/corefeatures/fib/neighbors.rst
similarity index 97%
rename from docs/gettingstarted/developers/fib20/neighbors.rst
rename to docs/developer/corefeatures/fib/neighbors.rst
index f460955..13a3f07 100644 (file)
--- a/docs/gettingstarted/developers/fib20/neighbors.rst
+++ b/docs/developer/corefeatures/fib/neighbors.rst
@@ -10,7 +10,7 @@ Figure 1: Neighbour data model
 Figure 1 shows the data model for IP neighbours. An IP neighbour contains the mapping
 between a peer, identified by an IPv4 or IPv6 address, and its MAC address on a given
 interface. An IP-table (VRF) is not part of the neighbour's
-data/identity. This is because the virtualisation of a router into
+data/identity. This is because the virtualization of a router into
 different tables (VRFs) is performed at the interface level, i.e. an
 IP-table is bound to a particular interface. A neighbour, which is
 attached to an interface, is thus implicitly in that table, and
@@ -69,7 +69,7 @@ have an associated interface and are terminal. The [sub] sub-types are:
 
 * A Glean Adjacency (key={interface}). This is a representation of the need to discover
   a peer on the given interface. It is used when it is known that the
-  packet is destined to an undiscoverd peer on that interface. The
+  packet is destined to an undiscovered peer on that interface. The
   difference between the glean adjacency and an
   incomplete neighbour adjacency is that in the forwarding path the
   glean adjacency will construct an ARP/ND request for the peer as