acrolinx

Author: b-ahibbard

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

@@ -99,7 +99,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
         ![Show advanced selection](../media/azure-netapp-files/volume-create-advanced-selection.png)
 
         >[!NOTE]
-        >By default, the .snapshot directory path is hidden from NFSv4.1 clients. Enabling the **Hide snapshot path** option will hide the .snapshot directory from NFSv3 clients; the directory will still be accessible.
+        >By default, the `.snapshot` directory path is hidden from NFSv4.1 clients. Enabling the **Hide snapshot path** option will hide the .snapshot directory from NFSv3 clients; the directory will still be accessible.
 
 3. Click **Protocol**, and then complete the following actions:  
     * Select **NFS** as the protocol type for the volume.   

articles/azure-netapp-files/convert-nfsv3-nfsv41.md

@@ -39,8 +39,8 @@ Converting a volume between NFSv3 and NFSv4.1 does not require that you create a
 * You cannot convert a single-protocol NFS volume to a dual-protocol volume, or the other way around. 
 * You cannot convert a destination volume in a cross-region replication relationship. 
 * Converting an NFSv4.1 volume to NFSv3 will cause all advanced NFSv4.1 features such as ACLs and file locking to become unavailable. 
-* Converting a volume from NFSv3 to NFSv4.1 will cause the .snapshot directory to be hidden from NFSv4.1 clients. The directory will still be accessible.
-* Converting a volume from NFSv4.1 to NFSv3 will cause the .snapshot directory to be visible. You can modify the properties of the volume to [hide the snapshot path](snapshots-edit-hide-path.md).
+* Converting a volume from NFSv3 to NFSv4.1 will cause the `.snapshot` directory to be hidden from NFSv4.1 clients. The directory will still be accessible.
+* Converting a volume from NFSv4.1 to NFSv3 will cause the `.snapshot` directory to be visible. You can modify the properties of the volume to [hide the snapshot path](snapshots-edit-hide-path.md).
 
 ## Register the option 
 

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

@@ -50,9 +50,9 @@ For example, if a client mounting a volume becomes unresponsive or crashes beyon
 
 A grace period defines a period of special processing in which clients can try to reclaim their locking state during a server recovery. The default timeout for the leases is 30 seconds with a grace period of 45 seconds. After that time, the client's lease will be released. 
 
-## Why is the .snapshot directory not visible in an NFSv4.1 volume, but it is visible in an NFSv3 volume?
+## Why is the `.snapshot` directory not visible in an NFSv4.1 volume, but it is visible in an NFSv3 volume?
 
-By design, the .snapshot directory is never visible to NFSv4.1 clients. By default, the .snapshot directory will be visible to NFSv3 clients. To hide the .snapshot directory from NFSv3 clients, edit the properties of the volume to [hide the snapshot path](snapshots-edit-hide-path.md).
+By design, the .snapshot directory is never visible to NFSv4.1 clients. By default, the `.snapshot `directory will be visible to NFSv3 clients. To hide the `.snapshot` directory from NFSv3 clients, edit the properties of the volume to [hide the snapshot path](snapshots-edit-hide-path.md).
 
 ## Oracle dNFS