Merge pull request #247868 from mahipdeora/main

updates

Author: prmerger-automator[bot]

articles/load-balancer/backend-pool-management.md

@@ -224,7 +224,7 @@ az vm create \
   * You can configure IP based and NIC based backend pools for the same load balancer. You can’t create a single backend pool that mixes backed addresses targeted by NIC and IP addresses within the same pool.
   * A virtual machine in the same virtual network as an internal load balancer can't access the frontend of the ILB and its backend VMs simultaneously.
   * Internet routing preference IPs are currently not supported with IP based backend pools. Any Internet routing preference IPs in IP based backend pools will be billed and routed via the default Microsoft global network.
-  * If backend pools are constantly changing (due to the constant addition or removal of backend resources), there is a chance that existing connections may get rehashed. During this process, the backend resource may send a reset signal to the source. A workaround is to utilize retries to avoid the reset signal.
+  * If backend pools are constantly changing (due to the constant addition or removal of backend resources). This may cause reset signals sent back to the source from the backend resource. As a workaround, you can use retries.
 
 >[!Important]
 > When a backend pool is configured by IP address, it will behave as a Basic Load Balancer with default outbound enabled. For secure by default configuration and applications with demanding outbound needs, configure the backend pool by NIC.