From 7cbd67427d3c1cffb46091c22f3d3522c9d00a72 Mon Sep 17 00:00:00 2001
From: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com>
Date: Tue, 9 Mar 2021 17:29:13 +0200
Subject: [PATCH] Update upgrading.md

---
 content/rs/installing-upgrading/upgrading.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/rs/installing-upgrading/upgrading.md b/content/rs/installing-upgrading/upgrading.md
index 4e715ff2925..53530ddfc05 100644
--- a/content/rs/installing-upgrading/upgrading.md
+++ b/content/rs/installing-upgrading/upgrading.md
@@ -141,7 +141,8 @@ When you upgrade an Active-Active (CRDB) database, you can also upgrade:
 - Upgrade all instances of a specific CRDB within a reasonable time frame to avoid temporary inconsistencies between the instances.
 - Make sure that you upgrade all instances of a specific CRDB before you do global operations on the CRDB, such as removing instances and adding new instances.
 - Protocol version 0 is deprecated on RS 6.0.20 or later.
-- Before upgrading to RS 6.0.20 or later, make sure all your Active-Active databases are set with their lastest protocol version. Otherwise upgrades will fail.
+- To avoid a failed upgrade, make sure all your Active-Active databases are configured with the latest protocol version before upgrading to Redis Enterprise Software 6.0.20 or later.
+
     {{< /note >}}
 
     After you upgrade an instance to use the new protocol version,
@@ -153,7 +154,7 @@ When you upgrade an Active-Active (CRDB) database, you can also upgrade:
     {{< note >}}
 
 - Feature set version 0 is deprecated on RS 6.0.20 or later.
-- Before upgrading to RS 6.0.20 or later, make sure all your Active-Active databases are set with their lastest feature set version. Otherwise upgrades will fail.
+- To avoid a failed upgrade, make sure all your Active-Active databases are configured with the latest feature set version before upgrading to Redis Enterprise Software 6.0.20 or later.
     {{< /note >}}
 
 To upgrade a CRDB instance: