From: Igor Ryzhov <iryzhov@nfware.com>
Date: Mon, 28 Jun 2021 14:49:14 +0000 (+0300)
Subject: doc: remove unnecessary index directives
X-Git-Tag: base_8.1~374^2~1
X-Git-Url: https://git.puffer.fish/?a=commitdiff_plain;h=c9ba467f6840d393aeea246c1e0d8c7ecd2042b5;p=mirror%2Ffrr.git

doc: remove unnecessary index directives

Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
---

diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst
index fab742f539..fe01725b61 100644
--- a/doc/user/bgp.rst
+++ b/doc/user/bgp.rst
@@ -2751,7 +2751,6 @@ route with gateway IP.
 1. CLI to add gateway IP while generating EVPN type-5 route from a BGP IPv4/IPv6
 prefix:
 
-.. index:: advertise <ipv4|ipv6> unicast [gateway-ip]
 .. clicmd:: [no] advertise <ipv4|ipv6> unicast [gateway-ip]
 
 When this CLI is configured for a BGP vrf under L2VPN EVPN address family, EVPN
@@ -2763,7 +2762,6 @@ routes are generated without overlay index.
 
 2. Add gateway IP to EVPN type-5 route using a route-map:
 
-.. index:: set evpn gateway-ip <ipv4|ipv6> <addr>
 .. clicmd:: [no] set evpn gateway-ip <ipv4|ipv6> <addr>
 
 When route-map with above set clause is applied as outbound policy in BGP, it
@@ -2788,7 +2786,6 @@ A PE that receives a type-5 route with gateway IP overlay index should have
 "enable-resolve-overlay-index" configuration enabled to recursively resolve the
 overlay index nexthop and install the prefix into zebra.
 
-.. index:: enable-resolve-overlay-index
 .. clicmd:: [no] enable-resolve-overlay-index
 
 Example configuration:
diff --git a/doc/user/ospf6d.rst b/doc/user/ospf6d.rst
index 1e8c66ab2e..af838cfd60 100644
--- a/doc/user/ospf6d.rst
+++ b/doc/user/ospf6d.rst
@@ -83,7 +83,6 @@ OSPF6 router
 OSPF6 area
 ==========
 
-.. index:: [no] area A.B.C.D nssa
 .. clicmd:: [no] area A.B.C.D nssa
 
 NSSA Support in OSPFv3
diff --git a/doc/user/zebra.rst b/doc/user/zebra.rst
index ee9da63445..3654801100 100644
--- a/doc/user/zebra.rst
+++ b/doc/user/zebra.rst
@@ -647,7 +647,6 @@ FRR's cli or frr.conf or zebra.conf. This section shows how
 to configure SRv6 on FRR. Of course SRv6 can be used as standalone,
 and this section also helps that case.
 
-.. index:: show segment-routing srv6 locator [json]
 .. clicmd:: show segment-routing srv6 locator [json]
 
    This command dump SRv6-locator configured on zebra.  SRv6-locator is used
@@ -666,7 +665,6 @@ and this section also helps that case.
    loc1                       1 2001:db8:1:1::/64        Up
    loc2                       2 2001:db8:2:2::/64        Up
 
-.. index:: show segment-routing srv6 locator NAME detail [json]
 .. clicmd:: show segment-routing srv6 locator NAME detail [json]
 
    As shown in the example, by specifying the name of the locator, you
@@ -696,29 +694,24 @@ and this section also helps that case.
    Chunks:
    - prefix: 2001:db8:2:2::/64, owner: sharp
 
-.. index:: segment-routing
 .. clicmd:: segment-routing
 
    Move from configure mode to segment-routing node.
 
-.. index:: srv6
 .. clicmd:: srv6
 
    Move from segment-routing node to srv6 node.
 
-.. index:: locators
 .. clicmd:: locators
 
    Move from srv6 node to locator node. In this locator node, user can
    configure detailed settings such as the actual srv6 locator.
 
-.. index:: locator NAME
 .. clicmd:: locator NAME
 
    Create a new locator. If the name of an existing locator is specified,
    move to specified locator's configuration node to change the settings it.
 
-.. index:: prefix X:X::X:X/M [function-bits-length 32]
 .. clicmd:: prefix X:X::X:X/M [function-bits-length 32]
 
    Set the ipv6 prefix block of the locator. SRv6 locator is defined by