Update load-balancer-migration-guidelines.md

Corrected the H2, H2 titles.

Author: sreekzz

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

@@ -1,14 +1,13 @@
 ---
-title: Load balancer migration guidelines in Azure HDInsight on AKS
-description: Guidelines to perform load balancer migration in Azure HDInsight on AKS
+title: Load balancer migration guidelines for Azure HDInsight on AKS
+description: Guidelines to perform load balancer migration for Azure HDInsight on AKS
 ms.service: azure-hdinsight
 ms.topic: how-to
 ms.date: 09/25/2024
 ---
 
 # Load balancer migration guidelines
 
-
 This article describes the details about the impact on HDInsight clusters and the necessary steps required as HDInsight service is transitioning to use standard load balancers for all its cluster configurations.
 
 This transition is done in line with the announcement of retirement of Azure basic load balancer by 30 September 2025 and no support for new deployment by Mar 31, 2025. For more information, see [Azure Basic Load Balancer retires on 30 September 2025. Upgrade to Standard Load Balancer](https://azure.microsoft.com/updates/azure-basic-load-balancer-will-be-retired-on-30-september-2025-upgrade-to-standard-load-balancer).
@@ -61,7 +60,7 @@ In this case, there are two options to create a cluster
 
 To upgrade your existing custom virtual network to integrate Azure standard load balancer (which is HDInsight clusters use by default), 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:
 
-Scenario 1: Existing subnet has no HDInsight clusters with Azure basic load balancer
+### Scenario 1: Existing subnet has no HDInsight clusters with Azure basic load balancer
 
 1. (Optional) Create a new NAT gateway and a new network security group.
 
@@ -83,7 +82,7 @@ Scenario 1: Existing subnet has no HDInsight clusters with Azure basic load bala
     > [!NOTE]
     > If you are unable to find the NAT gateway, see, [FAQ of the NAT gateway (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). 
 
-## Scenario 2: The existing subnet has HDInsight clusters with basic load balancers.
+### Scenario 2: The existing subnet has HDInsight clusters with basic load balancers.
 
 Approach 1: The most recommended way is to associate a NAT gateway to the subnet along with Network security group.
 
@@ -116,4 +115,4 @@ To associate with a NAT Gateway, perform the following steps.
 
 **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.
 
-**Approach 3:** Create a new subnet and then create the cluster with the new subnet.
+**Approach 3:** Create a new subnet and then create the cluster with the new subnet.