hpc-cache: more edits and new screenshots

Author: ekpgh

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

@@ -4,7 +4,7 @@ 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: 10/30/2019
+ms.date: 11/11/2019
 ms.author: rohogue
 ---
 
@@ -36,7 +36,7 @@ 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 with the container to reference.
+* **Storage account** - Select the account with the container that you want to use.
 
   You will need to authorize the cache instance to access the storage account as described in [Add the access roles](#add-the-access-control-roles-to-your-account).
 
@@ -49,7 +49,7 @@ To define an Azure Blob container, enter this information.
 When finished, click **OK** to add the storage target.
 
 > [!NOTE]
-> If your storage account firewall is set to restrict access to selected networks only, use the temporary workaround documented in [Work around Blob storage account firewall settings](hpc-cache-blob-firewall-fix.md) to create Blob storage targets.
+> If your storage account firewall is set to restrict access to only "selected networks," use the temporary workaround documented in [Work around Blob storage account firewall settings](hpc-cache-blob-firewall-fix.md).
 
 ### Add the access control roles to your account
 
@@ -82,7 +82,7 @@ Steps to add the RBAC roles:
 
 ## Add a new NFS storage target
 
-An NFS storage target has some extra fields to specify how to reach the storage export and how to efficiently cache its data. Also, you can create multiple namespace paths from one NFS host if it has more than one export available.
+An NFS storage target has more fields than the Blob storage target. These fields specify how to reach the storage export and how to efficiently cache its data. Also, an NFS storage target lets you create multiple namespace paths if the NFS host has more than one export available.
 
 ![Screenshot of add storage target page with NFS target defined](media/hpc-cache-add-nfs-target.png)
 
@@ -127,17 +127,17 @@ There are three options:
 
   This option caches files that clients read, but passes writes through to the back-end storage immediately. Files stored in the cache are never compared to the files on the NFS storage volume.
 
-  Do not use this option if there is a risk that a file might be modified directly on the storage system without first writing it to the cache. If that happens, the cached version of the file will never be updated with changes from the back end, and the data set will become inconsistent.
+  Do not use this option if there is a risk that a file might be modified directly on the storage system without first writing it to the cache. If that happens, the cached version of the file will never be updated with changes from the back end, and the data set can become inconsistent.
 
-* **Greater than 15% writes** - This option balances read and write performance. With this option, all clients must access files through the Azure HPC Cache instead of mounting the back-end storage directly, because the cached files will have recent changes not stored on the back end.
+* **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.
 
-  Files in the cache are not checked against the files on back-end storage. Also, a file that a client has changed is stored in the cache only for up to an hour before it is written to the long-term storage system.
+  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.
 
 * **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.
 
   With this usage model, the files in the cache are frequently checked against the back-end versions for updates. This verification allows files to be changed outside of the cache while maintaining data consistency.
 
-This table summarizes the differences between the usage models.
+This table summarizes the usage model differences:
 
 | Usage model | Caching mode | Back-end verification | Maximum write-back delay |
 | ---- | ---- | ---- | ---- |
@@ -152,4 +152,4 @@ After creating storage targets, consider one of these tasks:
 * [Mount the Azure HPC Cache](hpc-cache-mount.md)
 * [Move data to Azure Blob storage](hpc-cache-ingest.md)
 
-If you need to change a storage target, read [Edit storage targets](hpc-cache-edit-storage.md) to learn how.
+You also can [edit a storage target](hpc-cache-edit-storage.md).

articles/hpc-cache/hpc-cache-blob-firewall-fix.md

@@ -16,9 +16,9 @@ The firewall setting that allows access only from "selected networks" can preven
 
 The issue is that the cache service uses a hidden service virtual network that is separate from customer environments. It isn't possible to explicitly authorize this network to access your storage account.
 
-When you create a Blob storage target, the cache service uses the service network to check whether or not the container is empty. If the firewall does not allow access from the hidden network, the check fails, and the storage target creation fails.
+When you create a Blob storage target, the cache service uses this network to check whether or not the container is empty. If the firewall does not allow access from the hidden network, the check fails, and the storage target creation fails.
 
-To work around the problem, temporarily change your firewall settings to create the storage target:
+To work around the problem, temporarily change your firewall settings while creating the storage target:
 
 1. Go to the storage account **Firewalls and virtual networks** page and change the setting "Allow access from" to **All networks**.
 1. Create the Blob storage target in your Azure HPC Cache.

articles/hpc-cache/hpc-cache-create.md

@@ -4,7 +4,7 @@ description: How to create an Azure HPC Cache instance
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: tutorial
-ms.date: 10/30/2019
+ms.date: 11/11/2019
 ms.author: rohogue
 ---
 
@@ -59,6 +59,7 @@ Cache creation takes about 10 minutes. You can track the progress in the Azure p
 ![screenshot of cache creation "deployment underway" and "notifications" pages in portal](media/hpc-cache-deploy-status.png)
 
 When creation finishes, a notification appears with a link to the new Azure HPC Cache instance, and the cache appears in your subscription's **Resources** list.
+<!-- double check on notification -->
 
 ![screenshot of Azure HPC Cache instance in Azure portal](media/hpc-cache-new-overview.png)
 

articles/hpc-cache/hpc-cache-ingest-manual.md

@@ -12,7 +12,7 @@ ms.author: rohogue
 
 This article gives detailed instructions for manually copying data to a Blob storage container for use with Azure HPC Cache. It uses multi-threaded parallel operations to optimize the copy speed.
 
-To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage for Azure HPC Cache](hpc-cache-ingest.md).
+To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage](hpc-cache-ingest.md).
 
 ## Simple copy example
 

articles/hpc-cache/hpc-cache-ingest-msrsync.md

@@ -12,7 +12,7 @@ ms.author: rohogue
 
 This article gives detailed instructions for using the ``msrsync`` utility to copy data to an Azure Blob storage container for use with Azure HPC Cache.
 
-To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage for Azure HPC Cache](hpc-cache-ingest.md).
+To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage](hpc-cache-ingest.md).
 
 The ``msrsync`` tool can be used to move data to a backend storage target for the Azure HPC Cache. This tool is designed to optimize bandwidth usage by running multiple parallel ``rsync`` processes. It is available from GitHub at https://github.com/jbd/msrsync.
 

articles/hpc-cache/hpc-cache-ingest-parallelcp.md

@@ -12,7 +12,7 @@ ms.author: rohogue
 
 This article gives instructions for creating the ``parallelcp`` script and using it to move data to a Blob storage container for use with Azure HPC Cache.
 
-To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage for Azure HPC Cache](hpc-cache-ingest.md).
+To learn more about moving data to Blob storage for your Azure HPC Cache, read [Move data to Azure Blob storage](hpc-cache-ingest.md).
 
 ## Create the parallelcp script
 

articles/hpc-cache/hpc-cache-manage.md

@@ -40,7 +40,7 @@ After all the data is saved to storage targets, the cache automatically starts t
 
 ## Upgrade cache software
 
-If a new software version is available, the **Upgrade** button becomes active. You also might see a message at the top of the page about updating software.
+If a new software version is available, the **Upgrade** button becomes active. You also should see a message at the top of the page about updating software.
 
 ![screenshot of the top row of buttons with the Upgrade button enabled](media/hpc-cache-upgrade-button.png)
 

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

@@ -43,7 +43,9 @@ The cache needs DNS to access resources outside of its virtual network. Dependin
 * To access Azure Blob storage endpoints and other internal resources, you need the Azure-based DNS server.
 * To access on-premises storage, you need to configure a custom DNS server that can resolve your storage hostnames.
 
-If you only need access to Blob storage, you can use the default Azure-provided DNS server for your cache. However, if you need access to other resources, you should create a custom DNS server and configure it to forward any Azure-specific resolution requests to the Azure DNS server. (A simple DNS server also can be used to load balance client connections among all the available cache mount points.)
+If you only need access to Blob storage, you can use the default Azure-provided DNS server for your cache. However, if you need access to other resources, you should create a custom DNS server and configure it to forward any Azure-specific resolution requests to the Azure DNS server.
+
+A simple DNS server also can be used to load balance client connections among all the available cache mount points.
 
 Learn more about Azure virtual networks and DNS server configurations in [Name resolution for resources in Azure virtual networks](https://docs.microsoft.com/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances).
 
@@ -53,7 +55,9 @@ Check these permission-related prerequisites before starting to create your cach
 
 * The cache instance needs to be able to create virtual network interfaces (NICs). The user who creates the cache must have sufficient privileges in the subscription to create NICs.
 
-* If using Blob storage, Azure HPC Cache needs authorization to access your storage account. You can use role-based access control (RBAC) to give the cache access to your Blob storage. Two roles are required: Storage Account Contributor and Storage Blob Data Contributor. Follow the instructions in [Add storage targets](hpc-cache-add-storage.md#add-the-access-control-roles-to-your-account) to add the roles.
+* If using Blob storage, Azure HPC Cache needs authorization to access your storage account. Use role-based access control (RBAC) to give the cache access to your Blob storage. Two roles are required: Storage Account Contributor and Storage Blob Data Contributor.
+
+  Follow the instructions in [Add storage targets](hpc-cache-add-storage.md#add-the-access-control-roles-to-your-account) to add the roles.
 
 ## Storage infrastructure
 
@@ -83,7 +87,7 @@ To create a compatible storage account, use these settings:
 It's a good practice to use a storage account in the same location as your cache.
 <!-- clarify location - same region or same resource group or same virtual network? -->
 
-You also must give the cache application access to your Azure storage account. Follow the description in [Add storage targets](hpc-cache-add-storage.md#add-the-access-control-roles-to-your-account) to give the cache the access roles Storage Account Contributor and Storage Blob Data Contributor. If you are not the storage account owner, have the owner do this step.
+You also must give the cache application access to your Azure storage account as mentioned in [Permissions](#permissions), above. Follow the procedure in [Add storage targets](hpc-cache-add-storage.md#add-the-access-control-roles-to-your-account) to give the cache the required access roles. If you are not the storage account owner, have the owner do this step.
 
 ## Next steps