Updated all connectivity config-related pages

Author: andreamichaelmsft

articles/virtual-network-manager/concept-connectivity-configuration.md

@@ -40,7 +40,7 @@ By default, the mesh topology defined in your connectivity configuration is a re
 
 ## Behind the scenes: connected group
 
-When you create a mesh topology or enable direct connectivity in a hub-and-spoke topology, a new connectivity construct exclusive to Azure Virtual Network Manager is created called a *connected group*. Virtual networks in a connected group can communicate with each other just like manually connected virtual networks. When you observe the effective routes for a network interface, you'll see a next hop type of *ConnectedGroup*. Virtual networks connected together in a connected group don't have a peering configuration listed under *Peerings* for the virtual network. This connected group is what enables Azure Virtual Network Manager to support a higher scale of virtual network connectivity than traditional virtual network peerings.
+When you create a mesh topology or enable direct connectivity in a hub-and-spoke topology, a new connectivity construct exclusive to Azure Virtual Network Manager is created. This construct is called a *connected group*. Virtual networks in a connected group can communicate with each other just like manually connected virtual networks. When you observe the effective routes for a network interface, you'll see a next hop type of *ConnectedGroup*. Virtual networks connected together in a connected group don't have a peering configuration listed under *Peerings* for the virtual network. This connected group is what enables Azure Virtual Network Manager to support a higher scale of virtual network connectivity than traditional virtual network peerings.
 
 > [!NOTE]
 > A virtual network can be part of up to two connected groups, meaning it can be part of up to two mesh topologies.
@@ -53,7 +53,7 @@ Azure Virtual Network Manager's high-scale connected group feature empowers you
 
 #### Prepare each virtual network in the connected group
 
-1. Review [Increase Private Endpoint virtual network limits](../private-link/increase-private-endpoint-vnet-limits.md) for detailed guidance on raising these limits. Enabling or disabling this feature initiates a one-time connection reset. It's recommended to perform these changes during a maintenance window.
+1. Review [Increase Private Endpoint virtual network limits](../private-link/increase-private-endpoint-vnet-limits.md) for detailed guidance on raising these limits. Enabling or disabling this feature initiates a one-time connection reset. We recommend performing these changes during a maintenance window.
 
 2. Register the feature flag of `Microsoft.Network/EnableMaxPrivateEndpointsVia64kPath` for each subscription containing an Azure Virtual Network Manager instance and virtual networks in your connected group.
 
@@ -68,9 +68,9 @@ In this step, you configure the connectivity configuration's mesh topology setti
 
 1. In your mesh connectivity configuration, locate and select the checkbox for **Enable private endpoints high scale**. This option activates the high-scale feature for your connected group.
 
-1. Verify every virtual network in your connected group (i.e. your entire mesh) is configured with high-scale private endpoints. The Azure portal validates the settings across the entire group. If a virtual network without the high-scale configuration is added later, it can't communicate with private endpoints in other virtual networks.
+1. Verify every virtual network in your entire mesh (connected group) is configured with high-scale private endpoints. The Azure portal validates the settings across the entire group. If a virtual network without the high-scale configuration is added later, it can't communicate with private endpoints in other virtual networks.
 
-1. After verifying all virtual networks are properly configured, deploy the connectivity configuration. This finalizes the setup of your high-scale connected group.
+1. After verifying all virtual networks are properly configured, deploy the connectivity configuration. This step finalizes the setup of your high-scale connected group.
 
 ## Hub-and-spoke topology
 
@@ -120,9 +120,10 @@ You can review the current topology of a connectivity configuration by selecting
 
 ## Next steps
 
-- [Learn how to create a hub-and-spoke connectivity configuration](./how-to-create-hub-and-spoke.md) to manage your network topologies.
-- [Create a secured hub-and-spoke topology in this tutorial](./tutorial-create-secured-hub-and-spoke.md).
-- [Learn how to deploy a hub-and-spoke topology with Azure Firewall](./how-to-deploy-hub-spoke-topology-with-azure-firewall.md).
+- [Learn how to create a mesh connectivity configuration](how-to-create-mesh-network.md).
+- [Learn how to create a hub-and-spoke connectivity configuration](how-to-create-hub-and-spoke.md).
+- [Create a secured hub-and-spoke topology in this tutorial](tutorial-create-secured-hub-and-spoke.md).
+- [Learn how to deploy a hub-and-spoke topology with Azure Firewall](how-to-deploy-hub-spoke-topology-with-azure-firewall.md).
 - [Understand configuration deployments](concept-deployments.md) to effectively manage your network settings.
 - [Block unwanted network traffic](how-to-block-network-traffic-portal.md) using security admin configurations.
 - [Deploy Azure Virtual Network Manager using Terraform](create-virtual-network-manager-terraform.md) to quickly set up your environment.

articles/virtual-network-manager/how-to-create-hub-and-spoke.md

@@ -16,7 +16,7 @@ In this article, you learn how to create a hub-and-spoke topology with Azure Vir
 ## Prerequisites
 
 * Read about the [Hub-and-spoke](concept-connectivity-configuration.md#hub-and-spoke-topology) network topology.
-* Create a [Azure Virtual Network Manager instance](create-virtual-network-manager-portal.md#create-a-virtual-network-manager-instance).
+* Create an [Azure Virtual Network Manager instance](create-virtual-network-manager-portal.md#create-a-virtual-network-manager-instance).
 * Identify the virtual networks you want to use in the hub-and-spoke configuration or create new [virtual networks](../virtual-network/quick-create-portal.md). 
 
 ## <a name="group"></a> Create a network group
@@ -34,7 +34,7 @@ Azure Virtual Network Manager provides you with two methods for adding membershi
 
 ### Manually adding virtual networks
 
-To manually add the desired virtual networks to your network group for use in your connectivity configuration, follow the steps below:
+To manually add the desired virtual networks to your network group for use in your connectivity configuration, follow these steps:
 
 1. From the list of network groups, select your network group and select **Add virtual networks** under *Manually add members* on the network group page.
 
@@ -46,6 +46,8 @@ To manually add the desired virtual networks to your network group for use in yo
 
 This section guides you through creating a hub-and-spoke configuration with the network group you created in the previous section.
 
+1. Select **Configurations** under *Settings*, then select **+ Create**.
+
 1. Select **Connectivity configuration** from the drop-down menu to begin creating a connectivity configuration.
 
 1. On the **Basics** page, enter the following information, and select **Next: Topology >**.
@@ -59,7 +61,7 @@ This section guides you through creating a hub-and-spoke configuration with the
 
 1. Select the **Delete existing peerings** checkbox if you want to remove all previously created virtual network peerings between virtual networks in the network groups included in this configuration. Then select **Select a hub**.
 
-1. On the **Select a hub** pane, select the virtual network that will be the hub virtual network and select **Select**.
+1. On the **Select a hub** pane, select the virtual network intended as the hub virtual network and select **Select**.
 
 1. Select **+ Add network groups**. 
 
@@ -78,6 +80,7 @@ This section guides you through creating a hub-and-spoke configuration with the
 To have this configuration take effect in your environment, you need to deploy the configuration to the regions in which your selected virtual networks reside.
 
 1. Select **Deployments** under *Settings*, then select **Deploy a configuration**.
+
 1. On the **Deploy a configuration** page, select the following settings:
 
     | Setting | Value |
@@ -87,22 +90,24 @@ To have this configuration take effect in your environment, you need to deploy t
     | Target regions | Select all the regions that apply to virtual networks you select for the configuration. You might choose to select a subset of regions at a time if you want to gradually roll out this configuration. |
 
 1. Select **Next** and then select **Deploy** to complete the deployment.
-1. The deployment displays in the list for the selected region. The deployment of the configuration can take a few minutes to complete.
+
+1. The deployment displays in the list for the selected region. The deployment of the configuration can take a few minutes to complete. Select the **Refresh** button to check on the status of the deployment.
 
     :::image type="content" source="./media/how-to-create-hub-and-spoke/deployment-succeeded.png" alt-text="Screenshot of configuration deployment in progress status.":::
 
 > [!NOTE]
-> If you're currently using virtual network peerings created outside of Azure Virtual Network Manager and want to manage your topology and connectivity with Azure Virtual Network Manager, you can migrate without any downtime to your network. Azure Virtual Network Manager instances are fully compatible with pre-existing hub-and-spoke topology deployments using manual peerings. When you deploy a connectivity configuration, the connectivity established is additive by default. This means that you aren't required to delete any existing peered connections between the hub and spoke virtual networks while you verify the connectivity configuration is establishing connectivity as desired.
+> If you're currently using virtual network peerings created outside of Azure Virtual Network Manager and want to manage your topology and connectivity with Azure Virtual Network Manager, you can migrate without any downtime to your network. Azure Virtual Network Manager instances are fully compatible with preexisting hub-and-spoke topology deployments using manual peerings. When you deploy a connectivity configuration, the connectivity established is additive by default. This means that you aren't required to delete any existing peered connections between the hub and spoke virtual networks while you verify the connectivity configuration is establishing connectivity as desired.
 
 ## Confirm configuration deployment
 
-1. See [view applied configuration](how-to-view-applied-configurations.md).
+1. See [view applied configurations](how-to-view-applied-configurations.md).
 
 1. To test *direct connectivity* between spoke virtual networks, deploy a virtual machine into each spoke virtual network. Then initiate an ICMP request from one virtual machine to the other.
 
 ## Next steps
 
-- [Create a secured hub-and-spoke topology in this tutorial](./tutorial-create-secured-hub-and-spoke.md).
-- [Learn how to deploy a hub-and-spoke topology with Azure Firewall](./how-to-deploy-hub-spoke-topology-with-azure-firewall.md).
+- [Create a secured hub-and-spoke topology in this tutorial](tutorial-create-secured-hub-and-spoke.md).
+- [Learn how to deploy a hub-and-spoke topology with Azure Firewall](how-to-deploy-hub-spoke-topology-with-azure-firewall.md).
+- [Learn how to create a mesh connectivity configuration](how-to-create-mesh-network.md).
 - Learn about [Security admin rules](concept-security-admins.md)
 - Learn how to block network traffic with a [Security admin configuration](how-to-block-network-traffic-portal.md).