Merge pull request #232542 from halkazwini/patch-29

Tweak

Author: prmerger-automator[bot]

articles/route-server/next-hop-ip.md

@@ -1,6 +1,6 @@
 ---
 title: Next Hop IP Support
-description: Learn about Next Hop IP support for Azure Route Server.
+description: Learn how to use Next Hop IP feature in Azure Route Server to peer with network virtual appliances (NVAs) behind an internal load balancer.
 author: halkazwini
 ms.author: halkazwini
 ms.service: route-server
@@ -11,7 +11,7 @@ ms.custom: template-concept
 
 # Next Hop IP support
 
-With the support for Next Hop IP in [Azure Route Server](overview.md), you can peer with NVAs deployed behind an Azure Internal Load Balancer (ILB). The internal load balancer lets you set up active-passive connectivity scenarios and leverage load balancing to improve connectivity performance.
+With the support for Next Hop IP in [Azure Route Server](overview.md), you can peer with network virtual appliances (NVAs) that are deployed behind an Azure internal load balancer. The internal load balancer lets you set up active-passive connectivity scenarios and leverage load balancing to improve connectivity performance.
 
 :::image type="content" source="./media/next-hop-ip/route-server-next-hop.png" alt-text="Diagram of two NVAs behind a load balancer and a Route Server.":::
 
@@ -23,7 +23,7 @@ You can deploy a set of active-passive NVAs behind an internal load balancer to
 
 You can deploy a set of active-active NVAs behind an internal load balancer to optimize connectivity performance. With the support for Next Hop IP, you can define the next hop for both NVA instances as the IP address of the internal load balancer. Traffic that reaches the load balancer will be sent to both NVA instances.
 > [!NOTE]
-> * Active-Active NVA connectivity may result in asymmetric routing.
+> * Active-active NVA connectivity may result in asymmetric routing.
 
 ## Next hop IP configuration