Skip to content

Commit 520f477

Browse files
committed
standardize capitalization of Standard
1 parent ee13b2a commit 520f477

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Azure NetApp Files volumes are designed to be contained in a special purpose sub
3333

3434
### Supported regions
3535

36-
Azure NetApp Files standard network features are supported for the following regions:
36+
Azure NetApp Files Standard network features are supported for the following regions:
3737

3838
* Australia Central
3939
* Australia Central 2
@@ -161,7 +161,7 @@ The following diagram illustrates an Azure-native environment with cross-region
161161

162162
:::image type="content" source="../media/azure-netapp-files/azure-native-cross-region-peering.png" alt-text="Diagram depicting Azure native environment setup with cross-region VNet peering." lightbox="../media/azure-netapp-files/azure-native-cross-region-peering.png":::
163163

164-
With the standard network feature, VMs are able to connect to volumes in another region via global or cross-region VNet peering. The above diagram adds a second region to the configuration in the [local VNet peering section](#vnet-peering). For VNet 4 in this diagram, an Azure NetApp Files volume is created in a delegated subnet and can be mounted on VM5 in the application subnet.
164+
With Standard network features, VMs are able to connect to volumes in another region via global or cross-region VNet peering. The above diagram adds a second region to the configuration in the [local VNet peering section](#vnet-peering). For VNet 4 in this diagram, an Azure NetApp Files volume is created in a delegated subnet and can be mounted on VM5 in the application subnet.
165165

166166
In the diagram, VM2 in Region 1 can connect to Volume 3 in Region 2. VM5 in Region 2 can connect to Volume 2 in Region 1 via VNet peering between Region 1 and Region 2.
167167

0 commit comments

Comments
 (0)