fixed PRMerge issues

Author: flang-msft

articles/azure-cache-for-redis/cache-administration.md

@@ -78,7 +78,7 @@ No. Reboot isn't available for the Enterprise tier yet. Reboot is available for
 
 ## Flush data (preview)
 
-When using th Basic, Standard, or Premium tiers of Azure Cache for Redis, you see **Flush data** on the resource menu. The **Flush data** operation allows you to delete or _flush_ all data in your cache. This _flush_ operation can be used before scaling operations to potentially reduce the time required to complete the scaling operation on your cache. You can also configure to run the _flush_ operation periodically on your dev/test caches to keep memory usage in check.
+When using the Basic, Standard, or Premium tiers of Azure Cache for Redis, you see **Flush data** on the resource menu. The **Flush data** operation allows you to delete or _flush_ all data in your cache. This _flush_ operation can be used before scaling operations to potentially reduce the time required to complete the scaling operation on your cache. You can also configure to run the _flush_ operation periodically on your dev/test caches to keep memory usage in check.
 
 The _flush_ operation, when executed on a clustered cache, clears data from all shards at the same time.
 

articles/azure-cache-for-redis/cache-configure.md

@@ -185,7 +185,7 @@ Use the **Maxmemory policy**, **maxmemory-reserved**, and **maxfragmentationmemo
 
 **Maxmemory policy** configures the eviction policy for the cache and allows you to choose from the following eviction policies:
 
-- `volatile-lru`: The default eviction policy, removes the least recently used key out of all the keys with an expiration set.
+- `volatile-lru`: The default eviction policy. It removes the least recently used key out of all the keys with an expiration set.
 - `allkeys-lru`: Removes the least recently used key.
 - `volatile-random`: Removes a random key that has an expiration set.
 - `allkeys-random`: Removes a random key.

articles/azure-cache-for-redis/cache-whats-new.md

@@ -31,7 +31,7 @@ For more information, see [update channels](cache-administration.md#update-chann
 
 ### Remove TLS 1.0 and 1.1 from use with Azure Cache for Redis
 
-To meet the industry-wide push toward the exclusive use of Transport Layer Security (TLS) version 1.2 or later, Azure Cache for Redis is moving toward requiring the use of the TLS 1.2 in October  2024.
+To meet the industry-wide push toward the exclusive use of Transport Layer Security (TLS) version 1.2 or later, Azure Cache for Redis is moving toward requiring the use of TLS 1.2 in October 2024.
 
 As a part of this effort, you can expect the following changes to Azure Cache for Redis: