adding NFSv4.1 default domain config instructions

Author: julie.chen

articles/azure-netapp-files/TOC.yml

@@ -47,12 +47,12 @@
     href: azure-netapp-files-set-up-capacity-pool.md
   - name: Delegate a subnet to Azure NetApp Files
     href: azure-netapp-files-delegate-subnet.md
+  - name: Create an SMB volume for Azure NetApp Files
+    href: azure-netapp-files-create-volumes-smb.md
   - name: Create an NFS volume for Azure NetApp Files
     href: azure-netapp-files-create-volumes.md
   - name: Configure NFSv4.1 default domain for Azure NetApp Files
     href: azure-netapp-files-configure-nfsv41-domain.md
-  - name: Create an SMB volume for Azure NetApp Files
-    href: azure-netapp-files-create-volumes-smb.md
   - name: Configure export policy for an NFS volume
     href: azure-netapp-files-configure-export-policy.md
   - name: Manage volumes

articles/azure-netapp-files/azure-netapp-files-configure-nfsv41-domain.md

@@ -40,20 +40,20 @@ As the above example shows, the user for `file1` should be `root`, but it maps t
 
     ![Updated configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-updated-config.png)
 
-2. Umount any currently mounted NFS volumes.
+2. Unmount any currently mounted NFS volumes.
 3. Update the `/etc/idmapd.conf` file.
 4. Restart the `rpcbind` service on your host (`service rpcbind restart`), or simply reboot the host.
 5. Mount the NFS volumes as required.   
 
     See [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md). 
 
-    The following example shows the resulting user/group change: 
+The following example shows the resulting user/group change: 
 
-    ![Resulting configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-resulting-config.png)
+![Resulting configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-resulting-config.png)
 
-    As the example shows, the user/group has now changed from `nobody` to `root`.
+As the example shows, the user/group has now changed from `nobody` to `root`.
 
-## Behavior about other (non-root) users and groups
+## Behavior of other (non-root) users and groups
 
 Azure NetApp Files supports local users (users created locally on a host) who have permissions associated with files or folders in NFSv4.1 volumes. However, the service does not currently support mapping the users/groups across multiple nodes. Therefore, users created on one host do not map by default to users created on another host. 
 

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

@@ -110,7 +110,7 @@ A subnet must be delegated to Azure NetApp Files.
 
 ## Next steps  
 
-* [Configure NFSv4.1 default domain for Azure NetApp File(azure-netapp-files-configure-nfsv41-domain.md)
+* [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md)
 * [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md)
 * [Configure export policy for an NFS volume](azure-netapp-files-configure-export-policy.md)
 * [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)

articles/azure-netapp-files/azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md

@@ -27,9 +27,8 @@ You can mount or unmount a volume for Windows or Linux virtual machines as neces
 
     ![Mount instructions SMB](../media/azure-netapp-files/azure-netapp-files-mount-instructions-smb.png)
 
-If you are using NFSv4.1:   
+    If you are using NFSv4.1, use the following command to mount your file system:  
 
-* Use the following command to mount your file system:  
 `sudo mount -t nfs -o rw,hard,rsize=65536,wsize=65536,vers=4.1,tcp,sec=sys $MOUNTTARGETIPADDRESS:/$VOLUMENAME $MOUNTPOINT`  
 
-* See [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md). 
+    Also, see [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md).