Skip to content

Commit 2f0eaa2

Browse files
committed
reformat
1 parent b0e5f36 commit 2f0eaa2

File tree

2 files changed

+12
-14
lines changed

2 files changed

+12
-14
lines changed

articles/azure-netapp-files/faq-nfs.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -40,15 +40,14 @@ You can specify whether the root account can access the volume or not by using t
4040
## Can I use the same file path for multiple volumes?
4141

4242
The same file path can be used for:
43-
* volumes deployed in different regions.
44-
* volumes deployed to different availability zones within the same region.
43+
* volumes deployed in different regions
44+
* volumes deployed to different availability zones within the same region
4545

46-
Also, the same file path can be used for:
47-
* regional volumes (without availability zones).
48-
* volumes within the same region.
46+
If you are using:
47+
* regional volumes (without availability zones) or
48+
* volumes within the same region,
4949

50-
For these cases (regional volumes and volumes with the same region), the file path must be unique within each delegated subnet or assigned to different delegated subnets.
51-
<!-- confirm part after or -->
50+
the same file path can be used, however the file path must be unique within each delegated subnet or assigned to different delegated subnets.
5251

5352
For more information, see [Create an NFS volume for Azure NetApp Files](azure-netapp-files-create-volumes.md) or [Create a dual-protocol volume for Azure NetApp Files](create-volumes-dual-protocol.md).
5453

articles/azure-netapp-files/faq-smb.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -83,15 +83,14 @@ Azure NetApp Files also supports [access-based enumeration](azure-netapp-files-c
8383
## Can I use the same share name for multiple volumes?
8484

8585
The same share name can be used for:
86-
* volumes deployed in different regions.
87-
* volumes deployed to different availability zones within the same region.
86+
* volumes deployed in different regions
87+
* volumes deployed to different availability zones within the same region
8888

89-
Also, the share name can be used for:
90-
* regional volumes (without availability zones)
91-
* volumes within the same region
89+
If you are using:
90+
* regional volumes (without availability zones) or
91+
* volumes within the same region,
9292

93-
For these cases (regional volumes and volumes with the same region), the share name must be unique within each delegated subnet or assigned to different delegated subnets.
94-
<!-- confirm part after or -->
93+
the same share name can be used, however the share name must be unique within each delegated subnet or assigned to different delegated subnets.
9594

9695
For more information, see For more information, see [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).
9796

0 commit comments

Comments
 (0)