Merge pull request #252644 from aviviano/av-style-guide-edits-091423

AI generated style guide edits

Author: American-Dipper

articles/azure-vmware/concepts-networking.md

@@ -1,27 +1,28 @@
 ---
 title: Concepts - Network interconnectivity
-description: Learn about key aspects and use cases of networking and interconnectivity in Azure VMware Solution.
+description: Learn about key concepts and use cases of networking and interconnectivity in Azure VMware Solution.
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 6/27/2023
+ms.date: 06/27/2023
 ms.custom: engagement-fy23
 ---
 
 # Azure VMware Solution networking and interconnectivity concepts
 
 [!INCLUDE [avs-networking-description](includes/azure-vmware-solution-networking-description.md)]
 
-There are two ways to interconnectivity in the Azure VMware Solution private cloud:
+Azure VMware Solution private cloud offers two types of interconnectivity:
 
-- [**Basic Azure-only interconnectivity**](#azure-virtual-network-interconnectivity) lets you manage and use your private cloud with only a single virtual network in Azure. This implementation is best suited for Azure VMware Solution evaluations or implementations that don't require access from on-premises environments.
+- [**Basic Azure-only interconnectivity**](#azure-virtual-network-interconnectivity) allows you to manage and use your private cloud with a single virtual network in Azure. This setup is ideal for evaluations or implementations that don't require access from on-premises environments.
 
 - [**Full on-premises to private cloud interconnectivity**](#on-premises-interconnectivity) extends the basic Azure-only implementation to include interconnectivity between on-premises and Azure VMware Solution private clouds.
- 
-This article covers the key concepts that establish networking and interconnectivity, including requirements and limitations. In addition, this article provides you with the information you need to know to work with Azure VMware Solution to configure your networking.
+
+This article explains key networking and interconnectivity concepts, including requirements and limitations. It also provides the information you need to configure your networking with Azure VMware Solution.
 
 ## Azure VMware Solution private cloud use cases
 
 The use cases for Azure VMware Solution private clouds include:
+
 - New VMware vSphere VM workloads in the cloud
 - VM workload bursting to the cloud (on-premises to Azure VMware Solution only)
 - VM workload migration to the cloud (on-premises to Azure VMware Solution only)
@@ -33,41 +34,41 @@ The use cases for Azure VMware Solution private clouds include:
 
 ## Azure virtual network interconnectivity
 
-You can interconnect your Azure virtual network with the Azure VMware Solution private cloud implementation. You can manage your Azure VMware Solution private cloud, consume workloads in your private cloud, and access other Azure services.
+You can interconnect your Azure virtual network with the Azure VMware Solution private cloud implementation. This connection allows you to manage your Azure VMware Solution private cloud, consume workloads in your private cloud, and access other Azure services.
 
-The diagram below shows the basic network interconnectivity established at the time of a private cloud deployment. It shows the logical networking between a virtual network in Azure and a private cloud. This connectivity is established via a backend ExpressRoute that is part of the Azure VMware Solution service. The interconnectivity fulfills the following primary use cases:
+The following diagram illustrates the basic network interconnectivity established during a private cloud deployment. It shows the logical networking between a virtual network in Azure and a private cloud. This connectivity is established via a backend ExpressRoute that is part of the Azure VMware Solution service. The interconnectivity supports the following primary use cases:
 
-- Inbound access to vCenter Server and NSX-T Manager that is accessible from VMs in your Azure subscription.
+- Inbound access to vCenter Server and NSX-T Manager from VMs in your Azure subscription.
 - Outbound access from VMs on the private cloud to Azure services.
-- Inbound access of workloads running in the private cloud.
+- Inbound access to workloads running in the private cloud.
 
 > [!IMPORTANT]
-> When connecting **production** Azure VMware Solution private clouds to an Azure virtual network, an ExpressRoute virtual network gateway with the Ultra Performance Gateway SKU should be used with FastPath enabled to achieve 10Gbps connectivity. Less critical environments can use the Standard or High Performance Gateway SKUs for slower network performance.
+> When connecting **production** Azure VMware Solution private clouds to an Azure virtual network, use an ExpressRoute virtual network gateway with the Ultra Performance Gateway SKU and enable FastPath to achieve 10Gbps connectivity. For less critical environments, use the Standard or High Performance Gateway SKUs for slower network performance.
 
 > [!NOTE]
-> If connecting more than four Azure VMware Solution private clouds in the same Azure region to the same Azure virtual network is a requirement, use [AVS Interconnect](connect-multiple-private-clouds-same-region.md) to aggregate private cloud connectivity within the Azure region.
+> If you need to connect more than four Azure VMware Solution private clouds in the same Azure region to the same Azure virtual network, use [AVS Interconnect](connect-multiple-private-clouds-same-region.md) to aggregate private cloud connectivity within the Azure region.
 
-:::image type="content" source="media/concepts/adjacency-overview-drawing-single.png" alt-text="Diagram showing the basic network interconnectivity established at the time of an Azure VMware Solution private cloud deployment." border="false" lightbox="media/concepts/adjacency-overview-drawing-single.png":::
+:::image type="content" source="media/concepts/adjacency-overview-drawing-single.png" alt-text="Diagram illustrating basic network interconnectivity during an Azure VMware Solution private cloud deployment." border="false" lightbox="media/concepts/adjacency-overview-drawing-single.png":::
 
 ## On-premises interconnectivity
 
-In the fully interconnected scenario, you can access the Azure VMware Solution from your Azure virtual network(s) and on-premises. This implementation is an extension of the basic implementation described in the previous section. An ExpressRoute circuit is required to connect from on-premises to your Azure VMware Solution private cloud in Azure.
+In the fully interconnected scenario, you can access the Azure VMware Solution from your Azure virtual network(s) and on-premises. This implementation extends the basic implementation described in the previous section. An ExpressRoute circuit is required to connect from on-premises to your Azure VMware Solution private cloud in Azure.
 
-The diagram below shows the on-premises to private cloud interconnectivity, which enables the following use cases:
+The following diagram shows the on-premises to private cloud interconnectivity, which enables the following use cases:
 
 - Hot/Cold vSphere vMotion between on-premises and Azure VMware Solution.
 - On-premises to Azure VMware Solution private cloud management access.
 
-:::image type="content" source="media/concepts/adjacency-overview-drawing-double.png" alt-text="Diagram showing the virtual network and on-premises to private cloud interconnectivity." border="false" lightbox="media/concepts/adjacency-overview-drawing-double.png":::
+:::image type="content" source="media/concepts/adjacency-overview-drawing-double.png" alt-text="Diagram displaying virtual network and on-premises to private cloud interconnectivity." border="false" lightbox="media/concepts/adjacency-overview-drawing-double.png":::
 
-For full interconnectivity to your private cloud, you need to enable ExpressRoute Global Reach and then request an authorization key and private peering ID for Global Reach in the Azure portal. The authorization key and peering ID are used to establish Global Reach between an ExpressRoute circuit in your subscription and the ExpressRoute circuit for your private cloud. Once linked, the two ExpressRoute circuits route network traffic between your on-premises environments to your private cloud. For more information on the procedures, see the [tutorial for creating an ExpressRoute Global Reach peering to a private cloud](tutorial-expressroute-global-reach-private-cloud.md).
+For full interconnectivity to your private cloud, enable ExpressRoute Global Reach and then request an authorization key and private peering ID for Global Reach in the Azure portal. Use the authorization key and peering ID to establish Global Reach between an ExpressRoute circuit in your subscription and the ExpressRoute circuit for your private cloud. Once linked, the two ExpressRoute circuits route network traffic between your on-premises environments and your private cloud. For more information on the procedures, see the [tutorial for creating an ExpressRoute Global Reach peering to a private cloud](tutorial-expressroute-global-reach-private-cloud.md).
 
 > [!IMPORTANT]
-> Customers should not advertise bogon routes over ExpressRoute from on-premises or their Azure VNet.  Examples of bogon routes include 0.0.0.0/5 or 192.0.0.0/3.
-
+> Don't advertise bogon routes over ExpressRoute from on-premises or your Azure VNet. Examples of bogon routes include 0.0.0.0/5 or 192.0.0.0/3.
 
 ## Route advertisement guidelines to Azure VMware Solution
- You need to follow these guidelines while advertising routes from your on-premises and Azure VNET to Azure VMware Solution over ExpressRoute:
+
+Follow these guidelines when advertising routes from your on-premises and Azure VNET to Azure VMware Solution over ExpressRoute:
 
 | **Supported** |**Not supported**|
 | ---------------| ---------------|
@@ -78,13 +79,13 @@ For full interconnectivity to your private cloud, you need to enable ExpressRout
 > [!NOTE]
 > The customer-advertised default route to Azure VMware Solution can't be used to route back the traffic when the customer accesses Azure VMware Solution management appliances (vCenter Server, NSX-T Manager, HCX Manager). The customer needs to advertise a more specific route to Azure VMware Solution for that traffic to be routed back.
 
-
 ## Limitations
+
 [!INCLUDE [azure-vmware-solutions-limits](includes/azure-vmware-solutions-limits.md)]
 
 ## Next steps 
 
-Now that you've covered Azure VMware Solution network and interconnectivity concepts, you may want to learn about:
+Now that you understand Azure VMware Solution network and interconnectivity concepts, consider learning about:
 
 - [Azure VMware Solution storage concepts](concepts-storage.md)
 - [Azure VMware Solution identity concepts](concepts-identity.md)