fixed publishing comments

Author: jjaygbay1

articles/azure-vmware/native-connect-multiple-private-clouds.md

@@ -13,19 +13,19 @@ ms.custom: engagement-fy25
 
 # Connect multiple Azure VMware Solution Generation 2 private clouds
 
-In this article, you learn how to connect a Azure VMware Solution Generation 2 (Gen 2) private cloud to other Gen 2 private clouds.
+In this article, you learn how to connect an Azure VMware Solution Generation 2 (Gen 2) private cloud to other Gen 2 private clouds.
 
 ## Prerequisite
 
 Have multiple Azure VMware Solution Gen 2 private clouds deployed successfully.
 
-## Connect multiple Azure VMware Solution Gen 2 
+## Use Virtual Network peering to connect multiple private clouds
 
-Private clouds deployed in different Azure Virtual Networks can be connected using Virtual Network peering. The Virtual Network peering provides the best possible throughput and latency between Azure VMware Solution private clouds in the same region. For more information about how to do Azure Virtual Network peering, see [Create, change, or delete a Virtual Network peering](/azure/virtual-network/virtual-network-peering-overview).
+You can connect private clouds deployed in different Azure Virtual Networks using virtual network peering. The virtual network peering provides the best possible throughput and latency between Azure VMware Solution private clouds in the same region. For more information about how to do Azure Virtual Network peering, see [Create, change, or delete a Virtual Network peering](/azure/virtual-network/virtual-network-peering-overview).
 
 Depending on the location of the private cloud, you may require local Virtual Network peering or a global Virtual Network peering.
 
-:::image type="content" source="./media/native-connectivity/native-connect-multiple-solutions-on-premises.png" alt-text="Diagram of an multiple Azure VMware Solution Gen 2 private clouds connected together." lightbox="media/native-connectivity/native-connect-multiple-solutions-on-premises.png":::
+:::image type="content" source="./media/native-connectivity/native-connect-multiple-solutions-on-premises.png" alt-text="Diagram of multiple Azure VMware Solution Gen 2 private clouds connected together." lightbox="media/native-connectivity/native-connect-multiple-solutions-on-premises.png":::
 
 ## Related topics 
 - [Connectivity to an Azure Virtual Network](native-network-connectivity.md)

articles/azure-vmware/native-dns-forward-lookup-zone.md

@@ -14,7 +14,7 @@ In this article, you learn how to configure a Domain Name System (DNS) forward l
 
 ## Prerequisite
 
-Gen 2 private cloud successfully deployed. 
+Gen 2 private cloud is successfully deployed. 
 
 ## DNS forward lookup zone configuration options 
 
@@ -28,44 +28,44 @@ DNS forward lookup zone can be configured at the time of creation or changed aft
 
 :::image type="content" source="./media/native-connectivity/native-connect-dns-lookup.png" alt-text="Diagram showing an Azure VMware Solution Gen 2 DNS forward lookup." lightbox="media/native-connectivity/native-connect-dns-lookup.png":::
 
-## Configuring Private DNS for your Azure VMware Solution Generation 2 Private Cloud  
+## Configure private DNS for your Azure VMware Solution Generation 2 private cloud  
 
 If you select the Private DNS option, the private cloud will be resolvable from the Virtual Network where the private cloud is provisioned. This is done by linking the private DNS zone to your Virtual Network. If you need to enable this zone to be resolvable outside of this Virtual Network, such as in your on-premises environment, you need to configure an Azure DNS Private Resolver, or deploy your own DNS server in your Virtual Network. Private DNS will use the Azure DNS Service (168.63.129.16) to resolve your private cloud FQDNs. This section explains configuring an Azure DNS Private Resolver. 
 
  ### Prerequisite
- 
- First, create two /28 subnets to delegate to the Azure DNS Private Resolver service. As an example. They can be named dns-in and dns-out. 
- 
+
+ Create two /28 subnets to delegate to the Azure DNS Private Resolver service. As an example, they can be named ```dns-in``` and ```dns-out```.
+
  ### Deploy Azure DNS Private Resolver
 
- In your Resource Group, deploy the Private DNS Resolver. 
+ In the Resource Group, deploy the Private DNS Resolver. 
 
- 1. Click create. 
- 2. In the Search the Marketplace field, type Private DNS Resolver and click enter. 
- 3. Click create for the Private DNS Resolver. 
- 4. Ensure the Subscription, Resource group, and Region fields are correct. Enter a name and choose your Virtual Network. This network must be the same as where you deployed your private cloud, then click Next: Inbound Endpoints. 
- 5. Click Add an Endpoint, enter a name for the Inbound endpoint, such as dns-in and select the subnet for the DNS inbound endpoint and click Save.
- 6. Click Next: Outbound Endpoints. 
- 7. Click Add an Endpoint, enter a name for the Outbound endpoint, such as dns-out and select the subnet for the DNS outbound endpoint and click Save.
- 8. Click Next: Ruleset. 
- 9. Click Next: Tags. 
- 10. Click Next: Review + Create. 
- 11. When the Validation passes, click create. 
+ 1. Select Create. 
+ 2. In the Search the Marketplace field, type Private DNS Resolver and select enter. 
+ 3. Select Create for the Private DNS Resolver. 
+ 4. Ensure the Subscription, Resource group, and Region fields are correct. Enter a name and choose your Virtual Network. This network must be the same as where you deployed your private cloud, then select Next: Inbound Endpoints. 
+ 5. Select Add an Endpoint, enter a name for the Inbound endpoint, such as dns-in and select the subnet for the DNS inbound endpoint and select Save.
+ 6. Select Next: Outbound Endpoints. 
+ 7. Select Add an Endpoint, enter a name for the Outbound endpoint, such as dns-out and select the subnet for the DNS outbound endpoint and select Save.
+ 8. Select Next: Ruleset. 
+ 9. Select Next: Tags. 
+ 10. Select Next: Review + Create. 
+ 11. When the Validation passes, select Create. 
 
-You can now resolve your private cloud DNS records from any workload using the Inbound endpoint of the Azure DNS Private Resolver as it’s DNS server. You should now create a conditional forwarder in your on-premesis DNS server and point it to the Inbound Endpoint of the Azure DNS Private Resolver to allow DNS resolution of your private cloud from your corporate network. 
+You can now resolve private cloud DNS records from any workload using the Inbound endpoint of the Azure DNS Private Resolver as it’s DNS server. You should now create a conditional forwarder in your on-premises DNS server and point it to the Inbound Endpoint of the Azure DNS Private Resolver to allow DNS resolution of the private cloud from your corporate network. 
 
- ### Enable Resolution for private cloud Workload Virtual Machines
+ ### Enable Resolution for private cloud workload virtual machines
 
- If you need workload Virtual Machines deployed in your private cloud to resolve the private cloud management components you must add a forwarder to VMware NSX. 
+ If you need workload virtual machines deployed in your private cloud to resolve the private cloud management components you must add a forwarder to VMware NSX. 
 
  1. In your Resource group, open your private cloud. 
- 2. Expand Workload Networking and click on DNS. 
- 3. Click the Add button, select FQDN zone, enter your private cloud’s DNS zone name and Domain, for IP address enter the IP address of the inbound endpoint of your Azure DNS Private Resolver and click OK. 
- 4. Click on DNS Service. 
- 5. Click Edit. 
- 6. Select the zone you just created in the FQDN zones dropdown and click OK.  
- 
- Your workload Virtual Machines can now resolve the private cloud management components. 
+ 2. Expand Workload Networking and select DNS. 
+ 3. Select the Add button, select FQDN zone, enter your private cloud’s DNS zone name and Domain. For IP address enter the IP address of the inbound endpoint of your Azure DNS Private Resolver and select OK. 
+ 4. Select DNS Service. 
+ 5. Select Edit. 
+ 6. Select the zone you just created in the FQDN zones dropdown and select OK.  
+
+ Your workload virtual machines can now resolve the private cloud management components. 
 
 ## Related topics
 - [Connectivity to an Azure Virtual Network](native-network-connectivity.md)