modification for private subnets, modification for secondary configs

Author: brianlehr

articles/load-balancer/load-balancer-floating-ip.md

@@ -145,7 +145,7 @@ sudo ufw allow 80/tcp
 ```
 </details>
 
-## <a name = "limitations"></a>Limitations
+## <a name = "limitations"></a>Limitations 
 
 -  With Floating IP enabled on a load balancing rule, your application must use the primary IP configuration of the network interface for outbound.
 -  If your application binds to the frontend IP address configured on the loopback interface in the guest OS, Azure's outbound won't rewrite the outbound flow, and the flow fails. Review [outbound scenarios](load-balancer-outbound-connections.md).

articles/virtual-network/ip-services/default-outbound-access.md

@@ -109,7 +109,7 @@ There are multiple ways to turn off default outbound access. The following secti
 >[!Important]
 > When a load balancer backend pool is configured by IP address, it will use default outbound access due to an ongoing known issue. For secure by default configuration and applications with demanding outbound needs, associate a NAT gateway to the VMs in your load balancer's backend pool to secure traffic. See more on existing [known issues](../../load-balancer/whats-new.md#known-issues).
 
-## If I need outbound access, what is the recommended way?
+## If I need outbound access, what is the recommended way? 
 
 NAT gateway is the recommended approach to have explicit outbound connectivity. A firewall can also be used to provide this access.