nfsv41 update and screenshots

Author: julie.chen

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

@@ -108,7 +108,7 @@ A subnet must be delegated to Azure NetApp Files.
     ![Active Directory Connections](../media/azure-netapp-files/azure-netapp-files-active-directory-connections-created.png)
 
 > [!NOTE] 
-> You can edit the username and password fields after saving the Active Directory connection. No other values can be edited after saving the connection. If you need to change any other values, you must first delete any deployed SMB volumes, then delete and re-create the AD connection.
+> You can edit the username and password fields after saving the Active Directory connection. No other values can be edited after saving the connection. If you need to change any other values, you must first delete any deployed SMB volumes, then delete and re-create the Active Directory connection.
 
 ## Add an SMB volume
 

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

@@ -31,18 +31,18 @@ A subnet must be delegated to Azure NetApp Files.
 * Deciding which NFS version to use  
   NFSv3 can handle a wide variety of use cases and is commonly deployed in most enterprise applications. You should validate what version (NFSv3 or NFSv4.1) your application requires and create your volume using the appropriate version. For example, if you use [Apache ActiveMQ](https://activemq.apache.org/shared-file-system-master-slave), file locking with NFSv4.1 is recommended over NFSv3. 
 
-  > [!IMPORTANT] 
-> Access to the NFSv4.1 feature requires whitelisting.  To request whitelisting, please submit a request to <[email protected]>. 
+> [!IMPORTANT] 
+> Access to the NFSv4.1 feature requires whitelisting.  To request whitelisting, submit a request to <[email protected]>. 
 
 * Security  
   Support for UNIX mode bits (read, write, and execute) is available for NFSv3 and NFSv4.1. Root-level access is required on the NFS client to mount NFS volumes.
 
-* Local user/group & LDAP support for NFSv4.1  
-  Currently NFSv4.1 supports root access to volumes only. 
+* Local user/group and LDAP support for NFSv4.1  
+  Currently, NFSv4.1 supports root access to volumes only. 
 
 ## Best practice
 
-* Ensure you’re using the mount instructions for the volume.  See [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md).
+* You should ensure that you’re using the proper mount instructions for the volume.  See [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md).
 
 * The NFS client should be in the same VNet or peered VNet as the Azure NetApp Files volume. Connecting from outside the VNet is supported; however, it will introduce additional latency and decrease overall performance.
 

articles/azure-netapp-files/azure-netapp-files-faqs.md

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 09/25/2019
+ms.date: 10/12/2019
 ms.author: b-juche
 ---
 # FAQs About Azure NetApp Files
@@ -45,7 +45,7 @@ Yes, you can, if you create the required DNS entries. Azure NetApp Files supplie
 
 ### Can the network traffic between the Azure VM and the storage be encrypted?
 
-Data traffic (traffic from the NFSv3 or SMBv3 client to Azure NetApp Files volumes) is not encrypted. However, the traffic from an Azure VM (running an NFS or SMB client) to Azure NetApp Files is as secure as any other Azure-VM-to-VM traffic. This traffic is local to the Azure data-center network. 
+Data traffic (traffic from the NFSv3, NFSv4.1, or SMBv3 client to Azure NetApp Files volumes) is not encrypted. However, the traffic from an Azure VM (running an NFS or SMB client) to Azure NetApp Files is as secure as any other Azure-VM-to-VM traffic. This traffic is local to the Azure data-center network. 
 
 ### Can the storage be encrypted at rest?
 
@@ -119,7 +119,7 @@ The volume size reported in DF is the maximum size the Azure NetApp Files volume
 Azure NetApp Files supports NFSv3 and NFSv4.1. You can create a volume using either NFS version. 
 
 > [!IMPORTANT] 
-> Access to the NFSv4.1 feature requires whitelisting.  To request whitelisting, please submit a request to <[email protected]>. 
+> Access to the NFSv4.1 feature requires whitelisting.  To request whitelisting, submit a request to <[email protected]>. 
 
 
 ### How do I enable root squashing?

articles/azure-netapp-files/azure-netapp-files-quickstart-set-up-account-create-volumes.md

@@ -251,6 +251,8 @@ This how-to article requires the Azure PowerShell module Az version 2.6.0 or lat
     * Select **NFS** as the protocol type for the volume.  
     * Enter **myfilepath1** as the file path that will be used to create the export path for the volume.  
     * Select the NFS version (**NFSv3** or **NFSv4.1**) for the volume.  
+> [!IMPORTANT] 
+> Access to the NFSv4.1 feature requires whitelisting.  To request whitelisting, submit a request to <[email protected]>. 
 
     ![Specify NFS protocol for quickstart](../media/azure-netapp-files/azure-netapp-files-quickstart-protocol-nfs.png)