diff --git a/asciidoc/product/atip-management-cluster.adoc b/asciidoc/product/atip-management-cluster.adoc
index 3f5397c8..d81ee4d7 100644
--- a/asciidoc/product/atip-management-cluster.adoc
+++ b/asciidoc/product/atip-management-cluster.adoc
@@ -76,8 +76,9 @@ For more information about Edge Image Builder, see <<components-eib,Edge Image B
 [#mgmt-cluster-image-preparation-connected]
 === Image preparation for connected environments
 
-Using Edge Image Builder to create the image for the management cluster, a lot of configurations can be customized, but in this document, we cover the minimal configurations necessary to set up the management cluster.
-Edge Image Builder is typically run from inside a container so, if you do not already have a way to run containers, we need to start by installing a container runtime such as https://podman.io[Podman] or https://rancherdesktop.io[Rancher Desktop]. For this guide, we assume you already have a container runtime available.
+Edge Image Builder is used to create the image for the management cluster, in this document we cover the minimal configuration necessary to set up the management cluster.
+
+Edge Image Builder runs inside a container, so a container runtime is required such as https://podman.io[Podman] or https://rancherdesktop.io[Rancher Desktop]. For this guide, we assume podman is available.
 
 Also, as a prerequisite to deploy a highly available management cluster, you need to reserve three IPs in your network:
 - `apiVIP` for the API VIP Address (used to access the Kubernetes API server).