Skip to content

Commit 66f2ed4

Browse files
authored
Merge pull request #103304 from kasimrehman/patch-10
Update virtual-wan-global-transit-network-architecture.md
2 parents 327c37c + a19be59 commit 66f2ed4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -112,9 +112,9 @@ The Remote User-to-branch path lets remote users who are using a point-to-site c
112112
The VNet-to-VNet transit enables VNets to connect to each other in order to interconnect multi-tier applications that are implemented across multiple VNets. Optionally, you can connect VNets to each other through VNet Peering and this may be suitable for some scenarios where transit via the VWAN hub isn't necessary.
113113

114114

115-
## <a name="DefaultRoute"></a>Force tunneling and default route
115+
## <a name="DefaultRoute"></a>Forced tunneling and default route
116116

117-
Force Tunneling can be enabled by configuring the enable default route on a VPN, ExpressRoute, or Virtual Network connection in Virtual WAN.
117+
Forced Tunneling can be enabled by configuring the enable default route on a VPN, ExpressRoute, or Virtual Network connection in Virtual WAN.
118118

119119
A virtual hub propagates a learned default route to a virtual network/site-to-site VPN/ExpressRoute connection if enable default flag is 'Enabled' on the connection.
120120

0 commit comments

Comments
 (0)