Fixing enumeration in L3VPN use case section

Change-Id: Ib2b6637ee8fac733dadc9bdd1f0f7c42faf8208e
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>

1 files changed, 27 insertions, 9 deletions

diff --git a/docs/requirements/use_cases/use_cases_l3vpn.rst b/docs/requirements/use_cases/use_cases_l3vpn.rst
index 93f3d80..ad11bbb 100644
--- a/docs/requirements/use_cases/use_cases_l3vpn.rst
+++ b/docs/requirements/use_cases/use_cases_l3vpn.rst
@@ -44,18 +44,30 @@ In L3VPN Red, VM G5 (10.1.1.5) is spawned on host A, and attached to subnet 10.1
 Exemplary workflow is described as follows:
 
 1. Create Network
+
 2. Create Network VRF Policy Resource ``Any-to-Any``
-2.1. This sets up that when this tenant is put on a HOST that:
-2.1.1. There will be a RD assigned per VRF
-2.1.2. There will be a RT used for the common any-to-any communication
+
+  2.1. This sets up that when this tenant is put on a HOST that:
+
+    2.1.1. There will be a RD assigned per VRF
+
+    2.1.2. There will be a RT used for the common any-to-any communication
+
 3. Create Subnet
+
 4. Create Port (subnet, network vrf policy resource). This causes controller to:
-4.1. Create vrf in vRouter's FIB, or Update vrf if already exists
-4.2. Install an entry for Guest's HOST-Route in FIBs of Vrouters serving this tenant Virtual Network
-4.3. Announce Guest HOST-Route to WAN-GW via MP-BGP
+
+  4.1. Create vrf in vRouter's FIB, or Update vrf if already exists
+
+  4.2. Install an entry for Guest's HOST-Route in FIBs of Vrouters serving this tenant Virtual Network
+
+  4.3. Announce Guest HOST-Route to WAN-GW via MP-BGP
+
 
 VRF Lets us do:
+
 1. Overlapping Addresses
+
 2. Segregation of Traffic
 
 Derrived Requirements
@@ -177,12 +189,18 @@ Exemplary VNF1(S) Spoke VRF is as follows:
 Exemplary workflow is described as follows:
 
 1. Create Network
+
 2. Create VRF Policy Resource
-2.1. Hub and Spoke
+
+  2.1. Hub and Spoke
+
 3. Create Subnet
+
 4. Create Port
-4.1. Subnet
-4.2. VRF Policy Resource, [H | S]
+
+  4.1. Subnet
+
+  4.2. VRF Policy Resource, [H | S]
 
 
 Derrived Requirements