Update route-maps-about.md

Author: cfields475

articles/virtual-wan/route-maps-about.md

@@ -10,14 +10,10 @@ ms.author: cherylmc
 ms.custom: references_regions
 
 ---
-# About Route-maps for virtual hubs (Preview)
+# About Route-maps for virtual hubs
 
 Route-maps is a feature that gives you the ability to control route advertisements and routing for Virtual WAN virtual hubs. Route-maps lets you have more control of the routing  that enters and leaves Azure Virtual WAN site-to-site (S2S) VPN connections, User VPN point-to-site (P2S) connections, ExpressRoute (ER) connections, and virtual network (VNet) connections. Route-maps can be configured using the Azure portal. For configuration steps, see [How to configure Route-maps](route-maps-how-to.md).
 
-> [!IMPORTANT]
-> [!INCLUDE [Preview text](../../includes/virtual-wan-route-maps-preview.md)]
->
-
 ## Why use Route-maps?
 
 Some of the key benefits of using Route-maps are:
@@ -52,7 +48,6 @@ Route-maps lets you perform route aggregation, route filtering, and gives you th
 
 Before using Route-maps, take into consideration the following limitations:
 
-* During Preview, hubs that are using Route-maps must be deployed in their own virtual WANs.
 * When using Route-maps to summarize a set of routes, the hub router strips the *BGP Community* and *AS-PATH* attributes from those routes. This applies to both inbound and outbound routes.
 * When using Route-maps, [do not use private ASNs for AS prepending](../expressroute/expressroute-optimize-routing.md) (note that the referenced article focuses on ExpressRoute Microsoft peerings, but the same applies for ExpressRoute private peerings).
 
@@ -61,7 +56,7 @@ Before using Route-maps, take into consideration the following limitations:
   * Private ASNs: 65515, 65517, 65518, 65519, 65520
 * When using Route-maps, do not remove the Azure BGP communities:
   *  65517:12001, 65517:12002, 65517:12003, 65517:12005, 65517:12006, 65518:65518, 65517:65517, 65517:12076, 65518:12076, 65515:10000, 65515:20000
-* You can't apply Route-maps to connections between on-premises and SD-WAN/Firewall NVAs in the virtual hub. These connections aren't supported during Preview. You can still apply route-maps to other supported connections when an NVA in the virtual hub is deployed. This doesn't apply to the Azure Firewall, as the routing for Azure Firewall is provided through Virtual WAN [routing intent features](how-to-routing-policies.md).
+* You can't apply Route-maps to connections between on-premises and SD-WAN/Firewall NVAs in the virtual hub. You can still apply route-maps to other supported connections when an NVA in the virtual hub is deployed. This doesn't apply to the Azure Firewall, as the routing for Azure Firewall is provided through Virtual WAN [routing intent features](how-to-routing-policies.md).
 * Route-maps only supports 2-byte ASN numbers.
 * The point-to-site (P2S) Multipool feature isn't currently supported with Route-maps.
 * Modifying the *Default* route is only supported when the default route is learned from on-premises or an NVA.
@@ -111,7 +106,7 @@ Match conditions are used to select a set of routes. Once those routes are selec
 
 ### Supported configurations for route-map rules
 
-This section shows the match conditions and actions supported for the Route-maps Preview.
+This section shows the match conditions and actions supported in the Route-maps feature.
 
 #### Match conditions