doc: clean up a couple snafus in doc changes

Signed-off-by: Quentin Young <qlyoung@nvidia.com>

diff --git a/doc/user/ospf_fundamentals.rst b/doc/user/ospf_fundamentals.rst
index 44312497f0c60f90a21d33179f1dc7b1b679cda4..38c18e5526655b967733b9dd38792e5dfe77be22 100644 (file)
--- a/doc/user/ospf_fundamentals.rst
+++ b/doc/user/ospf_fundamentals.rst
@@ -271,6 +271,7 @@ called `intra-area routes`.
     | Transit        | Link IP address of the :abbr:`DR` | Interface IP address                     |
     +----------------+-----------------------------------+------------------------------------------+
     | Point-to-Point | Router ID of the remote router    | Local interface IP address, or the       |
+    |                |                                   | :abbr:`ifindex (MIB-II interface index)` |
     |                |                                   | for unnumbered links                     |
     +----------------+-----------------------------------+------------------------------------------+
     | Stub           | IP address                        | Subnet Mask                              |

diff --git a/doc/user/pbr.rst b/doc/user/pbr.rst
index 2187c0d735115598695e8b86e7bc31b7ba1876ef..14a05a69d78d6005689fc2542dfe3c34b2238a13 100644 (file)
--- a/doc/user/pbr.rst
+++ b/doc/user/pbr.rst
@@ -255,7 +255,7 @@ causes the policy to be installed into the kernel.
    | name   | Interface name             | String  |
    +--------+----------------------------+---------+
    | index  | Device Index               | Integer |
-   +--------+---------------------------+----------+
+   +--------+----------------------------+---------+
    | policy | PBR map for this interface | String  |
    +--------+----------------------------+---------+
    | valid  | Is the map well-formed?    | Boolean |

diff --git a/doc/user/zebra.rst b/doc/user/zebra.rst
index d9c6eaf4d42a6b6c49f5c2bb9753eacdd6b29cdc..e5cd1de2012cd35d07858581f630240df142627b 100644 (file)
--- a/doc/user/zebra.rst
+++ b/doc/user/zebra.rst
@@ -843,7 +843,7 @@ FPM Commands
    Use the new netlink messages ``RTM_NEWNEXTHOP`` / ``RTM_DELNEXTHOP`` to
    group repeated route next hop information.
 
-   The ``no` form uses the old known FPM behavior of including next hop
+   The ``no`` form uses the old known FPM behavior of including next hop
    information in the route (e.g. ``RTM_NEWROUTE``) messages.
 
 .. clicmd:: show fpm counters [json]