Update load-balancer-outbound-connections.md

Rephrase port reuse explanation for TCP connections

Author: thisisanniefang

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

@@ -150,9 +150,9 @@ For more information about connection pooling with Azure App Service, see [Troub
 
 New outbound connections to a destination IP fail when port exhaustion occurs. Connections succeed when a port becomes available. This exhaustion occurs when the 64,000 ports from an IP address are spread thin across many backend instances. For guidance on mitigation of SNAT port exhaustion, see the [troubleshooting guide](./troubleshoot-outbound-connection.md).  
 
-For TCP connections, the load balancer uses a single SNAT port for every destination IP and port. This multiuse enables multiple connections to the same destination IP with the same SNAT port. This multiuse is limited if the connection isn't to different destination ports.
+For TCP connections, the load balancer uses a single SNAT port for every destination IP and port. This also enables the load balancer to reuse the same SNAT port for multiple connections, as long as the destination IP and port is unique. For scenarios involving multiple connections to the same destination IP and port, unique SNAT ports will be consumed and reuse will not apply.
 
-For UDP connections, the load balancer uses a **port-restricted cone NAT** algorithm, which consumes one SNAT port per destination IP whatever the destination port. 
+For UDP connections, the load balancer uses a **port-restricted cone NAT** algorithm, which consumes one SNAT port per destination IP, regardless of the destination port. 
 
 A port is reused for an unlimited number of connections. The port is only reused if the destination IP or port is different.