Merge pull request #218671 from flang-msft/fxl-details-about-upgrade-process

Fxl details about upgrade process

Author: prmerger-automator[bot]

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

@@ -5,7 +5,7 @@ author: flang-msft
 ms.author: franlanglois
 ms.service: cache
 ms.topic: conceptual
-ms.date: 03/15/2022
+ms.date: 11/16/2022
 
 ---
 
@@ -49,9 +49,10 @@ An *unplanned failover* might happen because of hardware failure, network failur
 
 The Azure Cache for Redis service regularly updates your cache with the latest platform features and fixes. To patch a cache, the service follows these steps:
 
-1. The management service selects one node to be patched.
-1. If the selected node is a primary node, the corresponding replica node cooperatively promotes itself. This promotion is considered a planned failover.
-1. The selected node reboots to take the new changes and comes back up as a replica node.
+1. The management service selects the node to be patched.
+1. The replica node is patched.
+1. The patched replica cooperatively promotes itself to primary. This promotion is considered a planned failover.
+1. The former primary node reboots to take the new changes and comes back up as a replica node.
 1. The replica node connects to the primary node and synchronizes data.
 1. When the data sync is complete, the patching process repeats for the remaining nodes.
 

articles/azure-cache-for-redis/cache-how-to-upgrade.md

@@ -6,14 +6,17 @@ author: flang-msft
 ms.author: franlanglois
 ms.service: cache
 ms.topic: how-to
-ms.date: 09/29/2022
+ms.date: 11/16/2022
 ms.custom: template-how-to 
+
 ---
 
 
 # How to upgrade an existing Redis 4 cache to Redis 6
 
-Azure Cache for Redis supports upgrading the version of your Azure Cache for Redis from Redis 4 to Redis 6. Upgrading is permanent, and it might cause a brief connection issue similar to regular monthly maintenance. As a precautionary step, we recommend exporting the data from your existing Redis 4 cache and testing your client application with a Redis 6 cache in a lower environment before upgrading.
+Azure Cache for Redis supports upgrading the version of your Azure Cache for Redis from Redis 4 to Redis 6. Upgrading is similar to regular monthly maintenance. Upgrading follows the same pattern as maintenance: First, the Redis version on the replica node is updated, followed by an update to the primary node. Your client application should treat the upgrade operation exactly like a planned maintenance event.
+
+As a precautionary step, we recommend exporting the data from your existing Redis 4 cache and testing your client application with a Redis 6 cache in a lower environment before upgrading.
 
 For more details on how to export, see [Import and Export data in Azure Cache for Redis](cache-how-to-import-export-data.md).