wording changes

Author: kaitlynmichael

content/operate/kubernetes/release-notes/8-0-2-releases/8-0-2-2-october2025.md

@@ -136,7 +136,7 @@ Any distribution not listed in the table is not supported for production workloa
 
 - **Only upgrades from 7.4.2-2 and later are supported.** If you are using an earlier version, install 7.4.2-2 before upgrading to 8.0.2-2.
 
-- **Upgrading redisVersion overrides moduleList versions.** When upgrading a database's `redisVersion`, any module versions specified in `moduleList` are overridden by the bundled module versions for that Redis version. This applies to both REDB and REAADB databases.
+- **You must keep existing moduleList version numbers when upgrading redisVersion.** When upgrading a database's `redisVersion`, you must keep the existing module version numbers in `moduleList` unchanged. If you modify the module versions in `moduleList` during a `redisVersion` upgrade, the upgrade request will fail. The database will automatically use the bundled module versions for the new Redis version, regardless of what versions are specified in `moduleList`. This applies to both REDB and REAADB databases.
 
 - **Custom certificate upload is not supported for internode encryption (RED-173229).** Internode communication between cluster nodes continues to use default self-signed certificates and cannot be configured with customer-provided certificates.
 

content/operate/kubernetes/upgrade/openshift-cli.md

@@ -222,7 +222,7 @@ To upgrade your REDB, specify your new database version in the `spec.redisVersio
 
 For Active-Active databases, the `redis.Version` change only needs to be applied on one participating cluster and will automatically propagate to all other participating clusters. All participating clusters must be running operator version 8.0.2-2 or later.
 
-If your REAADB uses supported modules, keep the existing `moduleList` version numbers unchanged when upgrading `redisVersion`. The database will automatically use the module versions that are bundled with the new Redis version, regardless of what versions are specified in `moduleList`. After the upgrade is complete, you can optionally remove the old version numbers from `moduleList`, but this change has no functional impact.
+If your REAADB uses supported modules, keep the existing `moduleList` version numbers unchanged when upgrading `redisVersion`. The database will automatically use the module versions that are bundled with the new Redis version, regardless of what versions are specified in `moduleList`. After the upgrade is complete, you can optionally change the old version numbers from `moduleList`, but this change has no functional impact.
 
 #### General upgrade notes
 

content/operate/kubernetes/upgrade/upgrade-olm.md

@@ -145,7 +145,7 @@ To upgrade your REDB, specify your new database version in the `spec.redisVersio
 
 For Active-Active databases, the `redis.Version` change only needs to be applied on one participating cluster and will automatically propagate to all other participating clusters. All participating clusters must be running operator version 8.0.2-2 or later.
 
-If your REAADB uses supported modules, keep the existing `moduleList` version numbers unchanged when upgrading `redisVersion`. The database will automatically use the module versions that are bundled with the new Redis version, regardless of what versions are specified in `moduleList`. After the upgrade is complete, you can optionally remove the old version numbers from `moduleList`, but this change has no functional impact.
+If your REAADB uses supported modules, keep the existing `moduleList` version numbers unchanged when upgrading `redisVersion`. The database will automatically use the module versions that are bundled with the new Redis version, regardless of what versions are specified in `moduleList`. After the upgrade is complete, you can optionally change the old version numbers from `moduleList`, but this change has no functional impact.
 
 ### General upgrade notes
 

content/operate/kubernetes/upgrade/upgrade-redis-cluster.md

@@ -222,7 +222,7 @@ To upgrade your REDB, specify your new database version in the `spec.redisVersio
 
 For Active-Active databases, the `redis.Version` change only needs to be applied on one participating cluster and will automatically propagate to all other participating clusters. All participating clusters must be running operator version 8.0.2-2 or later.
 
-If your REAADB uses supported modules, keep the existing `moduleList` version numbers unchanged when upgrading `redisVersion`. The database will automatically use the module versions that are bundled with the new Redis version, regardless of what versions are specified in `moduleList`. After the upgrade is complete, you can optionally remove the old version numbers from `moduleList`, but this change has no functional impact.
+If your REAADB uses supported modules, keep the existing `moduleList` version numbers unchanged when upgrading `redisVersion`. The database will automatically use the module versions that are bundled with the new Redis version, regardless of what versions are specified in `moduleList`. After the upgrade is complete, you can optionally change the old version numbers from `moduleList`, but this change has no functional impact.
 
 #### General upgrade notes