Overview statement update

Author: reyandap

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

@@ -13,9 +13,9 @@ Customer intent: As someone with a networking background, I want to understand w
 
 # About Azure Virtual WAN
 
-Azure Virtual WAN is a networking service that provides optimized and automated branch connectivity to, and through, Azure. Azure regions serve as hubs that you can choose to connect your branches to. You can leverage the Azure backbone to also connect branches and enjoy branch-to-VNet connectivity. We have a list of partners that support connectivity automation with Azure Virtual WAN VPN. For more information, see the [Virtual WAN partners and locations](virtual-wan-locations-partners.md) article.
+Azure Virtual WAN is a networking service that brings many networking, security and routing functionalities together to provide a single operational interface. These functionalities include Branch connectivity ( via connectivity automation from Virtual WAN Partner devices such as SD-WAN or VPN CPE) , Site-to-site VPN connectivity, Remote User VPN (Point-to-site) connectivity, Private (ExpressRoute) connectivity, Intra cloud connectivity (Transitive connectivity for Virtual Networks), VPN ExpressRoute Interconnectivity, Routing, Azure firewall, Encryption for private connectivity etc. You do not have to have all of these use cases to start using Virtual WAN. You can simply get started with just one use case and adjust your network as it evolves. The Virtual WAN architecture is a hub and spoke architecture with scale and performance built-in for branches (VPN/SD-WAN devices), users (Azure VPN/OpenVPN/IKEv2 Clients), ExpressRoute circuits, and Virtual Networks. It enables [global transit network architecture](virtual-wan-global-transit-network-architecture.md) where the cloud hosted network 'hub' enables transitive connectivity between endpoints that may be distributed across different types of 'spokes'.
 
-Azure Virtual WAN brings together many Azure cloud connectivity services such as site-to-site VPN, User VPN (point-to-site), and ExpressRoute into a single operational interface. Connectivity to Azure VNets is established by using virtual network connections. It enables [global transit network architecture](virtual-wan-global-transit-network-architecture.md) based on a classic hub-and-spoke connectivity model where the cloud hosted network 'hub' enables transitive connectivity between endpoints that may be distributed across different types of 'spokes'.
+Azure regions serve as hubs that you can choose to connect to. All hubs are connected in full mesh in a Standard Virtual WAN making it easy for the user to use the Microsoft backbone for any-to-any (any spoke) connectivity. For spoke connectivity with SD-WAN/VPN devices, users can either manually set it up in Azure Virtual WAN or use the Virtual WAN CPE (SD-WAN/VPN) partner solution to set up connectivity to Azure. We have a list of partners that support connectivity automation (ability to export the device info into Azure, download the Azure configuration and establish connectivity ) with Azure Virtual WAN. For more information, see the [Virtual WAN partners and locations](virtual-wan-locations-partners.md) article. 
 
 ![Virtual WAN diagram](./media/virtual-wan-about/virtualwan1.png)