hpc-cache: feedback changes

Author: ekpgh

articles/hpc-cache/hpc-cache-add-storage.md

@@ -4,13 +4,13 @@ description: How to define storage targets so that your Azure HPC Cache can use
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 03/25/2020
+ms.date: 04/03/2020
 ms.author: rohogue
 ---
 
 # Add storage targets
 
-*Storage targets* are back-end storage for files that are accessed through an Azure HPC Cache instance. You can add NFS storage (like an on-premises hardware system), or store data in Azure Blob.
+*Storage targets* are back-end storage for files that are accessed through an Azure HPC Cache. You can add NFS storage (like an on-premises hardware system), or store data in Azure Blob.
 
 You can define up to ten different storage targets for one cache. The cache presents all of the storage targets in one aggregated namespace.
 
@@ -30,10 +30,10 @@ A new Blob storage target needs an empty Blob container or a container that is p
 
 You can create a new container from this page just before adding it.
 
-To define an Azure Blob container, enter this information.
-
 ![screenshot of the add storage target page, populated with information for a new Azure Blob storage target](media/hpc-cache-add-blob.png)
 
+To define an Azure Blob container, enter this information.
+
 * **Storage target name** - Set a name that identifies this storage target in the Azure HPC Cache.
 * **Target type** - Choose **Blob**.
 * **Storage account** - Select the account that you want to use.
@@ -136,7 +136,7 @@ There are three options:
 
 * **Greater than 15% writes** - This option speeds up both read and write performance. When using this option, all clients must access files through the Azure HPC Cache instead of mounting the back-end storage directly. The cached files will have recent changes that are not stored on the back end.
 
-  In this usage model, files in the cache are not checked against the files on back-end storage. The cached version of the file is assumed to be more current. A modified file in the cache is only written to the back-end storage system after it has been in the cache for an hour with no additional changes.
+  In this usage model, files in the cache are not checked against the files on back-end storage. The cached version of the file is assumed to be more current. A modified file in the cache is written to the back-end storage system after it has been in the cache for an hour with no additional changes.
 
 * **Clients write to the NFS target, bypassing the cache** - Choose this option if any clients in your workflow write data directly to the storage system without first writing to the cache. Files that clients request are cached, but any changes to those files from the client are passed back to the back-end storage system immediately.
 

articles/hpc-cache/hpc-cache-mount.md

@@ -4,7 +4,7 @@ description: How to connect clients to an Azure HPC Cache service
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 04/01/2020
+ms.date: 04/03/2020
 ms.author: rohogue
 ---
 
@@ -29,7 +29,7 @@ Make sure your clients are able to mount the Azure HPC Cache by following the gu
 
 The client machines must have network access to the cache's virtual network and private subnet.
 
-For example, create client VMs within the same virtual network, or use an endpoint, gateway, or other solution in the virtual network for access from outside. (Remember that nothing other than the cache itself can be hosted inside the cache's subnet.)
+For example, create client VMs within the same virtual network, or use an endpoint, gateway, or other solution in the virtual network for access from outside. (Remember that nothing other than the cache itself should be hosted inside the cache's subnet.)
 
 ### Install utilities
 
@@ -42,7 +42,7 @@ Install the appropriate Linux utility software to support the NFS mount command:
 
 Create a local directory path on each client to connect to the cache. Create a path for each storage target that you want to mount.
 
-Example: `sudo mkdir /mnt/hpc-cache-1/target3`
+Example: `sudo mkdir -p /mnt/hpc-cache-1/target3`
 
 ## Use the mount instructions utility
 
@@ -65,7 +65,7 @@ To use this page, follow this procedure:
 
    Note the path name so that you can modify it in the command if needed.
 
-1. In step two, select one of the available IP addresses. All of the cache's [client mount points](#find-mount-command-components) are listed here.
+1. In step two, select one of the available IP addresses. All of the cache's [client mount points](#find-mount-command-components) are listed here. Make sure that you have a system to balance load among all IP addresses.
 
 1. The field in step three automatically populates with a prototype mount command. Click the copy symbol at the right side of the field to automatically copy it to your clipboard.
 

articles/hpc-cache/hpc-cache-prereqs.md

@@ -4,7 +4,7 @@ description: Prerequisites for using Azure HPC Cache
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 03/25/2020
+ms.date: 04/03/2020
 ms.author: rohogue
 ---
 
@@ -118,6 +118,8 @@ More information is included in [Troubleshoot NAS configuration and NFS storage
     | TCP/UDP  | 4046  | mountd   |
     | TCP/UDP  | 4047  | status   |
 
+    Some systems use different port numbers for these services - consult your storage system's documentation to be sure.
+
   * Check firewall settings to be sure that they allow traffic on all of these required ports. Be sure to check firewalls used in Azure as well as on-premises firewalls in your data center.
 
 * **Directory access:** Enable the `showmount` command on the storage system. Azure HPC Cache uses this command to check that your storage target configuration points to a valid export, and also to make sure that multiple mounts don't access the same subdirectories (a risk for file collision).
@@ -127,7 +129,7 @@ More information is included in [Troubleshoot NAS configuration and NFS storage
 
   Learn more about directory listing access in the NFS storage target [troubleshooting article](troubleshoot-nas.md#enable-export-listing).
 
-* **Root access:** The cache connects to the back-end system as user ID 0. Check these settings on your storage system:
+* **Root access** (read/write): The cache connects to the back-end system as user ID 0. Check these settings on your storage system:
   
   * Enable `no_root_squash`. This option ensures that the remote root user can access files owned by root.