docs: minor touch-up

_partials/self-hosted/_cloud-provider-config.mdx

@@ -5,9 +5,12 @@ partial_name: cloud-provider-config
 
 
 
-When using public cloud providers, {props.edition} automatically downloads the required infrastructure provider images from our public registries to set up a workload cluster. 
-For example, if you want to deploy an AWS cluster, {props.edition} downloads the required Amazon Machine Image (AMI) that contains the desired Operation System (OS) and Kubernetes binaries specified in the cluster profile. 
-The exception to this is when you are using a custom image, in which case you must provide the image yourself through the Bring Your Own OS (BYOOS) <VersionedLink text="workflow" url="/byoos/image-builder/"  />.
+Different cloud providers use different image formats to create virtual machines. Amazon Web Services (AWS), for example, uses Amazon Machine Images (AMI), while Azure uses Virtual Hard Disks (VHDs). We provide public images for each cloud provider that contains the desired Operation System (OS) and Kubernetes binaries specified in a cluster profile. 
+We make these infrastructure provider images available to you by ensuring the images are available in the required cloud provider regions.
+
+When you deploy a cluster using {props.edition}, it automatically selects the correct infrastructure provider image that contains the desired Operation System (OS) and Kubernetes binaries specified in the cluster profile.
+The exception to this process is when you are using a custom image, in which case you must provide the image yourself through the <VersionedLink text="Bring Your Own OS (BYOOS) " url="/integrations/packs/?pack=generic-byoi"  />. pack.
+
 
 In the event you need to enable new cloud providers, or rotate the credentials used to access our infrastructure provider images, you can do so through the [System API](https://docs.spectrocloud.com/api/v1/system/).
 Use the following steps to modify the cloud provider configuration for your self-hosted {props.edition} instance.