update diagram and instructions

Author: halkazwini

articles/route-server/quickstart-create-route-server-powershell.md

@@ -5,15 +5,15 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: azure-route-server
 ms.topic: quickstart
-ms.date: 02/10/2025
+ms.date: 02/26/2025
 ms.custom: devx-track-azurepowershell, mode-api
 ---
 
 # Quickstart: Create an Azure Route Server using PowerShell
 
 In this quickstart, you learn how to create an Azure Route Server to peer with a network virtual appliance (NVA) in your virtual network using Azure PowerShell.
 
-:::image type="content" source="./media/environment-diagram.png" alt-text="Diagram of Route Server deployment environment using the Azure PowerShell.":::
+:::image type="content" source="./media/route-server-diagram.png" alt-text="Diagram of Route Server deployment environment using the Azure PowerShell.":::
 
 [!INCLUDE [route server preview note](../../includes/route-server-note-preview-date.md)]
 
@@ -33,11 +33,11 @@ In this quickstart, you learn how to create an Azure Route Server to peer with a
 
 In this section, you create a route server. Prior to creating the route server, create a resource group to host all resources including the route server. You'll also need to create a virtual network with a dedicated subnet for the route server.
 
-1. Create a resource group using [New-AzResourceGroup](/powershell/module/az.Resources/New-azResourceGroup) cmdlet. The following example creates a resource group named **RouteServerRG** in the **WestUS** region:
+1. Create a resource group using [New-AzResourceGroup](/powershell/module/az.Resources/New-azResourceGroup) cmdlet. The following example creates a resource group named **myResourceGroup** in the **EastUS** region:
 
     ```azurepowershell-interactive
     # Create a resource group.
-    New-AzResourceGroup = -Name 'RouteServerRG' -Location 'WestUS'
+    New-AzResourceGroup = -Name 'myResourceGroup' -Location 'EastUS'
     ```
 
 1. The route server requires a dedicated subnet named *RouteServerSubnet*. Please configure a subnet size of minimum /26 or larger. Create a subnet configuration for **RouteServerSubnet** using [New-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/new-azvirtualnetworksubnetconfig) cmdlet.
@@ -47,11 +47,11 @@ In this section, you create a route server. Prior to creating the route server,
     $subnet = New-AzVirtualNetworkSubnetConfig -Name 'RouteServerSubnet' -AddressPrefix '10.0.1.0/26'
     ```
 
-1. Create a virtual network using [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork) cmdlet. The following example creates a default virtual network named **myRouteServerVNet** in the **WestUS** region.
+1. Create a virtual network using [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork) cmdlet. The following example creates a default virtual network named **myVirtualNetwork** in the **EastUS** region.
 
     ```azurepowershell-interactive
     # Create a virtual network and place into a variable.
-    $vnet = New-AzVirtualNetwork -Name 'myRouteServerVNet' -ResourceGroupName 'RouteServerRG' -Location 'WestUS' -AddressPrefix '10.0.0.0/16' -Subnet $subnet
+    $vnet = New-AzVirtualNetwork -Name 'myVirtualNetwork' -ResourceGroupName 'myResourceGroup' -Location 'EastUS' -AddressPrefix '10.0.0.0/16' -Subnet $subnet
     # Place the subnet ID into a variable.
     $subnetId = (Get-AzVirtualNetworkSubnetConfig -Name 'RouteServerSubnet' -VirtualNetwork $vnet).Id
     ```
@@ -60,14 +60,14 @@ In this section, you create a route server. Prior to creating the route server,
 
     ```azurepowershell-interactive
     # Create a Standard public IP and place it into a variable.
-    $publicIp = New-AzPublicIpAddress -ResourceGroupName 'RouteServerRG' -Name 'myRouteServerIP' -Location 'WestUS' -AllocationMethod 'Static' -Sku 'Standard' -IpAddressVersion 'Ipv4'
+    $publicIp = New-AzPublicIpAddress -ResourceGroupName 'myResourceGroup' -Name 'myRouteServerIP' -Location 'EastUS' -AllocationMethod 'Static' -Sku 'Standard' -IpAddressVersion 'Ipv4'
     ```
 
-1. Create the route server using [New-AzRouteServer](/powershell/module/az.network/new-azrouteserver) cmdlet. The following example creates a route server named **myRouteServer** in the **WestUS** region. The *HostedSubnet* is the resource ID of the RouteServerSubnet created in the previous steps.
+1. Create the route server using [New-AzRouteServer](/powershell/module/az.network/new-azrouteserver) cmdlet. The following example creates a route server named **myRouteServer** in the **EastUS** region. The *HostedSubnet* is the resource ID of the RouteServerSubnet created in the previous steps.
 
     ```azurepowershell-interactive
     # Create the route server.
-    New-AzRouteServer -RouteServerName 'myRouteServer' -ResourceGroupName 'RouteServerRG' -Location 'WestUS' -HostedSubnet $subnetId -PublicIP $publicIp
+    New-AzRouteServer -RouteServerName 'myRouteServer' -ResourceGroupName 'myResourceGroup' -Location 'EastUS' -HostedSubnet $subnetId -PublicIP $publicIp
     ```
 
     [!INCLUDE [Deployment note](../../includes/route-server-note-creation-time.md)]
@@ -78,7 +78,7 @@ In this section, you learn how to configure BGP peering with a network virtual a
 
 ```azurepowershell-interactive
 # Add a peer.
-Add-AzRouteServerPeer -ResourceGroupName 'RouteServerRG' -RouteServerName 'myRouteServer' -PeerName 'myNVA' -PeerAsn '65001' -PeerIp '10.0.0.4'
+Add-AzRouteServerPeer -ResourceGroupName 'myResourceGroup' -RouteServerName 'myRouteServer' -PeerName 'myNVA' -PeerAsn '65001' -PeerIp '10.0.0.4'
 ```
 
 ## Complete the configuration on the NVA
@@ -87,15 +87,15 @@ To complete the peering setup, you must configure the NVA to establish a BGP ses
 
 ```azurepowershell-interactive
 # Get the route server details.
-Get-AzRouteServer -ResourceGroupName 'RouteServerRG' -RouteServerName 'myRouteServer'
+Get-AzRouteServer -ResourceGroupName 'myResourceGroup' -RouteServerName 'myRouteServer'
 ```
 
 The output should look similar to the following example:
 
 ```output
 ResourceGroupName Name          Location RouteServerAsn RouteServerIps       ProvisioningState HubRoutingPreference AllowBranchToBranchTraffic
 ----------------- ----          -------- -------------- --------------       ----------------- -------------------- --------------------------
-RouteServerRG     myRouteServer westus   65515          {10.0.1.4, 10.0.1.5} Succeeded         ExpressRoute         False
+myResourceGroup     myRouteServer eastus   65515          {10.0.1.4, 10.0.1.5} Succeeded         ExpressRoute         False
 ```
 
 [!INCLUDE [NVA peering note](../../includes/route-server-note-nva-peering.md)]
@@ -106,7 +106,7 @@ When no longer needed, delete the resource group and all of the resources it con
 
 ```azurepowershell-interactive
 # Delete the resource group and all the resources it contains. 
-Remove-AzResourceGroup -Name 'RouteServerRG' -Force
+Remove-AzResourceGroup -Name 'myResourceGroup' -Force
 ```
 
 ## Next step