Skip to content

Commit b99446f

Browse files
authored
Apply suggestions from code review
Implement Acrolinx changes.
1 parent 820f5c9 commit b99446f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/load-balancer/load-balancer-outbound-connections.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Calculate ports per instance as follows:
5050

5151
**Number of frontend IPs * 64K / Number of backend instances**
5252

53-
If you have Virtual Machine Scale Sets in the backend, it's recommended to allocate ports by "maximum number of backend instances". If more VMs are added to the backend than remaining SNAT ports allowed, scale out of virtual machine scale set could be blocked, or the new VMs won't receive sufficient SNAT ports.
53+
If you have Virtual Machine Scale Sets in the backend, it's recommended to allocate ports by "maximum number of backend instances". If more VMs are added to the backend than remaining SNAT ports allowed, scale out of Virtual Machine Scale Sets could be blocked, or the new VMs won't receive sufficient SNAT ports.
5454

5555
For more information about outbound rules, see [Outbound rules](outbound-rules.md).
5656

@@ -89,7 +89,7 @@ Default outbound access is when An Azure resource is allocated a minimal number
8989

9090
- doesn't have a public IP associated to it.
9191
- doesn't have a load balancer with outbound Rules in front of it.
92-
- isn't part of virtual machine scale sets flexible orchestration mode.
92+
- isn't part of Virtual Machine Scale Sets flexible orchestration mode.
9393
- doesn't have a NAT gateway resource associated to its subnet.
9494

9595
Some other examples of default outbound access are:

0 commit comments

Comments
 (0)