diff --git a/docs_user/modules/con_post-adoption-tasks.adoc b/docs_user/modules/con_post-adoption-tasks.adoc
index 3a3b674bc..f0a5563d4 100644
--- a/docs_user/modules/con_post-adoption-tasks.adoc
+++ b/docs_user/modules/con_post-adoption-tasks.adoc
@@ -9,7 +9,7 @@ Perform the following post-adoption tasks to ensure that your {rhos_long} enviro
 * After adoption, {rhos_acro} data plane nodes run Red Hat Enterprise Linux (RHEL) 9.2. The data plane nodes can remain on RHEL 9.2; however, you must perform a system update to use the full feature set from the release, and to align your environment with the maximum support lifecycle of {rhos_acro}.
 ** You can perform a system update any time after you complete the adoption procedure.
 ** You can defer the system update to a separate maintenance window.
-** You can perform the system update on one nodeset at a time. For example, you can update one nodeset from RHEL 9.2 to RHEL 9.4 in one maintenance window, and then update a different nodeset in another maintenance window later.
+** You can perform the system update on one node set at a time. For example, you can update one node set from RHEL 9.2 to RHEL 9.4 or 9.6 in one maintenance window, and then update a different node set in another maintenance window later.
 * If you enabled the high availability for Compute instances (Instance HA) service, remove the Pacemaker components from your Compute nodes.
 * Enable TLS Everywhere (TLS-e).
 * Verify that you migrated all services from the Controller nodes, and then power off the nodes. If any services are still running in the Controller nodes, such as Open Virtual Networking (ML2/OVN), {object_storage_first_ref}, or {Ceph}, do not power off the nodes.