Lts update (#1258)

hazelcast · Aug 15, 2024 · 1f616b4 · 1f616b4
1 parent f6a0d86
commit 1f616b4
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/modules/maintain-cluster/pages/rolling-upgrades.adoc b/docs/modules/maintain-cluster/pages/rolling-upgrades.adoc
@@ -49,7 +49,7 @@ determines the feature set exposed by the cluster.
 [[hazelcast-members-compatibility]]
 === Upgrade Compatibility
 
-To allow you to use rolling upgrades, Hazelcast maintains the following GA (general availability) release compatibility:
+To allow you to use rolling upgrades, Hazelcast provides the following GA (general availability) release compatibility:
 
 - Hazelcast members operating on the same major and minor
 cluster version are always compatible, regardless of patch version.

diff --git a/docs/modules/migrate/pages/lts.adoc b/docs/modules/migrate/pages/lts.adoc
@@ -57,7 +57,7 @@ NOTE: Hazelcast has tested WAN Replication to validate the upgrade solution. The
 
 == Mixed-version Clusters
 
-Your LTS release member can join clusters that include members from an earlier supported version. You cannot have members from more than two different minor versions in the same cluster.
+Your LTS release member can join clusters that include members from an earlier supported version. However, it cannot join members with more than two different minor versions in the same cluster.
 
 The following table provides an example of the behaviour:
 
@@ -78,7 +78,7 @@ The following table provides an example of the behaviour:
 |Further member tries to join cluster
 |5.5 LTS
 |5.2
-|LTS member identifies that two different minor versions are already in the cluster and rejects joining the cluster
+|LTS member identifies that two different minor versions are already in the cluster (5.2 and 5.3) and rejects joining the cluster
 |===
 
 The scenario outlined below can occur because the logic for a mixed-version cluster is introduced in the first LTS release and cannot be enforced by earlier releases.
@@ -98,7 +98,7 @@ Hazelcast recommends that you avoid the following scenario:
 |Member tries to join cluster
 |5.5 LTS
 |5.2
-|Member identifies that only one minor version is already in the cluster and joins the cluster
+|Member identifies that only one minor version (5.2) is already in the cluster and joins the cluster
 
 |Further member tries to join cluster
 |5.3