Merge pull request #97741 from skishen525/patch-25

Update virtual-wan-faq-include.md

Author: PRMerger7

includes/virtual-wan-faq-include.md

@@ -108,7 +108,9 @@ You can connect a VNet in a different region than your virtual WAN.
 
 ### Can spoke VNets connected to a virtual hub communicate with each other?
 
-Yes. Spoke VNets can communicate directly via Virtual Network Peering. For more information, see [Virtual Network Peering](../articles/virtual-network/virtual-network-peering-overview.md). We also support VNets communicating transitively through the hub.
+Yes. Standard Virtual WAN supports Vnet to Vnet transitive connectivity via the Virtual WAN hub that the Vnets are connected to. In Virtual WAN terminology, we refer to these paths as “local Virtual WAN VNet transit” for VNets connected to a Virtual Wan Hub within a single region, and “global Virtual WAN VNet transit” for VNets connected through multiple Virtual WAN Hubs across two or more regions. VNet transit supports up to 3 Gbps of throughput during public preview. Throughput will expanded when global transit goes GA.   
+
+For some scenarios, spoke Vnets can also be directly peered with each other using [Virtual Network Peering](../articles/virtual-network/virtual-network-peering-overview.md) in addition to local or global Virtual WAN VNet transit. In this case, Vnet Peering takes precedence over the transitive connection via the Virtual WAN hub. 
 
 ### What is a branch connection to Azure Virtual WAN?