edit pass: tutorial-configure-networking-2

Author: ShawnJackson

articles/azure-vmware/includes/connect-expressroute-vnet.md

@@ -23,7 +23,7 @@ ms.custom: engagement-fy23
    | --- | --- |
    | **Name**  | Enter a name for the connection.  |
    | **Connection type**  | Select **ExpressRoute**.  |
-   | **Redeem authorization**  | Ensure that this box is selected.  |
+   | **Redeem authorization**  | Ensure that this checkbox is selected.  |
    | **Virtual network gateway** | The value is prepopulated with the virtual network gateway that you intend to use.  |
    | **Authorization key**  | Paste the authorization key that you copied earlier. |
    | **Peer circuit URI**  | Paste the ExpressRoute ID that you copied earlier.  |

articles/azure-vmware/includes/request-authorization-key.md

@@ -11,7 +11,11 @@ ms.custom: engagement-fy23
 
 <!-- used in tutorial-expressroute-global-reach-private-cloud.md and create-ipsec-tunnel.md -->
 
-1. In the Azure portal, go to the Azure VMware Solution private cloud. Select **Manage** > **Connectivity** > **ExpressRoute**, and then select **+ Request an authorization key**.
+1. In the Azure portal, go to the Azure VMware Solution private cloud.
+
+1. Under **Manage**, select **Connectivity**.
+
+1. Select the **ExpressRoute** tab, and then select **+ Request an authorization key**.
 
    :::image type="content" source="../media/expressroute-global-reach/start-request-authorization-key.png" alt-text="Screenshot that shows selections for requesting an ExpressRoute authorization key." border="true" lightbox="../media/expressroute-global-reach/start-request-authorization-key.png":::
 

articles/azure-vmware/tutorial-configure-networking.md

@@ -53,32 +53,36 @@ When you select an existing virtual network, the Azure Resource Manager (ARM) te
 
 If everything is set up, the deployment doesn't change anything. However, if anything is missing, it's created automatically. For example, if the gateway subnet is missing, it's added during the deployment.
 
-1. In your Azure VMware Solution private cloud, under **Manage**, select **Connectivity**.
+1. In the Azure portal, go to the Azure VMware Solution private cloud.
 
-2. Select the **Azure VNet connect** tab, and then select the existing virtual network.
+1. Under **Manage**, select **Connectivity**.
+
+1. Select the **Azure VNet connect** tab, and then select the existing virtual network.
 
    :::image type="content" source="media/networking/azure-vnet-connect-tab.png" alt-text="Screenshot that shows the Azure VNet connect tab with an existing virtual network selected.":::
 
-3. Select **Save**.
+1. Select **Save**.
 
 At this point, the virtual network detects whether IP address spaces overlap between Azure VMware Solution and the virtual network. If overlapping IP address spaces are detected, change the network address of either the private cloud or the virtual network so they don't overlap.
 
 ### Create a new virtual network
 
 When you create a virtual network, the required components to connect to Azure VMware Solution are automatically created.
 
-1. In your Azure VMware Solution private cloud, under **Manage**, select **Connectivity**.
+1. In the Azure portal, go to the Azure VMware Solution private cloud.
 
-2. Select the **Azure VNet connect** tab, and then select **Create new**.
+1. Under **Manage**, select **Connectivity**.
 
-   :::image type="content" source="media/networking/azure-vnet-connect-tab-create-new.png" alt-text="Screenshot that shows the Azure VNet connect tab and the link for creating a new virtual network.":::
+1. Select the **Azure VNet connect** tab, and then select **Create new**.
 
-3. Provide or update the information for the new virtual network, and then select **OK**.
+   :::image type="content" source="media/networking/azure-vnet-connect-tab-create-new.png" alt-text="Screenshot that shows the Azure VNet connect tab and the link for creating a new virtual network.":::
 
-   At this point, the virtual network detects whether IP address spaces overlap between Azure VMware Solution and the virtual network. If overlapping IP address spaces are detected, change the network address of either the private cloud or the virtual network so they don't overlap.
+1. Provide or update the information for the new virtual network, and then select **OK**.
 
    :::image type="content" source="media/networking/create-new-virtual-network.png" alt-text="Screenshot that shows the pane for creating a virtual network.":::
 
+At this point, the virtual network detects whether IP address spaces overlap between Azure VMware Solution and the virtual network. If overlapping IP address spaces are detected, change the network address of either the private cloud or the virtual network so they don't overlap.
+
 The virtual network with the provided address range and gateway subnet is created in your subscription and resource group.  
 
 ## Connect to the private cloud manually
@@ -100,7 +104,7 @@ The virtual network with the provided address range and gateway subnet is create
    1. On the **IP Addresses** tab, under **IPv4 address space**, enter the address space that you created in the previous tutorial.
 
       > [!IMPORTANT]
-      > You must use an address space that *does not* overlap with the address space that you used when you created your private cloud in the preceding tutorial.
+      > You must use an address space that doesn't overlap with the address space that you used when you created your private cloud in the preceding tutorial.
 
    1. Select **+ Add subnet**. On the **Add subnet** pane, give the subnet a name and an appropriate address range, and then select **Add**.
 
@@ -144,7 +148,7 @@ After the deployment finishes, move to the next section to connect ExpressRoute
 
 ### Connect ExpressRoute to the virtual network gateway
 
-Now that you've deployed a virtual network gateway, add a connection between it and your Azure VMware Solution private cloud.
+Now that you've deployed a virtual network gateway, add a connection between it and your Azure VMware Solution private cloud:
 
 [!INCLUDE [connect-expressroute-to-vnet](includes/connect-expressroute-vnet.md)]