Merge pull request #113833 from skishen525/patch-32

Update virtual-wan-global-transit-network-architecture.md

Author: PRMerger10

articles/virtual-wan/virtual-wan-global-transit-network-architecture.md

@@ -96,10 +96,9 @@ Branches can be connected to an Azure virtual WAN hub using ExpressRoute circuit
 
 This option lets enterprises leverage the Azure backbone to connect branches. However, even though this capability is available, you should weigh the benefits of connecting branches over Azure Virtual WAN vs. using a private WAN.  
 
-### Disabling Branch-to-Branch Connectivity in Virtual WAN
-Virtual WAN can be configured to disable Branch-to-Branch connectivity. This configuation will block route propagation between VPN (S2S and P2S) and Express Route connected sites. This configuration will not affect branch-to-Vnet and Vnet-to-Vnet route propogation and connectivity.
-
-In the Azure Portal, under Virtual WAN Configuration menu, Choose Setting: Branch-to-Branch -> Disabled. 
+> [!NOTE]
+> Disabling Branch-to-Branch Connectivity in Virtual WAN -
+> Virtual WAN can be configured to disable Branch-to-Branch connectivity. This configuation will block route propagation between VPN (S2S and P2S) and Express Route connected sites. This configuration will not affect branch-to-Vnet and Vnet-to-Vnet route propogation and connectivity. To configure this setting using Azure Portal: Under Virtual WAN Configuration menu, Choose Setting: Branch-to-Branch - Disabled. 
 
 ### Remote User-to-VNet (c)