added reviewer's comments

Author: jjaygbay

articles/azure-vmware/enable-vmware-cds-with-azure.md

@@ -1,13 +1,13 @@
 ---
 title: Enable VMware Cloud director service with Azure VMware Solution (Public Preview)
-description: This article explains how to use  Azure VMware Solution to enable enterprise customers to leverage Azure VMware Solution for private clouds underlying resources for virtual datacenters.
+description: This article explains how to use  Azure VMware Solution to enable enterprise customers to use Azure VMware Solution for private clouds underlying resources for virtual datacenters.
 ms.topic: how-to
 ms.date: 08/09/2022
 ---
 
 # Enable VMware Cloud Director service with Azure VMware Solution (Preview)
 
-[VMware Cloud Director Service (CDs)](https://docs.vmware.com/en/VMware-Cloud-Director-service/services/getting-started-with-vmware-cloud-director-service/GUID-149EF3CD-700A-4B9F-B58B-8EA5776A7A92.htmlor) with Azure VMware Solution enables enterprise customers, to use APIs or the Cloud Director services portal to self-service provision and manage virtual datacenters through multi-tenancy with reduced time and complexity.
+[VMware Cloud Director Service (CDs)](https://docs.vmware.com/en/VMware-Cloud-Director-service/services/getting-started-with-vmware-cloud-director-service/GUID-149EF3CD-700A-4B9F-B58B-8EA5776A7A92.htmlor) with Azure VMware Solution enables enterprise customers to use APIs or the Cloud Director services portal to self-service provision and manage virtual datacenters through multi-tenancy with reduced time and complexity.
 
 In this article, you'll learn how to enable VMware Cloud Director service (CDs) with Azure VMware Solution for enterprise customers to use Azure VMware Solution resources and Azure VMware Solution private clouds with underlying resources for virtual datacenters.
 
@@ -23,14 +23,14 @@ VMware Cloud Director supports multi-tenancy by using organizations. A single or
 
 ## Connect tenants and their organization virtual datacenters to Azure vNet based resources
 
-To provide access to vNET based Azure resources, each tenant can have their own dedicated Azure vNET with Azure VPN gateway. A Site-to-site VPN between customer organization VDC and Azure vNET is established. To achieve this connectivity, the provider will provide public IP to the organization VDC. Organization VDC’s Administrator can configure IPSEC VPN connectivity from Cloud Director Service portal. 
+To provide access to vNET based Azure resources, each tenant can have their own dedicated Azure vNET with Azure VPN gateway. A Site-to-site VPN between customer organization VDC and Azure vNET is established. To achieve this connectivity, the provider will provide public IP to the organization VDC. Organization VDC’s administrator can configure IPSEC VPN connectivity from Cloud Director Service portal. 
 
 :::image type="content" source="media/vmware-cds/site-to-site-vpn-diagram.png" alt-text="Diagram showing site to site VPN connection and how CDS is connected with Azure VMware Solution." border="false" lightbox="media/vmware-cds/site-to-site-vpn-diagram-expanded.png":::
 
 As shown in the diagram above, Organization 01 has two organization Virtual datacenters (VDCs): VDC1 and VDC2. The virtual datacenter of each organization has its own Azure vNETs connected with their respective organization VDC Edge gateway through IPSEC VPN.
-Providers provide public IP addresses to the organization VDC Edge gateway for IPSEC VPN configuration. ORG VDC Edge gateway’s firewall blocks all traffic by default, specific allow rules needs to be added on Organization Edge gateway firewall.
+Providers provide public IP addresses to the organization VDC Edge gateway for IPSEC VPN configuration. An ORG VDC Edge gateway firewall blocks all traffic by default, specific allow rules needs to be added on Organization Edge gateway firewall.
 
-Organization VDCs can be part of a single organization but it still provides isolation between them. For example, VM1 hosted in organization VDC1 cannot ping Azure VM JSVM2 for tenant2.
+Organization VDCs can be part of a single organization and still provide isolation between them. For example, VM1 hosted in organization VDC1 cannot ping Azure VM JSVM2 for tenant2.
 
 ### Prerequisites  
 - Organization VDC is configured with an Edge gateway and has Public IPs assigned to it to establish IPSEC VPN by provider.
@@ -59,7 +59,7 @@ To create an Azure virtual network gateway, see the [create-a-virtual-network-ga
 1.	Under **Instance details**, select **Endpoint** as IP address
 1.	Add IP address (add Public IP address from tenant’s OrgVDC Edge gateway).
 1.	Under **Address space** add **Tenants Org VDC Network**.
-1.	Similarly, create Local network gateway for tenant2.
+1.	Repeat steps 1-5 to create a local network gateway for tenant 2.
 
 ### Create IPSEC connection on VPN gateway
 1. Select tenant1 VPN Gateway (created earlier) and then select **Connection** (in left pane) to add new IPSEC connection with tenant1 orgVDC Edge gateway.  
@@ -100,15 +100,15 @@ Cloud Director Service supports a policy-based VPN. Azure VPN gateway configures
 1. Select **Finish** to apply configuration.
 
 ### Apply firewall configuration
-Organization VDC Edge router firewall denies traffic by default. We need to apply specific rules to enable connectivity. Use the following steps to apply firewall rules.
+Organization VDC Edge router firewall denies traffic by default. You'll need to apply specific rules to enable connectivity. Use the following steps to apply firewall rules.
 
 1.	Add IP set in CDS portal 
      1.	Log in to Edge router then select **IP SETS** under the **Security** tab in left plane.
-     1.Select **New** to create IP sets.
+     1. Select **New** to create IP sets.
      1.	Enter **Name** and **IP address** of test VM deployed in orgVDC.
      1.	Create another IP set for Azure vNET for this tenant.
 2.	Apply firewall rules on ORG VDC Edge router.
-      1. Under **Edge gateway**, select Edge gateway and then select **firewall** under **services**.
+      1. Under **Edge gateway**, select **Edge gateway** and then select **firewall** under **services**.
      1.	Select **Edit rules**. 
      1.	Select **NEW ON TOP** and enter rule name.
      1. Add **source** and **destination** details. Use created IPSET in source and destination.  
@@ -121,9 +121,9 @@ Organization VDC Edge router firewall denies traffic by default. We need to appl
 4.	Verify IPsec connection
      1.	Log in to Azure VM deployed in tenants vNET and ping tenant’s test VM IP address in tenant’s OrgVDC.  
      For example, ping VM1 from JSVM1. Similarly, you should be able to ping VM2 from JSVM2.
-     1.	You can verify isolation between tenants Azure vNETs. Tenant1’s VM1 won't be able to ping Tenant2’s Azure VM JSVM2 in tenant2 Azure vNETs. 
+You can verify isolation between tenants Azure vNETs. Tenant1’s VM1 won't be able to ping Tenant2’s Azure VM JSVM2 in tenant2 Azure vNETs. 
 
-## Connect Tenant’s workload to public Internet   
+## Connect Tenant workload to public Internet   
 
 - Tenants can use public IP to do SNAT configuration to enable Internet access for VM hosted in organization VDC. To achieve this connectivity, the provider can provide public IP to the organization VDC. 
 - Each organization VDC can be created with dedicated T1 router (created by provider) with reserved Public & Private IP for NAT configuration. Tenants can use public IP SNAT configuration to enable Internet access for VM hosted in organization VDC. 
@@ -150,7 +150,7 @@ Organization VDC Edge router firewall denies traffic by default. We need to appl
 
 ### Apply firewall rule
 1. Log in to Organization VDC and navigate to **Edge Gateway**, then select **IP set** under security.
-2. Create an IPset. Provide IP address of your VM (you can use CIDR also). Select save.
+2. Create an IPset. Provide IP address of your VM (you can use CIDR also). Select **Save**.
 3. Under **services**, select **Firewall**, then select **Edit rules**.
 4. Select **New ON TOP** and create a firewall rule to allow desired port and destination.
 1. Select the **IPset** your created earlier as source. Under **Action**, select **Allow**.