Update load-balancer-ha-ports-overview.md

Minor wording fixes

Author: thisisanniefang

articles/load-balancer/load-balancer-ha-ports-overview.md

@@ -89,9 +89,9 @@ You can configure **one** public standard load balancer resource for the backend
 
 - When the load balancer backend pool contains instances that have multiple NICs with only one IP configuration on each NIC
 
-- Dual-stack scenarios, where each backend instance only has one NIC and only one IPv4 and IPv6 configuration on each NIC. Note that flow symmetry is only guaranteed for IPv4 and IPv6 flows independently, as these IP configurations are presumably configured in two separate backend pools and frontend IP configuration.
+- Dual-stack scenarios, where each backend instance only has one NIC and only one IPv4 and IPv6 configuration on each NIC. Please note that flow symmetry is only guaranteed for IPv4 and IPv6 flows independently, as these IP configurations would be configured with two separate backend pools and frontend IP configurations, respectively.
 
-Flow symmetry isn't guaranteed in any scenarios that involve two or more load balancer components, such as across two different load balancers or multiple backend pools. Since traffic is distributed based on load balancing rules, which make independent decisions and aren't coordinated, flow symmetry cannot be guaranteed in such scenarios. As a result, flow symmetry isn't supported when placing NVAs between a public and internal load balancer. If you need flow symmetry in such scenarios, consider leveraging [Gateway Load Balancer](gateway-overview.md) instead.
+Flow symmetry isn't guaranteed in any scenarios that involve two or more load balancer components, such as across two different load balancers, multiple backend pools, or multiple frontend IP configurations. Since traffic is distributed based on load balancing rules, which make independent decisions and aren't coordinated, flow symmetry cannot be guaranteed in such scenarios. As a result, flow symmetry isn't supported when placing NVAs between a public and internal load balancer. If you need flow symmetry in such scenarios, consider leveraging [Gateway Load Balancer](gateway-overview.md) instead.
 
 
 ## Limitations