From d2a397361f926ad9cb09b99dc0558bb717b4a615 Mon Sep 17 00:00:00 2001
From: rebekah-lawrence <142301480+rebekah-lawrence@users.noreply.github.com>
Date: Mon, 29 Apr 2024 11:46:03 +0100
Subject: [PATCH] Docs 548 rolling upgrades jet job (#1094)

* Noting that Jet doesn't support RU

Originally raised from this Slack thread: https://hazelcast.slack.com/archives/CJZ745RRT/p1685950448256829

Addressing before starting the LTS Upgradeability drafting for a clean slate.

* Making sure I don't undo Jack's EE/OS variable work
---
 docs/modules/maintain-cluster/pages/rolling-upgrades.adoc | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/modules/maintain-cluster/pages/rolling-upgrades.adoc b/docs/modules/maintain-cluster/pages/rolling-upgrades.adoc
index db4f5e0a4..8c13ffc9b 100644
--- a/docs/modules/maintain-cluster/pages/rolling-upgrades.adoc
+++ b/docs/modules/maintain-cluster/pages/rolling-upgrades.adoc
@@ -48,6 +48,8 @@ As a result, you can use rolling upgrades to upgrade clusters to the following m
 +
 This also includes the ability of rolling upgrade from Hazelcast IMDG 4.2 to Platform 5.0, since IMDG is part of the Platform and 5.0 is considered to be the next minor version after IMDG 4.2.
 
+NOTE: Following the rolling upgrade, you must resubmit jobs as they don't run during the upgrade. For further information on the compatibility of job states in upgrades, see xref:deploy:versioning-compatibility.adoc#job-states[Versioning and Compatibility].
+
 [[rolling-upgrade-procedure]]
 == Performing a Rolling Upgrade
 
@@ -61,7 +63,7 @@ During migrations, members cannot join or leave the cluster.
 
 . Upgrade the member's codebase to a new patch version or the next minor version.
 +
-NOTE: To upgrade the codebase to the next minor version, you need an {enterprise-product-name} license.
+NOTE: To upgrade the codebase to the next minor version, you need an Enterprise license.
 
 . Start the member and wait until it joins the cluster.
 +
@@ -142,7 +144,7 @@ to merge as soon as the network partition is fixed.
 
 == Using Rolling Restarts to Switch to High-Density Memory Store
 
-As a Hazelcast Platform {enterprise-product-name} user, you can perform a rolling restart on your cluster to start using xref:storage:high-density-memory.adoc[High-Density Memory Store] in your maps.
+As a Hazelcast Platform Enterprise user, you can perform a rolling restart on your cluster to start using xref:storage:high-density-memory.adoc[High-Density Memory Store] in your maps.
 
 For this you need to: