Merge pull request #260260 from flang-msft/docs-editor/cache-failover-1701748798

Update cache-failover.md

Author: prmerger-automator[bot]

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/28/2023
+ms.date: 12/04/2023
 ms.custom: engagement-fy23
 
 ---
@@ -114,7 +114,7 @@ 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 [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.
+Additionally, we recommend that you use scheduled updates to choose an update channel and a maintenance window for your 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 [Update channel and Schedule updates](cache-administration.md#update-channel-and-schedule-updates).
 
 For more information, see [Connection resilience](cache-best-practices-connection.md).