diff --git a/images/341_OpenShift_CVO_manifests_0526.png b/images/341_OpenShift_CVO_manifests_0526.png
new file mode 100644
index 000000000000..e5fb59af09d5
Binary files /dev/null and b/images/341_OpenShift_CVO_manifests_0526.png differ
diff --git a/images/update-runlevels.png b/images/update-runlevels.png
deleted file mode 100644
index 309e195a9c58..000000000000
Binary files a/images/update-runlevels.png and /dev/null differ
diff --git a/modules/update-manifest-application.adoc b/modules/update-manifest-application.adoc
index 3f0bb8c12a99..68a92d6b7d99 100644
--- a/modules/update-manifest-application.adoc
+++ b/modules/update-manifest-application.adoc
@@ -55,7 +55,7 @@ The CVO waits until all cluster Operators in the Runlevel meet the following con
 Some actions can take significant time to finish. The CVO waits for the actions to complete in order to ensure the subsequent Runlevels can proceed safely.
 Initially reconciling the new release's manifests is expected to take 60 to 120 minutes in total; see *Understanding {product-title} update duration* for more information about factors that influence update duration.
 
-image::update-runlevels.png[A diagram displaying the sequence of Runlevels and the manifests of components within each level]
+image::341_OpenShift_CVO_manifests_0526.png[A diagram displaying the sequence of Runlevels and the manifests of components within each level]
 
 In the previous example diagram, the CVO is waiting until all work is completed at Runlevel 20.
 The CVO has applied all manifests to the Operators in the Runlevel, but the `kube-apiserver-operator ClusterOperator` performs some actions after its new version was deployed. The `kube-apiserver-operator ClusterOperator` declares this progress through the `Progressing=True` condition and by not declaring the new version as reconciled in its `status.versions`.