commit

Author: cfields475

articles/virtual-wan/route-maps-drop-inbound-branch-sites.md

@@ -52,25 +52,25 @@ In this scenario, the goal is to drop routes being advertised from VPN branch si
 
 ## Workflow
 
-1.  Use the Route-Map dashboard in hub 1 to verify what routes are being advertised from the VPN branch. 
+   1.  Use the Route-Map dashboard in hub 1 to verify what routes are being advertised from the VPN branch. 
 
    :::image type="content" source="./media/route-maps-drop-inbound-branch-sites/db-before.png" alt-text="Screenshot that shows routes before Route-maps." lightbox="./media/route-maps-drop-inbound-branch-sites/db-before.png"::: 
 
    Verify the routes are showing up in the effective route table for hub 1.
 
    :::image type="content" source="./media/route-maps-drop-inbound-branch-sites/er-before.png" alt-text="Screenshot that shows routes in effective routes table." lightbox="./media/route-maps-drop-inbound-branch-sites/er-before.png":::  
 
-2. Create a Route-Map to drop the routes. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
+   2. Create a Route-Map to drop the routes. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
 
    The Route-Map will have a match rule for route 10.122.2.0/16. The action **Drop** is selected. 
 
    :::image type="content" source="./media/route-maps-drop-inbound-branch-sites/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-drop-inbound-branch-sites/rm.png":::
 
-3. Apply the Route-Map on the VPN branch 1 site connection. The Route-Map will be applied in the inbound direction. 
+   3. Apply the Route-Map on the VPN branch 1 site connection. The Route-Map will be applied in the inbound direction. 
 
    :::image type="content" source="./media/route-maps-drop-inbound-branch-sites/apply.png" alt-text="Screenshot showing the Route-Map being applied." lightbox="./media/route-maps-drop-inbound-branch-sites/apply.png":::
 
-4. Using the Route-Map dashboard in Hub 1, Verify that routes 10.122.1.0/24,10.122.2.0/24, 10.122.3.0/24 are being dropped.   
+   4. Using the Route-Map dashboard in Hub 1, Verify that routes 10.122.1.0/24,10.122.2.0/24, 10.122.3.0/24 are being dropped.   
 
    :::image type="content" source="./media/route-maps-drop-inbound-branch-sites/db-after.png" alt-text="Screenshot showing routes after the Route-Map being applied." lightbox="./media/route-maps-drop-inbound-branch-sites/db-after.png":::
 

articles/virtual-wan/route-maps-how-to-summarize-routes-leaving-your-virtual-wan.md

@@ -52,21 +52,21 @@ In this scenario, a Route-map will summarize the routes being advertised to the
 
 ## Workflow
 
-1. Use the Route-map dashboard in hub 2 to verify the correct routes are currently being advertised to VPN branch 2 site.
+   1. Use the Route-map dashboard in hub 2 to verify the correct routes are currently being advertised to VPN branch 2 site.
 
    :::image type="content" source="./media/route-maps-how-to-summarize/db-one.png" alt-text="Screenshot that shows routes before Route-Maps." lightbox="./media/route-maps-how-to-summarize/db-one.png"::: 
 
-2. Create a Route-map to summarize the routes. Before you create your first time Route-map, see [How to configure Route-maps](route-maps-how-to.md) for more information.
+   2. Create a Route-map to summarize the routes. Before you create your first time Route-map, see [How to configure Route-maps](route-maps-how-to.md) for more information.
 
    The Route-map has a match rule for contains 10.122.0.0/16. The action **Modify** is selected. Route Modification has a **Replace** for the **RoutePrefix** 10.122.0.0/16.
 
    :::image type="content" source="./media/route-maps-how-to-summarize/rm.png" alt-text="Screenshot to show the Route-Map." lightbox="./media/route-maps-how-to-summarize/rm.png":::
 
-3. Apply the Route-map on the VPN branch 2 site connection. The Route-map will be applied in the outbound direction.
+   3. Apply the Route-map on the VPN branch 2 site connection. The Route-map will be applied in the outbound direction.
 
    :::image type="content" source="./media/route-maps-how-to-summarize/apply.png" alt-text="Screenshot to show the Route-Map being applied." lightbox="./media/route-maps-how-to-summarize/apply.png":::
 
-4. Using the Route-map dashboard in Hub 2, Verify that route 10.122.0.0/16 is being summarized.  
+   4. Using the Route-map dashboard in Hub 2, Verify that route 10.122.0.0/16 is being summarized.  
 
    :::image type="content" source="./media/route-maps-how-to-summarize/db-after.png" alt-text="Screenshot to show routes after Route-map was applied." lightbox="./media/route-maps-how-to-summarize/db-after.png":::
 

articles/virtual-wan/route-maps-prepend-routes.md

@@ -53,25 +53,25 @@ In this scenario, the goal is to prepend route 10.5.0.192/26 from virtual networ
 
 ## Workflow
 
-1.  Use the Route-Map dashboard in hub 2 to verify the ASNs on routes are being advertised from the virtual network connection. 
+   1.  Use the Route-Map dashboard in hub 2 to verify the ASNs on routes are being advertised from the virtual network connection. 
 
    :::image type="content" source="./media/route-maps-prepend-routes/db-before-one.png" alt-text="Screenshot that shows the routes before Route-Map being applied." lightbox="./media/route-maps-prepend-routes/db-before-one.png":::
 
    Look at the Route-Map dashboard for the VPN branch 2 to verify the ASNs for route 10.5.0.192/26 that are being sent to the branch office. 
 
    :::image type="content" source="./media/route-maps-prepend-routes/db-before-two.png" alt-text="Screenshot that shows the routes before Route-Map being applied to the VPN branch." lightbox="./media/route-maps-prepend-routes/db-before-two.png"::: 
 
-2. Create a Route-Map to tag the route. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
+   2. Create a Route-Map to tag the route. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
 
    The Route-Map will have a match rule for route 10.5.0.192/26. The action **modify** will be selected. Route Modification has a **Prepend** for **AS Path** 65533.  
 
    :::image type="content" source="./media/route-maps-prepend-routes/rm.png" alt-text="Screenshot that shows the Route-Map." lightbox="./media/route-maps-prepend-routes/rm.png":::
 
-3. Apply the Route-Map on the virtual network 3 connection. The Route-Map will be applied in the inbound direction. 
+   3. Apply the Route-Map on the virtual network 3 connection. The Route-Map will be applied in the inbound direction. 
 
    :::image type="content" source="./media/route-maps-prepend-routes/apply.png" alt-text="Screenshot of the Route-map being applied." lightbox="./media/route-maps-prepend-routes/apply.png":::
 
-4. Using the Route-Map dashboard in Hub 2, Verify that route 10.5.0.192/26 has an ASN of 65533 added.    
+   4. Using the Route-Map dashboard in Hub 2, Verify that route 10.5.0.192/26 has an ASN of 65533 added.    
 
    :::image type="content" source="./media/route-maps-prepend-routes/db-after-one.png" alt-text="Screenshot showing routes after Route-map was applied." lightbox="./media/route-maps-prepend-routes/db-after-one.png":::
 

articles/virtual-wan/route-maps-summarize-from-device-spoke-vnet-nva.md

@@ -51,25 +51,25 @@ In this scenario, the goal is to summarize some routes being advertised to the h
 
 ## Workflow
 
-1.  Use the Route-Map dashboard in hub 1 to verify the correct routes are currently being advertised from virtual network 1 to the hub.
+   1.  Use the Route-Map dashboard in hub 1 to verify the correct routes are currently being advertised from virtual network 1 to the hub.
 
    :::image type="content" source="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-before-one.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-before-one.png":::
 
    Use the Route-Map dashboard to verify the routes being sent to VPN branch 1.  
 
    :::image type="content" source="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-before-two.png" alt-text="Screenshot that shows the routes before Route-maps for VPN branch." lightbox="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-before-two.png":::  
 
-2. Create a Route-Map to tag the route. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
+   2. Create a Route-Map to tag the route. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
 
    The Route-Map will have a match rule for route 10.150.0.0/16. The action **modify** will be selected. Route Modification has an **Replace** for **RoutePrefix** 10.150.0.0/16.  
 
    :::image type="content" source="./media/route-maps-summarize-from-device-spoke-vnet-nva/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-summarize-from-device-spoke-vnet-nva/rm.png":::
 
-3. Apply the Route-Map on the virtual network 1 connection. The Route-Map will be applied in the inbound direction. 
+   3. Apply the Route-Map on the virtual network 1 connection. The Route-Map will be applied in the inbound direction. 
 
    :::image type="content" source="./media/route-maps-summarize-from-device-spoke-vnet-nva/apply.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="./media/route-maps-summarize-from-device-spoke-vnet-nva/apply.png":::
 
-4. Using the Route-Map dashboard in Hub 1, Verify that route 10.150.0.0/16 is being summarized.    
+   4. Using the Route-Map dashboard in Hub 1, Verify that route 10.150.0.0/16 is being summarized.    
 
    :::image type="content" source="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-after-one.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-summarize-from-device-spoke-vnet-nva/db-after-one.png":::
 

articles/virtual-wan/route-maps-tag-routes.md

@@ -51,25 +51,25 @@ In this scenario, the goal is to tag route 10.5.0.192/26 form virtual network 3
 
 ## Workflow
 
-1. Use the Route-Map dashboard in hub 2 to verify the BGP community on the route 10.5.0.192/26 being advertised from the virtual network connection.
+   1. Use the Route-Map dashboard in hub 2 to verify the BGP community on the route 10.5.0.192/26 being advertised from the virtual network connection.
 
    :::image type="content" source="./media/route-maps-tag-routes/db-before.png" alt-text="Screenshot that shows routes before Route-map." lightbox="./media/route-maps-tag-routes/db-before.png"::: 
 
    look at the Route-Map dashboard for the VPN Brach to verify the BGP community on the route for 10.5.0.192/26. The goal is to vary what routes are being sent on premises.
 
    :::image type="content" source="./media/route-maps-tag-routes/db-before-two.png" alt-text="Screenshot that shows routes for VPN branch." lightbox="./media/route-maps-tag-routes/db-before-two.png":::   
 
-2. Create a Route-Map to tag the route. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
+   2. Create a Route-Map to tag the route. If this is your first time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
 
    The Route-Map will have a match rule for route 10.5.0.192/26. The action **modify** will be selected. Route Modification has an **add** for **community** 3356:70.  
 
    :::image type="content" source="./media/route-maps-tag-routes/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-tag-routes/rm.png":::
 
-3. Apply the Route-Map on the virtual network 3 connection. The Route-Map will be applied in the inbound direction. 
+   3. Apply the Route-Map on the virtual network 3 connection. The Route-Map will be applied in the inbound direction. 
 
    :::image type="content" source="./media/route-maps-tag-routes/apply.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="./media/route-maps-tag-routes/apply.png":::
 
-4. Using the Route-Map dashboard in Hub 2, Verify that route 10.5.0.192/26 has the BGP community of 3356:70 added on the virtual network 3 connection.    
+   4. Using the Route-Map dashboard in Hub 2, Verify that route 10.5.0.192/26 has the BGP community of 3356:70 added on the virtual network 3 connection.    
 
    :::image type="content" source="./media/route-maps-tag-routes/db-after.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-tag-routes/db-after.png":::