Updates a few notes in image registry docs for clarity and new features

Author: Steven Smith

registry/configuring-registry-operator.adoc

@@ -19,9 +19,9 @@ The Image Registry Operator installs a single instance of the {product-registry}
 ifndef::openshift-dedicated,openshift-rosa[]
 [NOTE]
 ====
-Storage is only automatically configured when you install an installer-provisioned infrastructure cluster on AWS, GCP, Azure, or OpenStack.
+Storage is only automatically configured when you install an installer-provisioned infrastructure cluster on AWS, Azure, GCP, IBM, or OpenStack.
 
-When you install or upgrade an installer-provisioned infrastructure cluster on AWS or Azure, the Image Registry Operator sets the `spec.storage.managementState` parameter to `Managed`. If the `spec.storage.managementState` parameter is set to `Unmanaged`, the Image Registry Operator takes no action related to storage.
+When you install or upgrade an installer-provisioned infrastructure cluster on AWS, Azure, GCP, IBM, or OpenStack, the Image Registry Operator sets the `spec.storage.managementState` parameter to `Managed`. If the `spec.storage.managementState` parameter is set to `Unmanaged`, the Image Registry Operator takes no action related to storage.
 ====
 endif::openshift-dedicated,openshift-rosa[]
 
@@ -44,7 +44,7 @@ However, the `managementState` of the Image Registry Operator alters the behavio
 
 ifndef::openshift-dedicated,openshift-rosa[]
 [id="image-registry-on-bare-metal-vsphere"]
-== Image Registry on bare metal and vSphere
+== Image Registry on bare metal, Nutanix, and vSphere
 
 include::modules/registry-removed.adoc[leveloffset=+2]
 endif::openshift-dedicated,openshift-rosa[]