CNV#58159: Direct z-stream updates

Author: ousleyp

modules/virt-about-control-plane-only-updates.adoc

@@ -6,11 +6,12 @@
 [id="virt-about-control-plane-only-updates_{context}"]
 = Control Plane Only updates
 
-Every even-numbered minor version of {product-title}, including 4.10 and 4.12, is an Extended Update Support (EUS) version. However, because Kubernetes design mandates serial minor version updates, you cannot directly update from one EUS version to the next.
+Every even-numbered minor version of {product-title} is an Extended Update Support (EUS) version. However, Kubernetes design mandates serial minor version updates, so you cannot directly update from one EUS version to the next. An EUS-to-EUS update starts with updating {VirtProductName} to the latest z-stream of the next odd-numbered minor version. Next, update {product-title} to the target EUS version. When the {product-title} update succeeds, the corresponding update for {VirtProductName} becomes available. You can now update {VirtProductName} to the target EUS version.
 
-After you update from the source EUS version to the next odd-numbered minor version, you must sequentially update {VirtProductName} to all z-stream releases of that minor version that are on your update path. When you have upgraded to the latest applicable z-stream version, you can then update {product-title} to the target EUS minor version.
-
-When the {product-title} update succeeds, the corresponding update for {VirtProductName} becomes available. You can now update {VirtProductName} to the target EUS version.
+[NOTE]
+====
+You can directly update {VirtProductName} to the latest z-stream release of your current minor version without applying each intermediate z-stream update.
+====
 
 For more information about EUS versions, see the link:https://access.redhat.com/support/policy/updates/openshift[Red Hat OpenShift Container Platform Life Cycle Policy].
 

modules/virt-preventing-workload-updates-during-control-plane-only-update.adoc

@@ -155,8 +155,6 @@ Updating {product-title} to the next version is a prerequisite for updating {Vir
 $ oc get csv -n {CNVNamespace}
 ----
 
-. Update {VirtProductName} to every z-stream version that is available for the non-EUS minor version, monitoring each update by running the command shown in the previous step.
-
 . Confirm that {VirtProductName} successfully updated to the latest z-stream release of the non-EUS version by running the following command:
 +
 [source,terminal,subs="attributes+"]