Update tutorial-configure-networking.md

Author: rvandenbedem

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

@@ -4,7 +4,7 @@ description: Learn to create and configure the networking needed to deploy your
 ms.topic: tutorial
 ms.custom: engagement-fy23
 ms.service: azure-vmware
-ms.date: 12/19/2023
+ms.date: 6/12/2024
 ---
 
 # Tutorial: Configure networking for your VMware private cloud in Azure
@@ -22,65 +22,65 @@ In this tutorial, you learn how to:
 > * Connect your ExpressRoute circuit to the gateway
 
 >[!NOTE]
->Before you create a new virtual  network (vNet), evaluate if you already have an existing vNet in Azure and plan to use it to connect to Azure VMware Solution; or whether to create a new vNet entirely.  
->* To use an existing vNet in same Azure subscription as Azure VMware Solution, use the **[Azure vNet connect](#select-an-existing-vnet)** tab under **Connectivity**. 
->* To use an existing vNet in a different Azure subscription than Azure VMware Solution, use the guidance on **[Connect to the private cloud manually](#connect-to-the-private-cloud-manually)**. 
->* To create a new vNet in same Azure subscription as Azure VMware Solution, use the **[Azure vNet connect](#create-a-new-vnet)** tab or create one [manually](#create-a-vnet-manually).
+>Before you create a new virtual  network (VNet), evaluate if you already have an existing VNet in Azure and plan to use it to connect to Azure VMware Solution; or whether to create a new VNet entirely.  
+>* To use an existing VNet in same Azure subscription as Azure VMware Solution, use the **[Azure VNet connect](#select-an-existing-vnet)** tab under **Connectivity**. 
+>* To use an existing VNet in a different Azure subscription than Azure VMware Solution, use the guidance on **[Connect to the private cloud manually](#connect-to-the-private-cloud-manually)**. 
+>* To create a new VNet in same Azure subscription as Azure VMware Solution, use the **[Azure VNet connect](#create-a-new-vnet)** tab or create one [manually](#create-a-vnet-manually).
 
-## Connect with the Azure vNet connect feature
+## Connect with the Azure VNet connect feature
 
-You can use the **Azure vNet connect** feature to use an existing vNet or create a new vNet to connect to Azure VMware Solution. **Azure vNet connect** is a function to configure vNet connectivity, it doesn't record configuration state; browse the Azure portal to check what settings are already configured.
+You can use the **Azure VNet connect** feature to use an existing VNet or create a new VNet to connect to Azure VMware Solution. **Azure VNet connect** is a function to configure VNet connectivity, it doesn't record configuration state; browse the Azure portal to check what settings are already configured.
 
 >[!NOTE]
->Address space in the vNet cannot overlap with the Azure VMware Solution private cloud CIDR.
+>Address space in the VNet cannot overlap with the Azure VMware Solution private cloud CIDR.
 
 ### Prerequisites
 
-Before you select an existing vNet, there are specific requirements that must be met.
+Before you select an existing VNet, there are specific requirements that must be met.
 
-1. vNet must contain a gateway subnet.
+1. VNet must contain a gateway subnet.
 1. Be in the same region as Azure VMware Solution private cloud.
 1. Be in the same resource group as Azure VMware Solution private cloud.
-1. vNet must contain an address space that doesn't overlap with Azure VMware Solution.
+1. VNet must contain an address space that doesn't overlap with Azure VMware Solution.
 1. Validate solution design is within Azure VMware Solution limits (Microsoft technical documentation/azure/azure-resource-manager/management/azure-subscription-service-limits).
 
-### Select an existing vNet
+### Select an existing VNet
 
-When you select an existing vNet, the Azure Resource Manager (ARM) template that creates the vNet and other resources gets redeployed. The resources, in this case, are the public IP, gateway, gateway connection, and ExpressRoute authorization key. If everything is set up, the deployment doesn't change anything. However, if anything is missing, it gets created automatically. For example, if the GatewaySubnet is missing, then it gets added during the deployment.
+When you select an existing VNet, the Azure Resource Manager (ARM) template that creates the VNet and other resources gets redeployed. The resources, in this case, are the public IP, gateway, gateway connection, and ExpressRoute authorization key. If everything is set up, the deployment doesn't change anything. However, if anything is missing, it gets created automatically. For example, if the GatewaySubnet is missing, then it gets added during the deployment.
 
 1. In your Azure VMware Solution private cloud, under **Manage**, select **Connectivity**.
 
-2. Select the **Azure vNet connect** tab and then select the existing vNet.
+2. Select the **Azure VNet connect** tab and then select the existing VNet.
 
-   :::image type="content" source="media/networking/azure-vnet-connect-tab.png" alt-text="Screenshot showing the Azure vNet connect tab under Connectivity with an existing vNet selected.":::
+   :::image type="content" source="media/networking/azure-vnet-connect-tab.png" alt-text="Screenshot showing the Azure VNet connect tab under Connectivity with an existing VNet selected.":::
 
 3. Select **Save**.
 
-   At this point, the vNet validates if overlapping IP address spaces between Azure VMware Solution and vNet are detected. If detected, change the network address of either the private cloud or the vNet so they don't overlap. 
+   At this point, the VNet validates if overlapping IP address spaces between Azure VMware Solution and VNet are detected. If detected, change the network address of either the private cloud or the VNet so they don't overlap. 
 
 
-### Create a new vNet
+### Create a new VNet
 
-When you create a new vNet, the required components to connect to Azure VMware Solution are automatically created.
+When you create a new VNet, the required components to connect to Azure VMware Solution are automatically created.
 
 1. In your Azure VMware Solution private cloud, under **Manage**, select **Connectivity**.
 
-2. Select the **Azure vNet connect** tab and then select **Create new**.
+2. Select the **Azure VNet connect** tab and then select **Create new**.
 
-   :::image type="content" source="media/networking/azure-vnet-connect-tab-create-new.png" alt-text="Screenshot showing the Azure vNet connect tab under Connectivity.":::
+   :::image type="content" source="media/networking/azure-vnet-connect-tab-create-new.png" alt-text="Screenshot showing the Azure VNet connect tab under Connectivity.":::
 
-3. Provide or update the information for the new vNet and then select **OK**.
+3. Provide or update the information for the new VNet and then select **OK**.
 
-   At this point, the vNet validates if overlapping IP address spaces between Azure VMware Solution and vNet are detected. If detected, change the private cloud or vNet's network address so they don't overlap. 
+   At this point, the VNet validates if overlapping IP address spaces between Azure VMware Solution and VNet are detected. If detected, change the private cloud or VNet's network address so they don't overlap. 
 
    :::image type="content" source="media/networking/create-new-virtual-network.png" alt-text="Screenshot showing the Create virtual network window.":::
 
-The vNet with the provided address range and GatewaySubnet is created in your subscription and resource group.  
+The VNet with the provided address range and GatewaySubnet is created in your subscription and resource group.  
 
 
 ## Connect to the private cloud manually
 
-### Create a vNet manually
+### Create a VNet manually
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -154,13 +154,13 @@ Now that you deployed a virtual network gateway, add a connection between it and
 In this tutorial, you learned how to:
 
 > [!div class="checklist"]
-> * Create a Virtual Network using the vNet Connect Feature
+> * Create a Virtual Network using the VNet Connect Feature
 > * Create a Virtual Network Manually
 > * Create a Virtual Network gateway
 > * Connect your ExpressRoute circuit to the gateway
 
 
-Continue to the next tutorial to learn how to create the NSX-T network segments used for VMs in vCenter Server.
+Continue to the next tutorial to learn how to create the NSX network segments used for VMs in vCenter Server.
 
 > [!div class="nextstepaction"]
-> [Create an NSX-T network segment](./tutorial-nsx-t-network-segment.md)
+> [Create an NSX network segment](./tutorial-nsx-t-network-segment.md)