Merge pull request #89732 from ekpgh/hpc-cache-updatepreview-2

make non-blocking updates from PR 89614

Author: Jak-MS

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

@@ -34,7 +34,7 @@ From the Azure portal, open your cache instance and click **Storage targets** on
 
 ## Add a new Azure Blob storage target
 
-A new Blob storage target needs an empty Blob container or a container that is populated with data in the Azure HPC Cache cloud filesystem format. Read more about pre-loading a Blob container in [Move data to Azure Blob storage](hpc-cache-ingest.md).
+A new Blob storage target needs an empty Blob container or a container that is populated with data in the Azure HPC Cache cloud file system format. Read more about pre-loading a Blob container in [Move data to Azure Blob storage](hpc-cache-ingest.md).
 
 To define an Azure Blob container, enter this information.
 
@@ -49,7 +49,7 @@ To define an Azure Blob container, enter this information.
   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).
 * **Storage container** - Select the Blob container for this target.
 
-* **Virtual namespace path** - Set the client-facing filepath for this storage target. Read [Configure aggregated namespace](hpc-cache-namespace.md) to learn more about the virtual namespace feature.
+* **Virtual namespace path** - Set the client-facing file path for this storage target. Read [Configure aggregated namespace](hpc-cache-namespace.md) to learn more about the virtual namespace feature.
 
 When finished, click **OK** to add the storage target.
 
@@ -104,7 +104,7 @@ Create all of the paths from one storage target.
 
 Fill in these values for each namespace path: 
 
-* **Virtual namespace path** - Set the client-facing filepath for this storage target. Read [Configure aggregated namespace](hpc-cache-namespace.md) to learn more about the virtual namespace feature.
+* **Virtual namespace path** - Set the client-facing file path for this storage target. Read [Configure aggregated namespace](hpc-cache-namespace.md) to learn more about the virtual namespace feature.
 
 <!--  The virtual path should start with a slash ``/``. -->
 

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

@@ -18,7 +18,7 @@ To learn more about moving data to Blob storage for your Azure HPC Cache, read [
 
 You can manually create a multi-threaded copy on a client by running more than one copy command at once in the background against predefined sets of files or paths.
 
-The Linux/UNIX ``cp`` command includes the argument ``-p`` to preserve ownership and mtime metadata. Adding this argument to the commands below is optional. (Adding the argument increases the number of filesystem calls sent from the client to the destination filesystem for metadata modification.)
+The Linux/UNIX ``cp`` command includes the argument ``-p`` to preserve ownership and mtime metadata. Adding this argument to the commands below is optional. (Adding the argument increases the number of file system calls sent from the client to the destination file system for metadata modification.)
 
 This simple example copies two files in parallel:
 
@@ -76,9 +76,9 @@ cp -R /mnt/source/dir1/dir1d /mnt/destination/dir1/ &
 
 ## When to add mount points
 
-After you have enough parallel threads going against a single destination filesystem mount point, there will be a point where adding more threads does not give more throughput. (Throughput will be measured in files/second or bytes/second, depending on your type of data.) Or worse, over-threading can sometimes cause a throughput degradation.  
+After you have enough parallel threads going against a single destination file system mount point, there will be a point where adding more threads does not give more throughput. (Throughput will be measured in files/second or bytes/second, depending on your type of data.) Or worse, over-threading can sometimes cause a throughput degradation.  
 
-When this happens, you can add client-side mount points to other Azure HPC Cache mount addresses, using the same remote filesystem mount path:
+When this happens, you can add client-side mount points to other Azure HPC Cache mount addresses, using the same remote file system mount path:
 
 ```bash
 10.1.0.100:/nfs on /mnt/sourcetype nfs (rw,vers=3,proto=tcp,addr=10.1.0.100)
@@ -131,7 +131,7 @@ Client4: cp -R /mnt/source/dir3/dir3d /mnt/destination/dir3/ &
 
 ## Create file manifests
 
-After understanding the approaches above (multiple copy-threads per destination, multiple destinations per client, multiple clients per network-accessible source filesystem), consider this recommendation: Build file manifests and then use them with copy commands across multiple clients.
+After understanding the approaches above (multiple copy-threads per destination, multiple destinations per client, multiple clients per network-accessible source file system), consider this recommendation: Build file manifests and then use them with copy commands across multiple clients.
 
 This scenario uses the UNIX ``find`` command to create manifests of files or directories:
 

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

@@ -16,7 +16,7 @@ This article explains the best ways to move data to Blob storage for use with Az
 
 Keep these facts in mind:
 
-* Azure HPC Cache uses a specialized storage format to organize data in Blob storage. This is why a Blob storage target must either be a new, empty container, or a Blob container that was previously used for Azure HPC Cache data. ([Avere vFXT for Azure](https://azure.microsoft.com/services/storage/avere-vfxt/) also uses this cloud filesystem.)
+* Azure HPC Cache uses a specialized storage format to organize data in Blob storage. This is why a Blob storage target must either be a new, empty container, or a Blob container that was previously used for Azure HPC Cache data. ([Avere vFXT for Azure](https://azure.microsoft.com/services/storage/avere-vfxt/) also uses this cloud file system.)
 
 * Copying data through the Azure HPC Cache to a back-end storage target is more efficient when you use multiple clients and parallel operations. A simple copy command from one client will move data slowly.
 

articles/hpc-cache/hpc-cache-namespace.md

@@ -12,9 +12,9 @@ ms.author: v-erkell
 
 Azure HPC Cache (preview) allows clients to access a variety of storage systems through a virtual namespace that hides the details of the back-end storage system.
 
-When you add a storage target, you set the client-facing filepath. Client machines mount this filepath and can make file read requests to the cache instead of mounting the storage system directly.
+When you add a storage target, you set the client-facing file path. Client machines mount this file path and can make file read requests to the cache instead of mounting the storage system directly.
 
-Because Azure HPC Cache manages this virtual filesystem, you can change the storage target without changing the client-facing path. For example, you could replace a hardware storage system with cloud storage without needing to rewrite client-facing procedures.
+Because Azure HPC Cache manages this virtual file system, you can change the storage target without changing the client-facing path. For example, you could replace a hardware storage system with cloud storage without needing to rewrite client-facing procedures.
 
 ## Aggregated namespace example
 
@@ -37,23 +37,23 @@ The data to be analyzed has been copied to an Azure Blob storage container named
 
 To allow easy access through the cache, consider creating storage targets with these virtual namespace paths:
 
-| Back-end storage system <br/> (NFS filepath or Blob container) | Virtual namespace path |
+| Back-end storage system <br/> (NFS file path or Blob container) | Virtual namespace path |
 |-----------------------------------------|------------------------|
 | /goldline/templates/acme2017/sku798     | /templates/sku798      |
 | /goldline/templates/acme2017/sku980     | /templates/sku980      |
 | sourcecollection                        | /source/               |
 
 An NFS storage target can have multiple virtual namespace paths, as long as each one references a unique export path.
 
-Since the NFS source paths are subdirectories of the same export, you will need to define multiple namespace paths from the same storage target.
+Because the NFS source paths are subdirectories of the same export, you will need to define multiple namespace paths from the same storage target.
 
 | Storage target hostname  | NFS export path      | Subdirectory path | Namespace path    |
 |--------------------------|----------------------|-------------------|-------------------|
 | *IP address or hostname* | /goldline/templates  | acme2017/sku798   | /templates/sku798 |
 | *IP address or hostname* | /goldline/templates  | acme2017/sku980   | /templates/sku980 |
 
-A client application can mount the cache and easily access the aggregated namespace filepaths ``/source``, ``/templates/sku798``, and ``/templates/sku980``.
+A client application can mount the cache and easily access the aggregated namespace file paths ``/source``, ``/templates/sku798``, and ``/templates/sku980``.
 
 ## Next steps
 
-After you have decided how to set up your virtual filesystem, [create storage targets](hpc-cache-add-storage.md) to map your back-end storage to your client-facing virtual filepaths.
+After you have decided how to set up your virtual file system, [create storage targets](hpc-cache-add-storage.md) to map your back-end storage to your client-facing virtual file paths.

articles/hpc-cache/index.yml

@@ -5,7 +5,7 @@ summary: Use Azure HPC Cache to expedite file access for read-intensive high-per
 
 metadata:
   title: Microsoft Azure HPC Cache 
-  description: Learn how to create and use Azure HPC Cache to solve the latency problem between your compute resources and storage. Azure HPC Cache is for file-based read-heavy workloads, and can create an aggregated virtual filesystem that incorporates Azure Blob storage and on-premises hardware filers.
+  description: Learn how to create and use Azure HPC Cache to solve the latency problem between your compute resources and storage. Azure HPC Cache is for file-based read-heavy workloads, and can create an aggregated virtual file system that incorporates Azure Blob storage and on-premises hardware filers.
   ms.service: hpc-cache 
   ms.topic: landing-page 
   ms.collection: collection