misc. edits

Author: ktoliver

articles/azure-cache-for-redis/cache-development-faq.yml

@@ -55,11 +55,11 @@ sections:
             * Set the `ConnectionMultiplexer.ClientName` property to an app instance unique name for diagnostic purposes.
             * Use multiple `ConnectionMultiplexer` instances for custom workloads.
 
-              You can follow this model if you have varying load in your application. For example:
+              You can follow this model if you have varying loads in your application. For example:  
 
               * You can have one multiplexer for dealing with large keys.
               * You can have one multiplexer for dealing with small keys.
-              * You can set different values for connection timeouts and retry logic for each ConnectionMultiplexer that you use.
+              * You can set different values for connection timeouts and retry logic for each `ConnectionMultiplexer` that you use.
               * Set the `ClientName` property on each multiplexer to help with diagnostics.
               
               Following this guidance might lead to more streamlined latency per `ConnectionMultiplexer`.

articles/azure-cache-for-redis/cache-dotnet-core-quickstart.md

@@ -12,7 +12,7 @@ ms.date: 03/25/2022
 
 # Quickstart: Use Azure Cache for Redis with a .NET Core app
 
-In this quickstart, you incorporate Azure Cache for Redis into a .NET Core app to have access to a secure, dedicated cache that is accessible from any application in Azure. You specifically use the [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) client with C# code in a .NET Core console app.
+In this quickstart, you incorporate Azure Cache for Redis into a .NET Core app for access to a secure, dedicated cache that is accessible from any application in Azure. You specifically use the [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) client with C# code in a .NET Core console app.
 
 ## Skip to the code
 

articles/azure-cache-for-redis/cache-dotnet-how-to-use-azure-redis-cache.md

@@ -12,7 +12,7 @@ ms.date: 03/25/2022
 
 # Quickstart: Use Azure Cache for Redis with a .NET app
 
-In this quickstart, you incorporate Azure Cache for Redis into a .NET app to access a secure, dedicated cache that is accessible from any application in Azure. You specifically use the [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) client with C# code in a .NET console app.
+In this quickstart, you incorporate Azure Cache for Redis into a .NET app for access to a secure, dedicated cache that is accessible from any application in Azure. You specifically use the [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) client with C# code in a .NET console app.
 
 ## Skip to the code on GitHub
 

articles/azure-cache-for-redis/cache-management-faq.yml

@@ -39,7 +39,7 @@ sections:
           ### StackExchange.Redis best practices
 
           * Set `AbortConnect` to false, then let the ConnectionMultiplexer reconnect automatically.
-          * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request. For an example of how to manage a connection, see the `RedisConnection` class in [Connect to the cache by using Redisconnection](cache-dotnet-how-to-use-azure-redis-cache.md#connect-to-the-cache-by-using-redisconnection).
+          * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request. For an example of how to manage a connection, see the `RedisConnection` class in [Connect to the cache by using RedisConnection](cache-dotnet-how-to-use-azure-redis-cache.md#connect-to-the-cache-by-using-redisconnection).
           * Redis works best with smaller values, so consider chopping up bigger data into multiple keys. In [this Redis discussion](https://groups.google.com/forum/#!searchin/redis-db/size/redis-db/n7aa2A4DZDs/3OeEPHSQBAAJ), 100 kb is considered large. For more information, see [Best practices development](cache-best-practices-development.md#consider-more-keys-and-smaller-values).
           * Configure your [ThreadPool settings](#important-details-about-threadpool-growth) to avoid timeouts.
           * Use at least the default connectTimeout of 5 seconds. This interval gives StackExchange.Redis sufficient time to re-establish the connection if there's a network blip.