doc: pim evpn tabs -> spaces

And remove `interface` highlight directive

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

1 files changed, 11 insertions, 14 deletions

diff --git a/doc/user/pim.rst b/doc/user/pim.rst
index 8686d063e..5148d3baf 100644
--- a/doc/user/pim.rst
+++ b/doc/user/pim.rst
@@ -506,28 +506,25 @@ Clear commands reset various variables.
 
 PIM EVPN configuration
 ======================
-To use PIM in the underlay for overlay BUM forwarding associate a
-multicast group with the L2 VNI. The actual configuration is based
-on your distribution. Here is an ifupdown2 example -
-
-.. code-block:: interface
+To use PIM in the underlay for overlay BUM forwarding associate a multicast
+group with the L2 VNI. The actual configuration is based on your distribution.
+Here is an ifupdown2 example::
 
    auto vx-10100
    iface vx-10100
-	vxlan-id 10100
-	bridge-access 100
-	vxlan-local-tunnelip 27.0.0.11
-	vxlan-mcastgrp 239.1.1.100
-
+       vxlan-id 10100
+       bridge-access 100
+       vxlan-local-tunnelip 27.0.0.11
+       vxlan-mcastgrp 239.1.1.100
 
 .. note::
 
-   PIM will see the ``vxlan-mcastgrp`` configuration and auto configure
-   state to properly forward BUM traffic.
+   PIM will see the ``vxlan-mcastgrp`` configuration and auto configure state
+   to properly forward BUM traffic.
 
+PIM also needs to be configured in the underlay to allow the BUM MDT to be
+setup. This is existing PIM configuration:
 
-PIM also needs to be configured in the underlay to allow the BUM MDT to
-be setup. This is existing PIM configuration -
 - Enable pim on the underlay L3 interface via the "ip pim" command.
 - Configure RPs for the BUM multicast group range.
 - Ensure the PIM is enabled on the lo of the VTEPs and the RP.