edits

Author: v-thepet

articles/azure-cache-for-redis/cache-best-practices-memory-management.md

@@ -36,27 +36,27 @@ Large key values can leave memory fragmented on eviction and might lead to high
 
 Configure your [maxmemory-reserved settings](cache-configure.md#memory-policies) to maximize system responsiveness. Sufficient reservation settings are especially important for write-heavy workloads, or if you're storing values of 100 KB or more in your cache.
 
-The `maxmemory-reserved` setting configures the amount of memory, in MB per instance in a cluster, that's reserved for non-cache operations, such as replication during failover. Setting this value allows you to have a more consistent Redis server experience when your load varies.
+- The `maxmemory-reserved` setting configures the amount of memory, in MB per instance in a cluster, reserved for noncache operations such as replication during failover. Setting this value allows you to have a more consistent Redis server experience when your load varies.
 
-The `maxfragmentationmemory-reserved` setting configures the amount of memory, in MB per instance in a cluster, that's reserved to accommodate memory fragmentation. When you set this value, the Redis server experience is more consistent when the cache is full or close to full and the fragmentation ratio is high.
+- The `maxfragmentationmemory-reserved` setting configures the amount of memory, in MB per instance in a cluster, reserved to accommodate memory fragmentation. When you set this value, the Redis server experience is more consistent when the cache is full or close to full and the fragmentation ratio is high.
 
-When memory is reserved for these operations, it's unavailable for storing cached data. By default when you create a cache, approximately 10% of the available memory is reserved for `maxmemory-reserved`, and another 10% is reserved for `maxfragmentationmemory-reserved`. You can increase the amounts reserved if you have write-heavy loads. The allowed ranges for `maxmemory-reserved` and for `maxfragmentationmemory-reserved` are 10%-60% of `maxmemory`. If you try to set these values lower than 10% or higher than 60%, they are reevaluated and set to the 10% minimum and 60% maximum.
+When memory is reserved for these operations, it's unavailable for storing cached data. By default when you create a cache, approximately 10% of the available memory is reserved for `maxmemory-reserved`, and another 10% is reserved for `maxfragmentationmemory-reserved`. You can increase the amounts reserved if you have write-heavy loads.
 
-When you scale a cache up or down, both `maxmemory-reserved` and `maxfragmentationmemory-reserved` settings automatically scale in proportion to the cache size. For example, if `maxmemory-reserved` is set to 50% on a 6-GB cache, and you scale to a 12-GB cache, the setting automatically updates from 3 GB to 6 GB during scaling. If you scale down, the reverse happens.
+The allowed ranges for `maxmemory-reserved` and for `maxfragmentationmemory-reserved` are 10%-60% of `maxmemory`. If you try to set these values lower than 10% or higher than 60%, they're reevaluated and set to the 10% minimum and 60% maximum.
 
-If you change a `maxmemory-reserved` or `maxfragmentationmemory-reserved` memory reservation value, consider how this change might affect a cache with large amounts of data in it that is already running. For instance, if you have a 53-GB cache with the reserved values set to the minimums of 10 GB, the maximum available memory for the system is approximately 42 GB.
+When you scale a cache up or down, both `maxmemory-reserved` and `maxfragmentationmemory-reserved` settings automatically scale in proportion to the cache size. For example, if `maxmemory-reserved` is set to 3 GB on a 6-GB cache, and you scale to a 12-GB cache, the setting automatically updates to 6 GB during scaling. If you scale down, the reverse happens.
 
-If either your current `used_memory` or `used_memory_rss` values are higher than the limit of 42 GB, the system must evict data until both `used_memory` and `used_memory_rss` are below 42 GB. Eviction can increase server load and memory fragmentation.
+Consider how changing a `maxmemory-reserved` or `maxfragmentationmemory-reserved` memory reservation value might affect a cache with a large amount of data in it that is already running. For instance, if you have a 53-GB cache with the reserved values set to the 10% minimums, the maximum available memory for the system is approximately 42 GB. If either your current `used_memory` or `used_memory_rss` values are higher than 42 GB, the system must evict data until both `used_memory` and `used_memory_rss` are below 42 GB.
 
-For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](/azure/redis/monitor-cache#create-your-own-metrics).
+Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](/azure/redis/monitor-cache#create-your-own-metrics).
 
 > [!NOTE]
-> When you scale a cache up or down programmatically by using Azure PowerShell, Azure CLI, or REST API, any `maxmemory-reserved` and `maxfragmentationmemory-reserved` settings are ignored as part of the update request. Only your scaling change is honored. You can update the memory settings after the scaling operation has completed.
+> When you scale a cache up or down programmatically by using Azure PowerShell, Azure CLI, or REST API, any `maxmemory-reserved` and `maxfragmentationmemory-reserved` settings are ignored as part of the update request. Only your scaling change is honored. You can update the memory settings after the scaling operation completes.
 
 ## Next steps
 
 - [Memory policies](cache-configure.md#memory-policies)
-- [Troubleshoot high memory usage](cache-troubleshoot-timeouts.md#high-memory-usage
+- [Troubleshoot high memory usage](cache-troubleshoot-timeouts.md#high-memory-usage)
 - [Best practices for scaling](cache-best-practices-scale.md)
 - [Best practices for development](cache-best-practices-development.md)
 - [Azure Cache for Redis development FAQs](cache-development-faq.yml)