Required fixes for publish

Author: flang-msft

articles/azure-cache-for-redis/cache-how-to-encryption.md

@@ -59,7 +59,7 @@ In the **Enterprise Flash** tier, keys and values are also partially stored on-d
 
 In the **Basic, Standard, and Premium** tiers, the OS disk is encrypted using MMK. There's no persistence disk mounted and Azure Storage is used instead. 
 
-## Prerequisites and Limitations
+## Prerequisites and limitations
 
 ### General prerequisites and limitations
 
@@ -73,7 +73,7 @@ In the **Basic, Standard, and Premium** tiers, the OS disk is encrypted using MM
 - [Purge protection and soft-delete](../key-vault/general/soft-delete-overview.md) must be enabled in the Azure Key Vault instance. Purge protection isn't enabled by default.
 - When you use firewall rules in the Azure Key Vault, the Key Vault instance must be configured to [allow trusted services](/azure/key-vault/general/network-security).
 - Only RSA keys are supported
-- The user assigned managed identity must be given the permissions _Get_, _Unwrap Key_, and _Wrap Key_ in the Key Vault access policies, or the equivalent permissions within Azure Role Based Access Control. A recommended built-in role definition with the least priveleges needed for this scenario is called [KeyVault Crypto Service Encryption User](../role-based-access-control/built-in-roles.md#key-vault-crypto-service-encryption-user).
+- The user assigned managed identity must be given the permissions _Get_, _Unwrap Key_, and _Wrap Key_ in the Key Vault access policies, or the equivalent permissions within Azure Role Based Access Control. A recommended built-in role definition with the least privileges needed for this scenario is called [KeyVault Crypto Service Encryption User](../role-based-access-control/built-in-roles.md#key-vault-crypto-service-encryption-user).
 
 ## How to configure CMK encryption on Enterprise caches
 
@@ -100,7 +100,7 @@ In the **Basic, Standard, and Premium** tiers, the OS disk is encrypted using MM
 
    :::image type="content" source="media/cache-how-to-encryption/cache-managed-identity-version.png" alt-text="Screenshot showing the select identity and key fields completed.":::
 
-1. If using the **URI** input method, enter the Key Indentifier URI for your chosen key from Azure Key Vault.  
+1. If using the **URI** input method, enter the Key Identifier URI for your chosen key from Azure Key Vault.  
 
 1. When you've entered all the information for your cache, select **Review + create**.
 
@@ -125,11 +125,11 @@ In the **Basic, Standard, and Premium** tiers, the OS disk is encrypted using MM
 1. Choose the specific key using the **Customer-managed key (RSA)** drop-down. If there are multiple versions of the key to choose from, use the **Version** drop-down.
    :::image type="content" source="media/cache-how-to-encryption/cache-encryption-existing-key.png" alt-text="Screenshot showing the select identity and key fields completed for Encryption.":::
 
-1. If using the **URI** input method, enter the Key Indentifier URI for your chosen key from Azure Key Vault.  
+1. If using the **URI** input method, enter the Key Identifier URI for your chosen key from Azure Key Vault.  
 
 1. Select **Save**
 
-## Next Steps
+## Next steps
 
 Learn more about Azure Cache for Redis features:
 

articles/azure-cache-for-redis/cache-how-to-premium-persistence.md

@@ -130,13 +130,13 @@ It takes a while for the cache to create. You can monitor progress on the Azure
 
 1. To enable RDB persistence, select **RDB** and configure the settings.
 
- | Setting      | Suggested value  | Description |
+   | Setting      | Suggested value  | Description |
    | ------------ |  ------- | -------------------------------------------------- |
    | **Backup Frequency** | Use the drop-down and select a backup interval. Choices include **60 Minutes**, **6 hours**, and **12 hours**. | This interval starts counting down after the previous backup operation successfully completes. When it elapses, a new backup starts. |
 
 1. To enable AOF persistence, select **AOF** and configure the settings.
 
- | Setting      | Suggested value  | Description |
+   | Setting      | Suggested value  | Description |
    | ------------ |  ------- | -------------------------------------------------- |
    | **Backup Frequency** | Drop down and select a backup interval. Choices include **Write every second** and **Always write**. | The _Always write_ option will append new entries to the AOF file after every write to the cache. This choice offers the best durability but does lower cache performance. |
 
@@ -203,7 +203,7 @@ az redisenterprise database update --cluster-name "cache1" --resource-group "rg1
 
 ---
 
-## Managing Data Encryption
+## Managing data encryption
 Because Redis persistence creates data at rest, encrypting this data is an important concern for many users. Encryption options vary based on the tier of Azure Cache for Redis being used. 
 
 With the **Premium** tier, data is streamed directly from the cache instance to Azure Storage when persistence is initiated. Various encryption methods can be used with Azure Storage, including Microsoft-managed keys, customer-managed keys, and customer-provided keys. For information on encryption methods, see [Azure Storage encryption for data at rest](../storage/common/storage-service-encryption.md). 
@@ -262,6 +262,12 @@ AOF persistence saves every write to a log, which has a significant effect on th
 
 For more information on performance when using AOF persistence, see [Does AOF persistence affect throughput, latency, or performance of my cache?](#does-aof-persistence-affect-throughput-latency-or-performance-of-my-cache)
 
+### Does AOF persistence affect throughput, latency, or performance of my cache?
+
+AOF persistence does affect throughput. AOF runs on both the primary and replica process, therefore you see higher CPU and Server Load for a cache with AOF persistence than an identical cache without AOF persistence. AOF offers the best consistency with the data in memory because each write and delete is persisted with only a few seconds of delay. The trade-off is that AOF is more compute intensive.
+
+As long as CPU and Server Load are both less than 90%, there is a penalty on throughput, but the cache operates normally, otherwise. Above 90% CPU and Server Load, the throughput penalty can get much higher, and the latency of all commands processed by the cache increases. This is because AOF persistence runs on both the primary and replica process, increasing the load on the node in use, and putting persistence on the critical path of data. 
+
 ### What happens if I've scaled to a different size and a backup is restored that was made before the scaling operation?
 
 For both RDB and AOF persistence:
@@ -301,11 +307,7 @@ All RDB persistence backups, except for the most recent one, are automatically d
 
 Use a second storage account for AOF persistence when you think you've higher than expected set operations on the cache. Setting up the secondary storage account helps ensure your cache doesn't reach storage bandwidth limits. This option is only available for Premium tier caches.
 
-### Does AOF persistence affect throughput, latency, or performance of my cache?
-
-AOF persistence does affect throughput. AOF runs on both the primary and replica process, therefore you see both higher CPU and Server Load for a cache with AOF persistence, than for a cache with an identical workload without AOF persistence. AOF offers the best consistency with the data in memory because as each write and delete is persisted right away. The trade-off is that AOF is more compute intensive.
 
-As long as CPU and Server Load are both less than 90%, the penalty on throughput is not generally problematic. Above 90% CPU and Server Load, the penalty can get much higher. Persistence runs on the primary and replica process, increasing the load on the node in use, and putting persistence on the critical path of data. If persistence to storage is slow, then overall writes/deletes are also slow, also known as latency.
 
 ### How can I remove the second storage account?
 

articles/azure-cache-for-redis/cache-how-to-scale.md

@@ -15,7 +15,7 @@ ms.custom: devx-track-azurepowershell, devx-track-azurecli
 
 Azure Cache for Redis has different tier offerings that provide flexibility in the choice of cache size and features. Through scaling, you can change the size, tier, and number of nodes after creating a cache instance to match your application needs. This article shows you how to scale your cache using the Azure portal, plus tools such as Azure PowerShell and Azure CLI.
 
-## Types of Scaling
+## Types of scaling
 
 There are fundamentally two ways to scale an Azure Cache for Redis Instance:
 
@@ -60,7 +60,7 @@ For more information on determining the cache pricing tier to use, see [Choosing
 > For more information on how to optimize the scaling process, see the [best practices for scaling guide](cache-best-practices-scale.md)
 >
 
-## Prerequisites/Limitations of Scaling Azure Cache for Redis
+## Prerequisites/limitations of scaling Azure Cache for Redis
 
 You can scale up/down to a different pricing tier with the following restrictions:
 
@@ -89,15 +89,15 @@ You can scale out/in with the following restrictions:
 
 1. To scale your cache, [browse to the cache](cache-configure.md#configure-azure-cache-for-redis-settings) in the [Azure portal](https://portal.azure.com) and select **Scale** from the Resource menu.
 
-    :::image type="content" source="media/cache-how-to-scale/scale-a-cache.png" alt-text="scale on the resource menu":::
+    :::image type="content" source="media/cache-how-to-scale/scale-a-cache.png" alt-text="Screenshot showing Scale on the resource menu.":::
 
 1. Choose a pricing tier in the working pane and then choose **Select**.
 
-    :::image type="content" source="media/cache-how-to-scale/select-a-tier.png" alt-text="Azure Cache for Redis tiers":::
+    :::image type="content" source="media/cache-how-to-scale/select-a-tier.png" alt-text="Screenshot showing the Azure Cache for Redis tiers.":::
 
 1. While the cache is scaling to the new tier, a **Scaling Redis Cache** notification is displayed.
 
-    :::image type="content" source="media/cache-how-to-scale/scaling-notification.png" alt-text="notification of scaling":::
+    :::image type="content" source="media/cache-how-to-scale/scaling-notification.png" alt-text="Screenshot showing the notification of scaling.":::
 
 1.  When scaling is complete, the status changes from **Scaling** to **Running**.