Merge pull request #294363 from halkazwini/rs-hop

Freshness: Next hop IP support

Author: prmerger-automator[bot]

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

@@ -6,7 +6,7 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: azure-route-server
 ms.topic: concept-article
-ms.date: 02/13/2024
+ms.date: 02/10/2025
 
 #CustomerIntent: As an Azure administrator, I want to use the frontend IP address of the load balancer as the next hop IP so packets are routed to the load balancer to get to the NVAs that are in the backend pool.
 ---
@@ -18,7 +18,7 @@ With the support for Next hop IP in Azure Route Server, you can peer with networ
 :::image type="content" source="./media/next-hop-ip/route-server-next-hop.png" alt-text="Diagram of a Route Server peered with two NVAs behind an internal load balancer.":::
 
 > [!NOTE] 
-> The load balancer must be in the same region as the Route Server. If the load balancer is in a different region than the Route Server, then connectivity to these NVAs will not be functional.  
+> The load balancer must be in the same region as the Route Server. If the load balancer is in a different region than the Route Server, then connectivity to the NVAs won't be functional.  
 
 ## Active-passive NVA connectivity
 
@@ -29,13 +29,13 @@ 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 is sent to both NVA instances.
 
 > [!NOTE]
-> Active-active NVA connectivity may result in asymmetric routing.
+> Active-active NVA connectivity might result in asymmetric routing.
 
 ## Next hop IP configuration
 
 Next hop IP addresses are set up in the BGP configuration of the target NVAs. The Next hop IP isn't part of the Azure Route Server configuration.
 
 ## Related content
 
-- [Configure Azure Route Server](quickstart-configure-route-server-portal.md).
-- [Monitor Azure Route Server](monitor-route-server.md).
+- [Configure Azure Route Server](quickstart-configure-route-server-portal.md)
+- [Monitor Azure Route Server](monitor-route-server.md)