tweaks to the PS quickstart

Author: halkazwini

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

@@ -5,7 +5,7 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: azure-route-server
 ms.topic: quickstart
-ms.date: 09/19/2024
+ms.date: 09/23/2024
 ms.custom: devx-track-azurepowershell, mode-api
 ---
 
@@ -31,23 +31,23 @@ In this quickstart, you learn how to create an Azure Route Server to peer with a
 
 ## Create a route server
 
-In this section, you create a route server. Prior to creating the route server, you create a resource group to host all resources including the route server. You'll also create a virtual network with a dedicated subnet for the route server.
+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). 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 **RouteServerRG** in the **WestUS** region:
 
     ```azurepowershell-interactive
     # Create a resource group.
     New-AzResourceGroup = -Name 'RouteServerRG' -Location 'WestUS'
     ```
 
-1. The route server requires a dedicated subnet named *RouteServerSubnet*. The subnet size has to be at least /27 or shorter prefix (such as /26 or /25) or you'll receive an error message when deploying the route server. Create a subnet configuration for **RouteServerSubnet** using [New-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/new-azvirtualnetworksubnetconfig).
+1. The route server requires a dedicated subnet named *RouteServerSubnet*. The subnet size has to be at least /27 or shorter prefix (such as /26 or /25) or you'll receive an error message when deploying the route server. Create a subnet configuration for **RouteServerSubnet** using [New-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/new-azvirtualnetworksubnetconfig) cmdlet.
 
     ```azurepowershell-interactive
     # Create subnet configuration.
     $subnet = New-AzVirtualNetworkSubnetConfig -Name 'RouteServerSubnet' -AddressPrefix '10.0.1.0/27'
     ```
 
-1. Create a virtual network using [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork). 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 **myRouteServerVNet** in the **WestUS** region.
 
     ```azurepowershell-interactive
     # Create a virtual network and place into a variable.
@@ -56,25 +56,25 @@ In this section, you create a route server. Prior to creating the route server,
     $subnetId = (Get-AzVirtualNetworkSubnetConfig -Name 'RouteServerSubnet' -VirtualNetwork $vnet).Id
     ```
 
-1. To ensure connectivity to the backend service that manages Route Server configuration, assigning a public IP address is required. Create a Standard Public IP named **RouteServerIP** using [New-AzPublicIpAddress](/powershell/module/az.network/new-azpublicipaddress).
+1. To ensure connectivity to the backend service that manages Route Server configuration, assigning a public IP address is required. Create a Standard Public IP named **RouteServerIP** using [New-AzPublicIpAddress](/powershell/module/az.network/new-azpublicipaddress) cmdlet.
 
     ```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'
     ```
 
-1. Create the route server using [New-AzRouteServer](/powershell/module/az.network/new-azrouteserver). 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 section.
+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.
 
     ```azurepowershell-interactive
-    # Create a route server.
+    # Create the route server.
     New-AzRouteServer -RouteServerName 'myRouteServer' -ResourceGroupName 'RouteServerRG' -Location 'WestUS' -HostedSubnet $subnetId -PublicIP $publicIp
     ```
 
     [!INCLUDE [Deployment note](../../includes/route-server-note-creation-time.md)]
 
 ## Set up peering with NVA
 
-In this section, you learn how to configure BGP peering with a network virtual appliance (NVA). Use [Add-AzRouteServerPeer](/powershell/module/az.network/add-azrouteserverpeer) to establish BGP peering from the route server to your NVA. The following example adds a peer named **myNVA** that has an IP address of **10.0.0.4** and an ASN of **65001**. For more information, see [What Autonomous System Numbers (ASNs) can I use?](route-server-faq.md#what-autonomous-system-numbers-asns-can-i-use)
+In this section, you learn how to configure BGP peering with a network virtual appliance (NVA). Use [Add-AzRouteServerPeer](/powershell/module/az.network/add-azrouteserverpeer) cmdlet to establish BGP peering from the route server to your NVA. The following example adds a peer named **myNVA** that has an IP address of **10.0.0.4** and an ASN of **65001**. For more information, see [What Autonomous System Numbers (ASNs) can I use?](route-server-faq.md#what-autonomous-system-numbers-asns-can-i-use)
 
 ```azurepowershell-interactive
 # Add a peer.
@@ -83,14 +83,14 @@ Add-AzRouteServerPeer -ResourceGroupName 'RouteServerRG' -RouteServerName 'myRou
 
 ## Complete the configuration on the NVA
 
-To complete the peering setup, you must configure the NVA to establish a BGP session with the route server's peer IPs and ASN. Use [Get-AzRouteServer](/powershell/module/az.network/get-azrouteserver) to get the IP and ASN of the route server.
+To complete the peering setup, you must configure the NVA to establish a BGP session with the route server's peer IPs and ASN. Use [Get-AzRouteServer](/powershell/module/az.network/get-azrouteserver) cmdlet to get the IP and ASN of the route server.
 
 ```azurepowershell-interactive
 # Get the route server details.
 Get-AzRouteServer -ResourceGroupName 'RouteServerRG' -RouteServerName 'myRouteServer'
 ```
 
-The output looks like the following example:
+The output should look similar to the following example:
 
 ```output
 ResourceGroupName Name          Location RouteServerAsn RouteServerIps       ProvisioningState HubRoutingPreference AllowBranchToBranchTraffic
@@ -102,7 +102,7 @@ RouteServerRG     myRouteServer westus   65515          {10.0.1.4, 10.0.1.5} Suc
 
 ## Clean up resources
 
-When no longer needed, delete the resource group and all of the resources it contains using [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup).
+When no longer needed, delete the resource group and all of the resources it contains using [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup) cmdlet.
 
 ```azurepowershell-interactive
 # Delete the resource group and all the resources it contains.