Skip to content

Commit 6e37014

Browse files
committed
fix typo
1 parent a071bc2 commit 6e37014

File tree

6 files changed

+7
-39
lines changed

6 files changed

+7
-39
lines changed

articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ Before creating an SMB volume, you need to create an Active Directory connection
119119
120120
* Specify a unique **share name** for the volume. This share name is used when you create mount targets. The requirements for the share name are as follows:
121121
- For volumes not in an availability zone or volumes in the same availability zone, it must be unique within each subnet in the region.
122-
- For volumes in availability zones, it must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information and, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
122+
- For volumes in availability zones, it must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
123123
- It can contain only letters, numbers, or dashes (`-`).
124124
- The length must not exceed 80 characters.
125125

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,8 +113,8 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
113113
* Select **NFS** as the protocol type for the volume.
114114

115115
* Specify a unique **file path** for the volume. This path is used when you create mount targets. The requirements for the path are as follows:
116-
- For volumes not in an availability zone or volumes in the same availability zone, it must be unique within each subnet in the region. This feature is currently in **preview** and requires you to register the feature. For more information and, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
117-
- For volumes in availability zones, it must be unique within each availability zone.*
116+
- For volumes not in an availability zone or volumes in the same availability zone, it must be unique within each subnet in the region.
117+
- For volumes in availability zones, it must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
118118
- It must start with an alphabetical character.
119119
- It can contain only letters, numbers, or dashes (`-`).
120120
- The length must not exceed 80 characters.

articles/azure-netapp-files/create-volumes-dual-protocol.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
153153
* Specify a unique **Volume Path**. This path is used when you create mount targets. The requirements for the path are as follows:
154154
155155
- For volumes not in an availability zone or volumes in the same availability zone, the volume path must be unique within each subnet in the region.
156-
- For volumes in availability zones, the volume path must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information and, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
156+
- For volumes in availability zones, the volume path must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
157157
- It must start with an alphabetical character.
158158
- It can contain only letters, numbers, or dashes (`-`).
159159
- The length must not exceed 80 characters.

articles/azure-netapp-files/includes/file-path-uniqueness.md

Lines changed: 0 additions & 32 deletions
This file was deleted.

articles/azure-netapp-files/manage-availability-zone-volume-placement.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ You can deploy new volumes in the logical availability zone of your choice. You
3434

3535
* VMs and Azure NetApp Files volumes are to be deployed separately, within the same logical availability zone to create zone alignment between VMs and Azure NetApp Files. The availability zone volume placement feature doesn't create zonal VMs upon volume creation, or vice versa.
3636

37-
* <a name="file-path-uniqueness"></a> For volumes in the same availability zone, Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol). This feature is currently in preview.
37+
* <a name="file-path-uniqueness"></a> For volumes in different availability zones, Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol). This feature is currently in preview.
3838

3939
You need to register the feature before using it for the first time. After registration, the feature is enabled and works in the background. No UI control is required.
4040

articles/azure-netapp-files/whats-new.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
2323

2424
* [Volume enhancement: create volumes with the same file path, share name, or volume path in different availability zones](manage-availability-zone-volume-placement.md#file-path-uniqueness) (Preview)
2525

26-
Azure NetApp Files now allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol) as long as they are in different availability zones. For more information, see [Create an NFS volume for Azure NetApp Files](azure-netapp-files-create-volumes.md), [Create an SMB volume for Azure NetApp Files](azure-netapp-files-create-volumes-smb.md), or [Create a dual-protocol volume for Azure NetApp Files](create-volumes-dual-protocol.md). This enhancement is currently in preview.
27-
26+
Azure NetApp Files now allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol) as long as they are in different availability zones. For more information, see [Create an NFS volume for Azure NetApp Files](azure-netapp-files-create-volumes.md), [Create an SMB volume for Azure NetApp Files](azure-netapp-files-create-volumes-smb.md), or [Create a dual-protocol volume for Azure NetApp Files](create-volumes-dual-protocol.md). This enhancement is currently in preview.
27+
2828
## January 2024
2929

3030
* [Customer-managed keys](configure-customer-managed-keys.md) is now generally available (GA).

0 commit comments

Comments
 (0)