Skip to content

Commit 71f7d8c

Browse files
authored
Apply suggestions from code review
1 parent f00a6ce commit 71f7d8c

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/reliability/reliability-virtual-network.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,7 @@ Virtual networks themselves aren't usually affected by transient faults. However
6161

6262
[!INCLUDE [AZ support description](includes/reliability-availability-zone-description-include.md)]
6363

64-
A virtual network deployed in a region spans all availability zones within that region. Similarly, subnets within each virtual network span all availability zones within the region. User intervention isn't required to enable this support.
65-
64+
A virtual network, as well as the subnets within that virtual network, spans across all availability zones within the region in which it's deployed. You do not have to configure anything to enable this support.
6665
You don't need to divide your virtual networks or subnets by availability zones to accommodate zonal resources. For example, if you configure a zonal VM, you don't have to take into consideration the virtual network when selecting the availability zone for the VM. The same is true for other zonal resources.
6766

6867
### Region support
@@ -99,7 +98,7 @@ Azure Virtual Network is a single-region service. If the region becomes unavaila
9998

10099
### Alternative multi-region approaches
101100

102-
You can create virtual networks in multiple regions, and you can optionally *peer* them together to connect them.
101+
You can create virtual networks in multiple regions. You can also choose to connect those networks by *peering* them together.
103102

104103
By creating virtual networks and other resources in multiple regions, you can be resilient to regional outages. However, you need to consider many factors, including:
105104

0 commit comments

Comments
 (0)