screenshot reduction

Author: halkazwini

articles/route-server/configure-route-server.md

@@ -72,7 +72,7 @@ In this section, you learn how to add a BGP peering to your route server to peer
 
     Once the peer NVA is successfully added, you can see it in the list of peers with a **Succeeded** provisioning state.
 
-    :::image type="content" source="./media/configure-route-server/peer-list.png" alt-text="Screenshot that shows the route server's peers." lightbox="./media/configure-route-server/peer-list.png":::
+    :::image type="content" source="./media/peer-list.png" alt-text="Screenshot that shows the route server's peers." lightbox="./media/peer-list.png":::
 
     To complete the peering setup, you must configure the NVA to establish a BGP session with the route server's peer IPs and ASN. You can find the route server's Peer IPs and ASN in the **Overview** page:
 

articles/route-server/media/configure-route-server/peer-list.png renamed to articles/route-server/media/peer-list.png

@@ -209,7 +209,7 @@ In this section, you configure BGP settings on the VM so it acts as an NVA and c
 
 1. Once you add the NVA as a peer, the **Peers** page shows the **myNVA** as a peer:
 
-    :::image type="content" source="./media/peer-route-server-with-virtual-appliance/route-server-peers.png" alt-text="Screenshot that shows the peers of a Route Server." lightbox="./media/peer-route-server-with-virtual-appliance/route-server-peers.png":::
+    :::image type="content" source="./media/peer-list.png" alt-text="Screenshot that shows the peers of a Route Server." lightbox="./media/peer-list.png":::
 
  > [!NOTE]
  > - Azure Route Server supports BGP peering with NVAs that are deployed in the same VNet or a directly peered VNet. Configuring BGP peering between an on-premises NVA and Azure Route Server is not supported.