Skip to content

Commit 4b4764f

Browse files
authored
Corrected a minor format
Corrected a minor format
1 parent bc120d1 commit 4b4764f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ This transition is done in line with the announcement of retirement of Azure bas
2626

2727
### New cluster creation
2828

29-
There are several ways provided in the document [Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections)that could provide outbound connectivity for a cluster. The only compatible way with HDInsight is to associate a NAT gateway to the subnet, which supports auto-scaling features of HDInsight clusters.
29+
There are several ways provided in the document [Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections) that could provide outbound connectivity for a cluster. The only compatible way with HDInsight is to associate a NAT gateway to the subnet, which supports auto-scaling features of HDInsight clusters.
3030

3131
* **Scenario 1:** HDInsight clusters without custom virtual network (Creating cluster without any virtual network).
3232

@@ -38,7 +38,7 @@ There are several ways provided in the document [Source Network Address Translat
3838

3939
**Approach 1:** Create the cluster with a new subnet
4040

41-
1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones.
41+
1. Create a new NAT gateway and a new Network Security Group (NSG) or use the existing ones.
4242

4343
> [!NOTE]
4444
> You can use an existing NAT gateway and NSG.

0 commit comments

Comments
 (0)