edits

v-thepet · v-thepet · commit 0a756e835e67 · 2025-05-01T15:54:01.000-07:00
diff --git a/articles/azure-cache-for-redis/cache-best-practices-client-libraries.md b/articles/azure-cache-for-redis/cache-best-practices-client-libraries.md
@@ -20,6 +20,8 @@ Each client maintains reference documentation for its own library, and provides
 
 Microsoft and Azure Redis do recommend some libraries, based on popularity and whether there's an active online support community to answer questions. These libraries are under active development and often release new versions with reliability and performance improvements. Microsoft recommends using the latest available version, and upgrading regularly as new versions become available.
 
+The following table lists links and documentation for some recommended client libraries.
+
 | **Client library**  | **Language** |  **GitHub repo**                                  |          **Documentation**|
 | --------------------|------------- |-------------------------------------------------------| --------------------------|
 | StackExchange.Redis | C#/.NET |  [https://github.com/StackExchange/StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis)| [StackExchange.Redis](https://stackexchange.github.io/StackExchange.Redis/) |
@@ -62,15 +64,15 @@ Here are some recommended best practices for Redisson:
 
 - 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 [`CHANGELOG`](https://github.com/redisson/redisson/blob/master/CHANGELOG.md) and the [Redisson FAQ](https://github.com/redisson/redisson/wiki/16.-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.
 
 - 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.
+- 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).
 
diff --git a/articles/azure-cache-for-redis/cache-planning-faq.yml b/articles/azure-cache-for-redis/cache-planning-faq.yml
@@ -17,53 +17,54 @@ sections:
   - name: Ignored
     questions:
       - question: |
-          How can I benchmark Azure Cache for Redis performance?
+          Azure Cache for Redis performance
         answer: |
           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: |
-          In what region should I locate my cache?
-        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 that's mounted directly to the VMs and 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.
-          
-          >[!NOTE] 
-          >The Enterprise Flash tier also stores data on an ephemeral NVMe flash disk. This disk is mounted to the cache instance VM and therefore resides in the same region as the instance.
-          
-          You need to explicitly configure Azure Redis to use the preceding features. You also have complete control over the region where the storage account or secondary cache is located.
-          
-      - question: |
-          How am I billed for Azure Redis?
-        answer: |
-          For Azure Redis pricing, 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 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: |
           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 in these clouds compared with the Azure Public cloud.
+          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:
           
-          | Cloud   | DNS Suffix for Redis            |
+          | Cloud   | Domain Name System (DNS) suffix for Redis            |
           |---------|---------------------------------|
           | Public  | *.redis.cache.windows.net       |
           | US Government  | *.redis.cache.usgovcloudapi.net |
           | China   | *.redis.cache.chinacloudapi.cn  |
           
-          For more information on considerations for using Azure Redis with other clouds, see the following links:
+          For other considerations about using Azure Redis with other clouds, see the following links:
           
           - [Azure Government Databases](/azure/azure-government/compare-azure-government-global-azure)
           - [Azure operated by 21Vianet Cloud](https://www.azure.cn/home/features/redis-cache/)
           
-          For information on using Azure Redis with PowerShell in Azure Government Cloud and Azure operated by 21Vianet Cloud, see [How to connect to other clouds - PowerShell](../redis/how-to-manage-redis-cache-powershell.md#how-to-connect-to-other-clouds).
+          For information about using Azure Redis with PowerShell in Azure Government Cloud and Azure operated by 21Vianet Cloud, see [How to connect to other clouds - PowerShell](../redis/how-to-manage-redis-cache-powershell.md#how-to-connect-to-other-clouds).
           
           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?
+        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. 
+          
+          * 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.
+          
+            >[!NOTE] 
+            >The Enterprise Flash tier also stores data on an ephemeral NVMe flash disk. This disk is mounted to the cache instance VM and therefore resides in the same region as the instance.
+          
+          You need to explicitly configure Azure Redis to use the preceding features. You also have complete control over the region where the storage account or secondary cache is located.
+          
 additionalContent: |
 
   ## Related content
diff --git a/articles/azure-cache-for-redis/cache-tls-configuration.md b/articles/azure-cache-for-redis/cache-tls-configuration.md
@@ -54,7 +54,7 @@ To enable the non-TLS port:
 1. On the **Advanced settings** page, select **No** under **Allow access only via SSL**.
 1. Select **Save**.
 
-For more information, see [Access ports](cache-configure.md#access-ports):
+For more information, see [Access ports](cache-configure.md#access-ports).
 
 In clustered caches, TLS-enabled caches use ports in the `150XX` range, while non-TLS caches use ports in the `130XX` range. For more information, see [Can I directly connect to the individual shards of my cache?](cache-how-to-scale.md#can-i-directly-connect-to-the-individual-shards-of-my-cache)
 
