Merge pull request #114132 from ekpgh/hpc-update-squash

Updated root squash discussion

Author: PRMerger17

articles/hpc-cache/configuration.md

@@ -4,7 +4,7 @@ description: Explains how to configure additional settings for the cache like MT
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 04/27/2020
+ms.date: 05/06/2020
 ms.author: v-erkel
 ---
 
@@ -37,13 +37,15 @@ Learn more about MTU settings in Azure virtual networks by reading [TCP/IP perfo
 ## Configure root squash
 <!-- linked from troubleshoot -->
 
-The **Enable root squash** setting controls how the Azure HPC Cache allows root access. Root squash helps to prevent root-level access from unauthorized clients.
+The **Enable root squash** setting controls how Azure HPC Cache treats requests from the root user on client machines.
 
-This setting lets users control root access at the cache level, which can help compensate for the required ``no_root_squash`` setting for NAS systems used as storage targets. (Read more about [NFS storage target prerequisites](hpc-cache-prereqs.md#nfs-storage-requirements).) It also can improve security when used with Azure Blob storage targets.
+When root squash is enabled, root users from a client are automatically mapped to the user "nobody" when they send requests through the Azure HPC Cache. It also prevents client requests from using set-UID permission bits.
 
-The default setting is **Yes**. (Caches created before April 2020 might have the default setting **No**.)
+If root squash is disabled, a request from the client root user (UID 0) is passed through to a back-end NFS storage system as root. This configuration might allow inappropriate file access.
+
+Setting root squash on the cache can help compensate for the required ``no_root_squash`` setting on NAS systems that are used as storage targets. (Read more about [NFS storage target prerequisites](hpc-cache-prereqs.md#nfs-storage-requirements).) It also can improve security when used with Azure Blob storage targets.
 
-When enabled, this feature also prevents use of set-UID permission bits in client requests to the cache.
+The default setting is **Yes**. (Caches created before April 2020 might have the default setting **No**.)
 
 ## View snapshots for blob storage targets