create done, edit and add in progress

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: how-to
-ms.date: 05/05/2021
+ms.date: 06/23/2021
 ms.custom: subject-rbac-steps
 ms.author: v-erkel
 ---
@@ -33,11 +33,13 @@ Click the image below to watch a [video demonstration](https://azure.microsoft.c
 
 ## Size your cache correctly to support your storage targets
 
-<!-- asc12 to do: add L series standard (they all get 20 even though you can't change the size) -->
-The number of supported storage targets depends on the cache size, which is set when you create the cache. The size is a combination of throughput capacity (in GB/s) and storage capacity (in TB).
+The number of supported storage targets depends on the cache size, which is set when you create the cache. The cache capacity is a combination of throughput capacity (in GB/s) and storage capacity (in TB).
 
-* Up to 10 storage targets - If you choose the smallest or medium cache storage size for your selected throughput value, your cache can have up to 10 storage targets.
-* Up to 20 storage targets - Choose the highest available cache size for your selected throughput value if you want to use more than 10 storage targets. (If using Azure CLI, choose the highest valid cache size for your cache SKU.)
+* Up to 10 storage targets - If you choose a standard cache, and select the smallest or medium cache storage value for your selected throughput, your cache can have a maximum of 10 storage targets.
+* Up to 20 storage targets -
+
+  * All high-throughput caches (which have preconfigured cache storage sizes) can support up to 20 storage targets.
+  * Standard caches can support up to 20 storage targets if you choose the highest available cache size for your selected throughput value. (If using Azure CLI, choose the highest valid cache size for your cache SKU.)
 
 Read [Set cache capacity](hpc-cache-create.md#set-cache-capacity) to learn more about throughput and cache size settings.
 
@@ -48,7 +50,9 @@ A new Blob storage target needs an empty Blob container or a container that is p
 The Azure portal **Add storage target** page includes the option to create a new Blob container just before you add it.
 
 > [!NOTE]
-> For NFS-mounted blob storage, use the [ADLS-NFS storage target](#) type.
+>
+> * For NFS-mounted blob storage, use the [ADLS-NFS storage target](#add-a-new-adls-nfs-storage-target-preview) type.
+> * [High-throughput cache configurations](hpc-cache-create.md#choose-the-cache-type-for-your-needs) do not support standard Azure Blob storage targets. Use NFS-enabled blob storage (ADLS-NFS) instead.
 
 ### [Portal](#tab/azure-portal)
 

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: how-to
-ms.date: 06/21/2021
+ms.date: 06/23/2021
 ms.author: v-erkel 
 ms.custom: devx-track-azurepowershell
 ---
@@ -65,7 +65,7 @@ If you need help sizing your cache correctly, contact Microsoft Service and Supp
 
 ### Choose the cache type for your needs
 
-When you choose your cache capacity, you might notice that some throughput values have fixed cache size values, and others let you select from multiple cache size options. This is because there are two different styles of cache infrastructure:
+When you choose your cache capacity, you might notice that some throughput values have fixed cache sizes, and others let you select from multiple cache size options. This is because there are two different styles of cache infrastructure:
 
 * Standard caches - listed under **Read-write caching** in the throughput menu
 
@@ -94,13 +94,8 @@ Learn more about these options:
 * [Maximum number of storage targets](hpc-cache-add-storage.md#size-your-cache-correctly-to-support-your-storage-targets)
 * [Read and write caching modes](cache-usage-models.md#basic-file-caching-concepts)
 
-
-Choose one of the available throughput values. Also choose the cache storage size if your throughput size allows that option.
-
 ## Enable Azure Key Vault encryption (optional)
 
-The **Disk encryption keys** page appears between the **Cache** and **Tags** tabs.<!-- Read [Regional availability](hpc-cache-overview.md#region-availability) to learn more about region support. -->
-
 If you want to manage the encryption keys used for your cache storage, supply your Azure Key Vault information on the **Disk encryption keys** page. The key vault must be in the same region and in the same subscription as the cache.
 
 You can skip this section if you do not need customer-managed keys. Azure encrypts data with Microsoft-managed keys by default. Read [Azure storage encryption](../storage/common/storage-service-encryption.md) to learn more.
@@ -113,13 +108,16 @@ You can skip this section if you do not need customer-managed keys. Azure encryp
 
 For a complete explanation of the customer-managed key encryption process, read [Use customer-managed encryption keys for Azure HPC Cache](customer-keys.md).
 
-![screenshot of encryption keys page with "customer managed" selected and key vault fields showing](media/create-encryption.png)
+![Screenshot of encryption keys page with "Customer managed" selected and the "Customer key settings" and "Managed identities" configuration forms showing.](media/create-encryption.png)
 
 Select **Customer managed** to choose customer-managed key encryption. The key vault specification fields appear. Select the Azure Key Vault to use, then select the key and version to use for this cache. The key must be a 2048-bit RSA key. You can create a new key vault, key, or key version from this page.
 
-Select xxx 
+Check the **Always use current key version** box if you want to use [automatic key rotation](../virtual-machines/disk-encryption.md#automatic-key-rotation-of-customer-managed-keys-preview).
 
-[ xxx just explain this image: media/cmk-identities-asc12.png xxx ]
+If you need to use a specific managed identity for this cache, configure it in the **Managed identities** section. Read the [managed identities documentation](../active-directory/managed-identities-azure-resources/overview.md#managed-identity-types) for help.
+
+> [!NOTE]
+> You cannot change the assigned identity after you create the cache.
 
 After you create the cache, you must authorize it to use the key vault service. Read [Authorize Azure Key Vault encryption from the cache](customer-keys.md#3-authorize-azure-key-vault-encryption-from-the-cache) for details.
 

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

@@ -10,7 +10,9 @@ ms.author: v-erkel
 
 # Edit storage targets
 
-You can remove or modify storage targets with the Azure portal or by using the Azure CLI. You also can trigger actions on individual storage targets - like suspending service or writing cached data back to long-term storage - as described in Manage storage targets().
+You can modify, manage, or remove storage targets with the Azure portal or by using the Azure CLI.
+
+The xxx 
 
 Depending on the type of storage, you can modify these storage target values:
 
@@ -212,9 +214,9 @@ The configuration for ADLS-NFS usage models is identical to the NFS usage model
 
 ## Manage storage targets
 
-You can xxx
+You can also perform management actions on individual storage targets. These actions supplement the cache-level management options discussed in [Manage your cache](hpc-cache-manage.md).
 
-To learn more about cache-level management actions, read [Manage your cache](hpc-cache-manage.md).
+Sometimes an individual storage target can get into a bad state and need to be temporarily removed, or permanently deleted. You also can flush cached data for a specific target.
 
 ![Screenshot of the storage targets page in the Azure portal, with the cursor over the menu exposed by clicking on the three dots (...) symbol to the far right of the storage target's row in the list.](media/storage-target-manage-options.png)
 
@@ -224,7 +226,7 @@ To learn more about cache-level management actions, read [Manage your cache](hpc
 * Resume
 * Delete
 
-### Flush cached files to the storage target 
+### Flush cached files to the storage target
 
 ### Suspend a storage target
 
@@ -233,7 +235,7 @@ The suspend feature disables client access to a storage target, but doesn't perm
 ### Force remove a storage target
 <!-- https://msazure.visualstudio.com/One/_workitems/edit/8267141 -->
 
-
+Delete 
 
 
 ## Next steps