Update load-balancer-migration-guidelines.md

Author: abhishjain002

articles/hdinsight/load-balancer-migration-guidelines.md

@@ -14,38 +14,39 @@ This transition is done in line with the announcement of retirement of Azure bas
 
 ## Impact on HDInsight clusters
 
-### Long running clusters (when you don’t create and delete cluster daily for your use case)
+### Long running clusters (when you don’t create and delete cluster frequently for your use case)
 
-   * **Scenario 1:**  Existing HDInsight clusters without custom virtual network. (No virtual network provided during cluster creation.)
+   * **Scenario 1:**  Existing HDInsight clusters without custom virtual network (No virtual network provided during cluster creation).
 
      * No immediate disruption until Mar 31, 2025. However, we strongly recommend re-creating the cluster before Mar 31, 2025 to avoid potential disruption.
 
-   * **Scenario 2:** Existing HDInsight clusters with custom virtual network.
+   * **Scenario 2:** Existing HDInsight clusters with custom virtual network (Used your own VNet for cluster creation).
 
      * No immediate disruption until Mar 31, 2025. However, we strongly recommend re-creating the cluster before Mar 31, 2025 to avoid potential disruption.
 
 ### New cluster creation
 
-* **Scenario 1:** HDInsight clusters without custom virtual network. (No virtual network provided during cluster creation)
+* **Scenario 1:** HDInsight clusters without custom virtual network (No virtual network selected during cluster creation).
 
    * In this case, no impact. You can recreate the cluster directly.
 
-* **Scenario 2:** HDInsight clusters with custom virtual network. (Providing your own VNet during cluster creation)
+* **Scenario 2:** HDInsight clusters with custom virtual network (Using your own VNet during cluster creation).
 
    * In this case, there are two options to create a cluster
 
       **Approach 1:** Create the cluster with a new subnet
 
-      1. Choose the outbound connectivity for your cluster, and  follow this document [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and choose one method to provide outbound connectivity for the new cluster. The most recommended way is to attach a NAT gateway and a Network Security Group (NSG) to the subnet.
+      1. Choose the outbound connectivity for your cluster
+
+         Follow this document [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and choose one method to provide outbound connectivity for the new cluster. The most recommended way is to attach a NAT gateway and a Network Security Group (NSG) to the subnet.
 
-      1. (Optional) Create a new NAT gateway and a new network security group (NSG).
+      1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones.
 
          > [!NOTE]
-         > You can associate an existing NAT gateway and NSG or the newly created ones.
-         >
-         > Follow the docs [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
-         >
-         > You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
+         > You can use an existing NAT gateway and NSG.
+         
+         Follow the docs [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
+         You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
 
       1. Create a new subnet and associate the subnet with the NAT gateway and network security group.
 
@@ -58,23 +59,24 @@ This transition is done in line with the announcement of retirement of Azure bas
 
          :::image type="content" source="./media/load-balancer-migration-guidelines/create-hdinsight-cluster.png" alt-text="Screenshot showing how to create a HDInsight cluster." border="true" lightbox="./media/load-balancer-migration-guidelines/create-hdinsight-cluster.png":::  
 
-     **Approach 2: Use the existing subnet**
+     **Approach 2:** Create the cluster using the existing subnet
 
-      To upgrade your existing custom virtual network to integrate with Azure standard load balancer (which HDInsight clusters use by default now), see, [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections) to provide outbound connectivity for the cluster. 
+      Your existing virtual network may be incompatible with Azure Standard Load Balancer, to upgrade your existing custom virtual network to integrate with Azure standard load balancer (which HDInsight clusters use by default now), see, [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections) to provide outbound connectivity for the cluster. 
 
       The most recommended way is to attach a network security group and a NAT gateway to the subnet. Since the existing subnet which has HDInsight clusters with Azure basic load balancers can't be associated with an NAT gateway due to incompatibility with basic load balancer, there are two scenarios:
 
-#### Case 1: Existing subnet has no HDInsight clusters with Azure Basic load balancers
+#### Case 1: Existing subnet has no HDInsight clusters with Azure Basic Load Balancers
 
    Follow these steps:
 
-   1. Create a new NAT gateway and a new network security group or use the existing ones.
+   1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones.
 
       > [!NOTE]
-      > You could associate an existing NAT gateway and NSG or the newly created ones.
-      > Follow this document [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
-      > 
-      > You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
+      > You could use an existing NAT gateway and NSG.
+
+      Follow this document [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
+       
+      You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
 
 
 1. Associate the NAT gateway with your subnet along with a network security group.
@@ -92,21 +94,22 @@ This transition is done in line with the announcement of retirement of Azure bas
             
    Consider one of these methods:
 
-   * **Approach 1:** The most recommended way is to associate a NAT gateway to the subnet along with network security group.
+   * **Method 1:** The most recommended way is to associate a NAT gateway to the subnet along with network security group.
 
-      According to [Azure NAT Gateway frequently asked questions](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway), the subnet with NAT gateway and Azure standard load balancer isn't compatible.
+      According to [Azure NAT Gateway frequently asked questions](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway), NAT gateway is incomaptible with Azure basic load balancer.
 
       To associate with a NAT Gateway, perform the following steps.
 
       1. Delete all the existing HDInsight clusters with Azure basic load balancers in this subnet.
 
-      1. Create a new NAT gateway and a new network security group or use the existing ones.
+      1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones.
          
          > [!NOTE]
-         > You could associate an existing NAT gateway and NSG or use the newly created ones.
-         > Follow this document [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
-         > 
-         > You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
+         > You could use an existing NAT gateway and NSG.
+         
+         Follow this document [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
+          
+         You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
            
        1. Associate the subnet with the NAT gateway and network security group.
 
@@ -119,9 +122,9 @@ This transition is done in line with the announcement of retirement of Azure bas
          :::image type="content" source="./media/load-balancer-migration-guidelines/virtual-network.png" alt-text="Screenshot showing virtual network." border="true" lightbox="./media/load-balancer-migration-guidelines/virtual-network.png":::
 
 
-   * **Approach 2:** Select option other than **Associate a NAT gateway to the subnet** provided in [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and follow the instruction for the selected option.
+   * **Method 2:** Select option other than **Associate a NAT gateway to the subnet** provided in [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and follow the instruction for the selected option.
 
-   * **Approach 3:** Create a new subnet and then create the cluster with the new subnet.
+   * **Method 3:** Create a new subnet and then create the cluster with the new subnet.
 
 ## Next steps