touchups

Author: v-thepet

articles/azure-cache-for-redis/cache-best-practices-client-libraries.md

@@ -12,7 +12,7 @@ ms.custom: devx-track-java, devx-track-javaee, devx-track-javaee-liberty, devx-t
 
 # Client libraries
 
-Azure Cache for Redis is based on the open-source, in-memory data store Redis. Redis clients for many programming languages can access Azure Redis. Your application can use any client library that's compatible with open-source Redis to connect to your Azure Redis cache.
+Azure Cache for Redis is based on the Redis open-source, in-memory data store. Redis clients for many programming languages can access Azure Redis. Your application can use any client library that's compatible with open-source Redis to connect to your Azure Redis cache.
 
 Each client library has its own API that calls Redis servers using Redis commands. The client libraries are built to communicate with any Redis server.
 
@@ -60,21 +60,21 @@ Besides the reference documentation, you can use the following tutorials to get
 
 ## Best practices for Redisson (Java)
 
-Here are some recommended best practices for Redisson:
+Here are some recommended best practices for the Redisson client library:
 
 - Use Redisson 3.14.1 or higher. Older versions contain known connection leak issues that cause problems after failovers.
 
-- Monitor the Redisson changelog for known issues that can affect features your application uses. For more information, see [`CHANGELOG`](https://github.com/redisson/redisson/blob/master/CHANGELOG.md) and the [Redisson FAQ](https://github.com/redisson/redisson/wiki/16.-FAQ).
+- Monitor the Redisson changelog for known issues that can affect features your application uses. For more information, see the [Redisson Releases History](https://github.com/redisson/redisson/blob/master/CHANGELOG.md) and the [Redisson FAQ](https://redisson.pro/docs/faq/).
 
-- If you don't want to use the *read from replica* strategy, modify the `readMode` config setting. Unlike some other clients, Redisson uses *read from replica* as the default.
+- Modify the `readMode` config setting if you don't want to use the *read from replica* strategy. Unlike some other clients, Redisson uses *read from replica* as the default.
 
 - To reduce the risk of aggressive reconnect behaviors or *connection storms*, consider setting fewer minimum connections.
 
   Redisson has a connection pooling strategy with configurable minimum and maximum settings, and the default minimum values are large. The large defaults could contribute to aggressive reconnect behaviors or connection storms. To reduce this risk, consider using fewer connections. You can efficiently pipeline commands or batches of commands over a few connections.
 
 - Reset the idle connection timeout if necessary. Redisson has a default 10-second idle connection timeout, which can lead to more closing and reopening of connections than ideal.
 
-- For an article about Redisson's support for JCache as the store for HTTP session state in IBM Liberty on Azure, see [Use Java EE JCache with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache).
+- For an article about Redisson support for Java EE JCache as the store for HTTP session state in IBM Liberty on an Azure Kubernetes Service (AKS) cluster, see [Using Azure Redis as session cache for WebSphere Liberty or Open Liberty](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache).
 
 - Use the following recommended baseline configuration for cluster mode, and modify it as needed.
 

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

@@ -22,15 +22,20 @@ sections:
           For guidance on how to benchmark Azure Redis cache performance and for sample benchmarking numbers, see [Performance testing](cache-best-practices-performance.md#example-performance-benchmark-data).
           
       - question: |
-          Can I use Azure Redis with Azure Government Cloud or Azure operated by 21Vianet Cloud?
+          How am I billed for Azure Redis?
+        answer: |
+          For details about Azure Redis billing, see [Azure Cache for Redis pricing](https://azure.microsoft.com/pricing/details/cache/). The pricing page lists pricing as an hourly and monthly rate. Caches are billed on a per-minute basis. The billing period is measured from time a cache is created until the time that the cache is deleted. There's no option for stopping or pausing cache billing.
+          
+      - question: |
+          How can I use Azure Redis with Azure Government Cloud or Azure operated by 21Vianet Cloud?
         answer: |
-          Yes, the Basic, Standard, and Premium tiers of Azure Redis are available in Azure Government Cloud and Azure operated by 21Vianet Cloud. The URLs for accessing and managing Azure Redis are different for these clouds than for the Azure Public cloud, as shown in the following table:
+          The Basic, Standard, and Premium tiers of Azure Redis are available in Azure Government Cloud and Azure operated by 21Vianet Cloud. The URLs for accessing and managing Azure Redis are different for these clouds than for the Azure Public cloud, as shown in the following table:
           
           | Cloud   | Domain Name System (DNS) suffix for Redis            |
           |---------|---------------------------------|
           | Public  | *.redis.cache.windows.net       |
           | US Government  | *.redis.cache.usgovcloudapi.net |
-          | China   | *.redis.cache.chinacloudapi.cn  |
+          | 21Vianet Cloud (China)   | *.redis.cache.chinacloudapi.cn  |
           
           For other considerations about using Azure Redis with other clouds, see the following links:
           
@@ -42,20 +47,15 @@ sections:
           The Azure Redis Enterprise and Enterprise Flash tiers are available only in the Public cloud.
           
       - question: |
-          How am I billed for Azure Redis?
-        answer: |
-          For details about Azure Redis billing, see [Azure Cache for Redis pricing](https://azure.microsoft.com/pricing/details/cache/). The pricing page lists pricing as an hourly and monthly rate. Caches are billed on a per-minute basis. The billing period is measured from time a cache is created until the time that the cache is deleted. There's no option for stopping or pausing cache billing.
-          
-      - question: |
-          In what region should I locate my cache?
+          What region should I locate my cache in?
         answer: |
           For best performance and lowest latency, locate your Azure Redis cache in the same Azure region as your cache client application.
           
       - question: |
           Where does my cached data reside?
         answer: |
          In Azure Cache for Redis, your application data is stored in the RAM of the virtual machine (VM) or VMs, depending on the tier, that host your cache. By default, your data resides in the Azure region you selected. There are two cases where your data might leave a region:
-          * When you enable data persistence on a Premium-tier cache, Azure Cache for Redis backs up your data to an Azure Storage account. If your storage account is in another region, or replicates data through [geo-redundant storage (GRS)](/azure/storage/common/storage-redundancy#redundancy-in-a-secondary-region) to a different region, a copy of your data ends up there. The Enterprise and Enterprise Flash tiers use on-disk persistence mounted directly to the VMs and doesn't leave the region. 
+          * When you enable data persistence on a Premium-tier cache, Azure Cache for Redis backs up your data to an Azure Storage account. If your storage account is in another region, or replicates data through [geo-redundant storage (GRS)](/azure/storage/common/storage-redundancy#redundancy-in-a-secondary-region) to a different region, a copy of your data ends up there. The Enterprise and Enterprise Flash tiers use on-disk persistence mounted directly to the VMs that doesn't leave the region. 
           
           * If you set up [passive geo-replication](cache-how-to-geo-replication.md) on a Premium-tier cache and your secondary cache is in a different region, as is typical, your data is replicated to that region.
           If you set up [active geo-replication]() on an Enterprise or Enterprise Flash tier cache, your data is replicated to each cache in the geo-replication group. If caches in the geo-replication group reside in other regions, as is typical, your data is replicated to those regions.