fixed links

Author: flang-msft

articles/azure-cache-for-redis/TOC.yml

@@ -193,7 +193,7 @@
     - name: Reboot
       href: cache-administration.md#reboot
     - name: Schedule updates
-      href: cache-administration.md#schedule-updates
+      href: cache-administration.md#update-channel-and-schedule-updates
     - name: Configure redis-cli.exe access
       href: cache-how-to-redis-cli-tool.md
     - name: Create and manage a cache using CLI

articles/azure-cache-for-redis/cache-best-practices-connection.md

@@ -6,7 +6,7 @@ author: flang-msft
 
 ms.service: cache
 ms.topic: conceptual
-ms.date: 02/27/2023
+ms.date: 09/29/2023
 ms.author: franlanglois
 ---
 
@@ -22,7 +22,7 @@ Test your system's resiliency to connection breaks using a [reboot](cache-admini
 
 ## TCP settings for Linux-hosted client applications
 
-The default TCP settings in some Linux versions can cause Redis server connections to fail for 13 minutes or more. The default settings can prevent the client application from detecting closed connections and restoring them automatically if the connection wasn't closed gracefully. 
+The default TCP settings in some Linux versions can cause Redis server connections to fail for 13 minutes or more. The default settings can prevent the client application from detecting closed connections and restoring them automatically if the connection wasn't closed gracefully.
 
 The failure to reestablish a connection can happen in situations where the network connection is disrupted or the Redis server goes offline for unplanned maintenance.
 
@@ -77,19 +77,19 @@ Use notifications to learn of upcoming maintenance. For more information, see [C
 
 ## Schedule maintenance window
 
-Adjust your cache settings to accommodate maintenance. For more information about creating a maintenance window to reduce any negative effects to your cache, see [Schedule updates](cache-administration.md#schedule-updates).
+Adjust your cache settings to accommodate maintenance. For more information about creating a maintenance window to reduce any negative effects to your cache, see [Update channel and Schedule updates](cache-administration.md#update-channel-and-schedule-updates).
 
 ## More design patterns for resilience
 
 Apply design patterns for resiliency. For more information, see [How do I make my application resilient](cache-failover.md#how-do-i-make-my-application-resilient).
 
 ## Idle timeout
 
-Azure Cache for Redis has a 10-minute timeout for idle connections. The 10-minute timeout allows the server to automatically clean up leaky connections or connections orphaned by a client application. Most Redis client libraries have a built-in capability to send `heartbeat` or `keepalive` commands periodically to prevent connections from being closed even if there are no requests from the client application. 
+Azure Cache for Redis has a 10-minute timeout for idle connections. The 10-minute timeout allows the server to automatically clean up leaky connections or connections orphaned by a client application. Most Redis client libraries have a built-in capability to send `heartbeat` or `keepalive` commands periodically to prevent connections from being closed even if there are no requests from the client application.
 
 If there's any risk of your connections being idle for 10 minutes, configure the `keepalive` interval to a value less than 10 minutes. If your application is using a client library that doesn't have native support for `keepalive` functionality, you can implement it in your application by periodically sending a `PING` command.
 
-## Next steps
+## Related content
 
 - [Best practices for development](cache-best-practices-development.md)
 - [Azure Cache for Redis development FAQ](cache-development-faq.yml)

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

@@ -5,7 +5,7 @@ author: flang-msft
 
 ms.service: cache
 ms.topic: conceptual
-ms.date: 11/21/2022
+ms.date: 09/29/2023
 ms.author: franlanglois 
 ms.custom: engagement-fy23
 ---
@@ -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, 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.
@@ -264,7 +264,7 @@ The **Schedule updates** section on the left allows you to choose a maintenance
 
 To specify a maintenance window, check the days you want. Then, specify the maintenance window start hour for each day, and select **OK**. The maintenance window time is in UTC.
 
-For more information and instructions, see [Azure Cache for Redis administration - Schedule updates](cache-administration.md#schedule-updates)
+For more information and instructions, see [Update channel and Schedule updates](cache-administration.md#update-channel-and-schedule-updates).
 
 ### Geo-replication
 
@@ -478,7 +478,7 @@ New Azure Cache for Redis instances are configured with the following default Re
 | `lua-event-limit` |500 |Max size of script event queue. |
 | `client-output-buffer-limit normal` / `client-output-buffer-limit pubsub` |`0 0 0` / `32mb 8mb 60` |The client output buffer limits can be used to force disconnection of clients that aren't reading data from the server fast enough for some reason. A common reason is that a Pub/Sub client can't consume messages as fast as the publisher can produce them. For more information, see [https://redis.io/topics/clients](https://redis.io/topics/clients). |
 
-<a name="databases"></a>
+### Databases
 
 <sup>1</sup>The limit for `databases` is different for each Azure Cache for Redis pricing tier and can be set at cache creation. If no `databases` setting is specified during cache creation, the default is 16.
 
@@ -504,9 +504,9 @@ For more information about databases, see [What are Redis databases?](cache-deve
 > The `databases` setting can be configured only during cache creation and only using PowerShell, CLI, or other management clients. For an example of configuring `databases` during cache creation using PowerShell, see [New-AzRedisCache](cache-how-to-manage-redis-cache-powershell.md#databases).
 >
 
-<a name="maxclients"></a>
+### Maxclients
 
-<sup>2</sup>`maxclients` is different for each Azure Cache for Redis pricing tier.
+<sup>2</sup>The `maxclients` property is different for each Azure Cache for Redis pricing tier.
 
 - Basic and Standard caches
   - C0 (250 MB) cache - up to 256 connections
@@ -556,8 +556,7 @@ For cache instances using active geo-replication, the following commands are als
 
 For more information about Redis commands, see [https://redis.io/commands](https://redis.io/commands).
 
-## Next steps
+## Related content
 
 - [How can I run Redis commands?](cache-development-faq.yml#how-can-i-run-redis-commands-)
 - [Monitor Azure Cache for Redis](cache-how-to-monitor.md)
-

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

@@ -6,7 +6,7 @@ author: flang-msft
 ms.author: franlanglois
 ms.service: cache
 ms.topic: conceptual
-ms.date: 11/16/2022
+ms.date: 09/29/2023
 ms.custom: engagement-fy23
 
 ---
@@ -114,12 +114,12 @@ Refer to these design patterns to build resilient clients, especially the circui
 
 To test a client application's resiliency, use a [reboot](cache-administration.md#reboot) as a manual trigger for connection breaks.
 
-Additionally, we recommend that you [schedule updates](cache-administration.md#schedule-updates) on a cache to apply Redis runtime patches during specific weekly windows. These windows are typically periods when client application traffic is low, to avoid potential incidents.
+Additionally, we recommend that you [Update channel and Schedule updates](cache-administration.md#update-channel-and-schedule-updates) on a cache to apply Redis runtime patches during specific weekly windows. These windows are typically periods when client application traffic is low, to avoid potential incidents.
 
 For more information, see [Connection resilience](cache-best-practices-connection.md).
 
-## Next steps
+## Related content
 
-- [Schedule updates](cache-administration.md#schedule-updates) for your cache.
-- Test application resiliency by using a [reboot](cache-administration.md#reboot).
-- [Configure](cache-configure.md#memory-policies) memory reservations and policies.
+- [Update channel and Schedule updates](cache-administration.md#update-channel-and-schedule-updates)
+- Test application resiliency by using a [reboot](cache-administration.md#reboot)
+- [Configure](cache-configure.md#memory-policies) memory reservations and policies

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

@@ -6,7 +6,7 @@ ms.author: franlanglois
 ms.service: cache
 ms.custom: ignite-2022
 ms.topic: overview
-ms.date: 03/28/2023
+ms.date: 09/29/2023
 ---
 
 # About Azure Cache for Redis
@@ -63,10 +63,10 @@ The [Azure Cache for Redis Pricing](https://azure.microsoft.com/pricing/details/
 | [Redis Modules](cache-redis-modules.md) |-|-|-|✔|Preview|
 | [Import/Export](cache-how-to-import-export-data.md) |-|-|✔|✔|✔|
 | [Reboot](cache-administration.md#reboot) |✔|✔|✔|-|-|
-| [Scheduled updates](cache-administration.md#schedule-updates) |✔|✔|✔|-|-|
+| [Update channel and Schedule updates](cache-administration.md#update-channel-and-schedule-updates) |✔|✔|✔|-|-|
 
 > [!NOTE]
-> The Enterprise Flash tier currently supports only the RediSearch module (in preview) and the RedisJSON module. 
+> The Enterprise Flash tier currently supports only the RediSearch module (in preview) and the RedisJSON module.
 
 ### Choosing the right tier
 
@@ -103,7 +103,7 @@ The Enterprise tiers rely on Redis Enterprise, a commercial variant of Redis fro
 
 Azure Cache for Redis is continually expanding into new regions. To check the availability by region, see [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=redis-cache&regions=all).
 
-## Next steps
+## Related content
 
 - [Create an open-source Redis cache](quickstart-create-redis.md)
 - [Create a Redis Enterprise cache](quickstart-create-redis-enterprise.md)

articles/azure-cache-for-redis/cache-troubleshoot-timeouts.md

@@ -6,7 +6,7 @@ ms.author: franlanglois
 ms.service: cache
 ms.topic: conceptual
 ms.custom: devx-track-csharp
-ms.date: 12/30/2021
+ms.date: 09/29/2023
 ---
 
 # Troubleshoot Azure Cache for Redis latency and timeouts
@@ -31,7 +31,7 @@ This section discusses troubleshooting for latency and timeout issues that occur
   - [StackExchange.Redis timeout exceptions](#stackexchangeredis-timeout-exceptions)
 
 > [!NOTE]
-> Several of the troubleshooting steps in this guide include instructions to run Redis commands and monitor various performance metrics. For more information and instructions, see the articles in the [Additional information](#additional-information) section.
+> Several of the troubleshooting steps in this guide include instructions to run Redis commands and monitor various performance metrics. For more information and instructions, see the articles in the [Additional information](#related-content) section.
 >
 
 ## Client-side troubleshooting
@@ -98,7 +98,6 @@ Because of optimistic TCP settings in Linux, client applications hosted on Linux
 If you're using `RedisSessionStateProvider`, ensure you have set the retry timeout correctly. The `retryTimeoutInMilliseconds` value should be higher than the `operationTimeoutInMilliseconds` value. Otherwise, no retries occur. In the following example, `retryTimeoutInMilliseconds` is set to 3000. For more information, see [ASP.NET Session State Provider for Azure Cache for Redis](cache-aspnet-session-state-provider.md) and [How to use the configuration parameters of Session State Provider and Output Cache Provider](https://github.com/Azure/aspnet-redis-providers/wiki/Configuration).
 
  ```xml
- 
  <add 
     name="AFRedisCacheSessionStateProvider"
     type="Microsoft.Web.Redis.RedisSessionStateProvider"
@@ -120,9 +119,9 @@ If you're using `RedisSessionStateProvider`, ensure you have set the retry timeo
 
 Planned or unplanned maintenance can cause disruptions with client connections. The number and type of exceptions depends on the location of the request in the code path, and when the cache closes its connections. For instance, an operation that sends a request but hasn't received a response when the failover occurs might get a time-out exception. New requests on the closed connection object receive connection exceptions until the reconnection happens successfully.
 
-For information, check these other sections:
+For more information, check these other sections:
 
-- [Scheduling updates](cache-administration.md#schedule-updates)
+- [Update channel and Schedule updates](cache-administration.md#update-channel-and-schedule-updates)
 - [Connection resilience](cache-best-practices-connection.md#connection-resilience)
 - `AzureRedisEvents` [notifications](cache-failover.md#can-i-be-notified-in-advance-of-planned-maintenance)
 
@@ -191,9 +190,7 @@ To mitigate situations where network bandwidth usage is close to maximum capacit
 
 For more specific information to address timeouts when using StackExchange.Redis, see [Investigating timeout exceptions in StackExchange.Redis](https://azure.microsoft.com/blog/investigating-timeout-exceptions-in-stackexchange-redis-for-azure-redis-cache/).
 
-## Additional information
-
-See these articles for additional information about latency issues and timeouts.
+## Related content
 
 - [Troubleshoot Azure Cache for Redis client-side issues](cache-troubleshoot-client.md)
 - [Troubleshoot Azure Cache for Redis server-side issues](cache-troubleshoot-server.md)