MicrosoftDocs
diff --git a/‎articles/hdinsight/load-balancer-migration-guidelines.md
Lines changed: 1 addition & 4 deletions b/‎articles/hdinsight/load-balancer-migration-guidelines.md
Lines changed: 1 addition & 4 deletions
diff --git a/‎articles/hdinsight/media/load-balancer-migration-guidelines/create-hdinsight-cluster.png
11.3 KB b/‎articles/hdinsight/media/load-balancer-migration-guidelines/create-hdinsight-cluster.png
11.3 KB
diff --git a/‎articles/hdinsight/media/load-balancer-migration-guidelines/security-networking.png
11.3 KB b/‎articles/hdinsight/media/load-balancer-migration-guidelines/security-networking.png
11.3 KB
diff --git a/‎articles/hdinsight/media/load-balancer-migration-guidelines/viritual-network.png
11.2 KB b/‎articles/hdinsight/media/load-balancer-migration-guidelines/viritual-network.png
11.2 KB
@@ -116,7 +116,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.