minor correctionsto new features articles

Author: ekpgh

articles/hpc-cache/access-policies.md

@@ -4,7 +4,7 @@ description: How to create and apply custom access policies to limit client acce
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: how-to
-ms.date: 12/22/2020
+ms.date: 12/28/2020
 ms.author: v-erkel
 ---
 
@@ -86,6 +86,17 @@ If you turn on root squash, you must also set the anonymous ID user value to one
 * **65535** (no access)
 * **0** (unprivileged root)
 
+## Update access policies
+
+You can edit or delete access policies from the table in the **Client access policies** page.
+
+Click the policy name to open it for editing.
+
+To delete a policy, mark the checkbox next to its name in the list, then click the **Delete** button at the top of the list. You can't delete the policy named Default.
+
+> [!NOTE]
+> You can't delete an access policy that is in use. Remove the policy from any namespace paths that include it before trying to delete it.
+
 ## Next steps
 
 * Apply access policies in the namespace paths for your storage targets. Read [Set up the aggregated namespace](add-namespace-paths.md) to learn how.

articles/hpc-cache/directory-services.md

@@ -39,7 +39,7 @@ Under **Active directory details**, supply these values:
 
 * **AD DNS domain name** - Provide the fully qualified domain name of the AD server that the cache will join to get the credentials.
 
-* **Cache server name (computer account)** - Set the name that will be assigned to this HPC cache when it joins the AD domain. Specify a name that is easy to recognize as this cache. The name can be up to 15 characters long and can include capital or lowercase letters, numbers, hyphens (-), and underscores (_).
+* **Cache server name (computer account)** - Set the name that will be assigned to this HPC cache when it joins the AD domain. Specify a name that is easy to recognize as this cache. The name can be up to 15 characters long and can include capital or lowercase letters, numbers, and hyphens (-).
 
 In the **Credentials** section, provide an AD administrator username and password that the Azure HPC Cache can use to access the AD server. This information is encrypted when stored, and can't be queried.