From 28584c8b8d930e5b2de887106794e53321b3d7e1 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Mon, 20 Oct 2025 10:47:25 +0200 Subject: [PATCH] fix(red): fix --- .../api-cli/upgrade-redis-version.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/managed-databases-for-redis/api-cli/upgrade-redis-version.mdx b/pages/managed-databases-for-redis/api-cli/upgrade-redis-version.mdx index dc311d0ea1..496d09214f 100644 --- a/pages/managed-databases-for-redis/api-cli/upgrade-redis-version.mdx +++ b/pages/managed-databases-for-redis/api-cli/upgrade-redis-version.mdx @@ -81,5 +81,5 @@ You can list your Database Instances to determine which ones need to be updated. If the operation is successful you will see the configuration of your Instance, with the updated version. - If your Database Instance is in standalone mode, there might be a few seconds of downtime while the Instance upgrades. For High Availability and Cluster modes, the upgrade is performed first on secondary nodes, then the main node. When the main node is upgraded, one of the secondary nodes takes over automatically to reduce downtime. + If your Database Instance is in standalone mode, there might be a few seconds of downtime while the Instance upgrades. For High Availability and Cluster modes, the upgrade is performed on one node at a time. When a node is upgraded, one of the secondary nodes takes over automatically to reduce downtime. \ No newline at end of file