repair item

Author: siddomala

articles/route-server/route-server-faq.md

@@ -73,6 +73,10 @@ Azure Route Server supports ***NO_ADVERTISE*** BGP community. If a network virtu
 
 Yes. If a VNet peering is created between your hub VNet and spoke VNet, Azure Route Server will perform a BGP soft reset by sending route refresh requests to all its peered NVAs. If the NVAs do not support BGP route refresh, then Azure Route Server will perform a BGP hard reset with the peered NVAs, which may cause connectivity disruption for traffic traversing the NVAs. 
 
+### How is the 1000 route limit calculated on a BGP peering session between an NVA and Azure Route Server?
+
+Today, Route Server can accept a maximum of 1000 routes from a single BGP peer. When processing BGP route updates, this limit is calculated as the number of current routes learnt from a BGP peer plus the number of routes coming in the BGP route update. For example, if an NVA initially advertises 501 routes to Route Server and later re-advertises these 501 routes in a BGP route update, Route Server would calculate this as 1002 routes and tear down the BGP session. 
+
 ### What Autonomous System Numbers (ASNs) can I use?
 
 You can use your own public ASNs or private ASNs in your network virtual appliance (NVA). You can't use ASNs reserved by Azure or IANA.

articles/virtual-wan/monitor-virtual-wan-reference.md

@@ -24,10 +24,10 @@ The following metric is available for virtual hub router within a virtual hub:
 | --- | --- |
 | **Virtual Hub Data Processed** | Data on how much traffic traverses the virtual hub router in a given time period. Only the following flows use the virtual hub router: VNet to VNet (same hub and interhub) and VPN/ExpressRoute branch to VNet (interhub). If a virtual hub is secured with routing intent, then these flows traverse the firewall instead of the hub router. |
 | **Routing Infrastructure Units** | The virtual hub's routing infrastructure units (RIU). The virtual hub's RIU determines how much bandwidth the virtual hub router can process for flows traversing the virtual hub router. The hub's RIU also determines how many VMs in spoke VNets the virtual hub router can support. For more details on routing infrastructure units, see [Virtual Hub Capacity](hub-settings.md#capacity).
-| **Spoke VM Utilization** | The number of deployed spoke VMs as a percentage of the total number of spoke VMs that the hub's routing infrastructure units can support. For example, if the hub's RIU is set to 2 (which supports 2000 spoke VMs), and 1000 VMs are deployed across spoke VNets, then this metric will display as 50%.  |
+| **Spoke VM Utilization** | The approximate number of deployed spoke VMs as a percentage of the total number of spoke VMs that the hub's routing infrastructure units can support. For example, if the hub's RIU is set to 2 (which supports 2000 spoke VMs), and 1000 VMs are deployed across spoke VNets, then this metric's approximate value will be 50%.  |
 
 > [!NOTE]
-> As of March 28, 2024, the backend functionality for the Routing Infrastructure Units and Spoke VM Utilization metrics are still rolling out. As a result, even if you see these metrics displayed in Portal, the actual values of these metrics might appear as 0. The backend functionality of these metrics is aimed to finish rolling out within the next several weeks, which will ensure the proper values are emitted. 
+> As of March 28, 2024, the backend functionality for the Routing Infrastructure Units and Spoke VM Utilization metrics are still rolling out. As a result, even if you see these metrics displayed in Portal, the actual values of these metrics might appear as 0. The backend functionality of these metrics is aimed to finish rolling out swithin the next several weeks, which will ensure the proper values are emitted. 
 > 
 
 ### <a name="s2s-metrics"></a>Site-to-site VPN gateway metrics

articles/virtual-wan/scenario-route-through-nva.md

@@ -114,7 +114,7 @@ Virtual WAN  doesn't support a scenario where VNets 5,6 connect to virtual hub a
    :::image type="content" source="./media/routing-scenarios/nva/nva-static-expand.png" alt-text="Example":::
 
    > [!NOTE]
-   > To simplify the routing and to reduce the changes in the Virtual WAN hub route tables, we recommend the new BGP peering with Virtual WAN hub (preview). For more information, see the following articles: 
+   > To simplify the routing and to reduce the changes in the Virtual WAN hub route tables, we recommend the new BGP peering with Virtual WAN hub. For more information, see the following articles: 
    >* [Scenario: BGP peering with a virtual hub](scenario-bgp-peering-hub.md) 
    >* [How to create BGP peering with virtual hub - Azure portal](create-bgp-peering-hub-portal.md)
    >