commit

Author: cfields475

articles/virtual-wan/how-to-configure-route-maps-to-drop-inbound-routes-from-branch-sites.md

@@ -58,7 +58,7 @@ In this scenario, the goal is to drop routes being advertised from VPN branch si
 
    Verify the routes are showing up in the effective route table for hub 1.
 
-   :::image type="content" source="./media/route-maps-how-to-drop/er_before.png" alt-text="Screenshot that shows routes before." lightbox="./media/route-maps-how-to-drop/er_before.png":::   
+   :::image type="content" source="./media/route-maps-how-to-drop/er_before.png" alt-text="Screenshot that shows routes before effective routes." lightbox="./media/route-maps-how-to-drop/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. 
 
@@ -76,7 +76,7 @@ In this scenario, the goal is to drop routes being advertised from VPN branch si
 
    Verify the routes are no longer in the effective route table.
 
-   :::image type="content" source="./media/route-maps-how-to-drop/er_after.png" alt-text="Screenshot that shows routes after applying Route-Map." lightbox="./media/route-maps-how-to-drop/ER_after.png":::
+   :::image type="content" source="./media/route-maps-how-to-drop/er_after.png" alt-text="Screenshot that shows routes after applying Route-Map effective routes." lightbox="./media/route-maps-how-to-drop/ER_after.png":::
 
 ## Next steps
 

articles/virtual-wan/how-to-configure-route-maps-to-prepend-routes.md

@@ -59,7 +59,7 @@ In this scenario, the goal is to prepend route 10.5.0.192/26 from virtual networ
 
    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-how-to-prepend/db_before_two.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-how-to-prepend/db_before_two.png"::: 
+   :::image type="content" source="./media/route-maps-how-to-prepend/db_before_two.png" alt-text="Screenshot that shows the routes before Route-Map VPN." lightbox="./media/route-maps-how-to-prepend/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. 
 
@@ -77,7 +77,7 @@ In this scenario, the goal is to prepend route 10.5.0.192/26 from virtual networ
 
    look at the Route-Map dashboard for VPN branch 2 connection to verify route 10.5.0.192/26 has the ASNs 65533 advertised to VPN branch 2.
 
-   :::image type="content" source="./media/route-maps-how-to-prepend/db_after_two.png" alt-text="Screenshot of routes after Route-map being applied." lightbox="./media/route-maps-how-to-prepend/db_after_two.png":::
+   :::image type="content" source="./media/route-maps-how-to-prepend/db_after_two.png" alt-text="Screenshot of routes after Route-map being applied VPN." lightbox="./media/route-maps-how-to-prepend/db_after_two.png":::
 
 ## Next steps
 

articles/virtual-wan/how-to-configure-route-maps-to-summarize-routes-from-an-device-a-spoke-vNet.md

@@ -47,35 +47,35 @@ Here's the addressing for this environment:
 
 In this scenario, the goal is to summarize some routes being advertised to the hub from the NVA in virtual network 1. In this example we'll be taking the routes 10.150.1.0/24, 10.150.2.0/24, 10.150.3.0/24, 10.150.4.0/24, and summarizing them to 10.150.0.0/16   
 
-   :::image type="content" source="./media/route-maps-how-to-nva/nva.png" alt-text="Screenshot that shows the Scenario." lightbox="route-maps-how-to-nva/nva.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/nva.png" alt-text="Screenshot that shows the Scenario." lightbox="./media/route-maps-how-to-nva/nva.png":::
 
 ## 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.
 
-   :::image type="content" source="./media/route-maps-how-to-nva/db_before_one.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="route-maps-how-to-nva/db_before_one.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/db_before_one.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="./media/route-maps-how-to-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-how-to-nva/db_before_2.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="route-maps-how-to-nva/db_before_2.png":::  
+   :::image type="content" source="./media/route-maps-how-to-nva/db_before_two.png" alt-text="Screenshot that shows the routes before Route-maps on VPN." lightbox="./media/route-maps-how-to-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. 
 
    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-how-to-nva/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="route-maps-how-to-nva/rm.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-how-to-nva/rm.png":::
 
 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-how-to-nva/apply.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-nva/apply.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/apply.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="./media/route-maps-how-to-nva/apply.png":::
 
 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-how-to-nva/db_after_one.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-NVA/db_after_one.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/db_after_one.png" alt-text="Screenshot that shows the Route-map after being applied." lightbox="./media/route-maps-how-to-nva/db_after_one.png":::
 
    Using the Route-Map dashboard verify route 10.150.0.0/16 has been advertised to VPN branch 1
 
-   :::image type="content" source="./media/route-maps-how-to-nva/db_after_two.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-nva/db_after_two.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/db_after_two.png" alt-text="Screenshot that shows the Route-map after being applied VPN." lightbox="./media/route-maps-how-to-nva/db_after_two.png":::
 
 ## Next steps
 

articles/virtual-wan/how-to-configure-route-maps-to-tag-routes.md

@@ -57,7 +57,7 @@ In this scenario, the goal is to tag route 10.5.0.192/26 form virtual network 3
 
    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 very what routes are being sent on prem.
 
-   :::image type="content" source="./media/route-maps-how-to-tag/db_before_2.png" alt-text="Screenshot that shows routes before Route-map." lightbox="./media/route-maps-how-to-tag/db_before_2.png":::   
+   :::image type="content" source="./media/route-maps-how-to-tag/db_before_two.png" alt-text="Screenshot that shows routes before Route-map VPN." lightbox="./media/route-maps-how-to-tag/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. 
 
@@ -75,7 +75,7 @@ In this scenario, the goal is to tag route 10.5.0.192/26 form virtual network 3
 
    look at the Route-Map dashboard for the VPN branch connection to verify route 10.5.0.192/26 has the BGP community 3356:70 being advertised to the VPN branch office 2.  
 
-   :::image type="content" source="./media/route-maps-how-to-Tag/rm_after_two.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-how-to-tag/rm_after_two.png":::
+   :::image type="content" source="./media/route-maps-how-to-Tag/rm_after_two.png" alt-text="Screenshot that shows routes after Route-map being applied VPN." lightbox="./media/route-maps-how-to-tag/rm_after_two.png":::
 
 ## Next steps