Merge pull request #66712 from stevsmit/19915-follow-up

Updates OMR language for bootstrapping

Author: stevsmit

modules/mirror-registry-introduction.adoc

@@ -24,8 +24,6 @@ The following limitations apply to the _mirror registry for Red Hat OpenShift_:
 
 * Support for Red Hat product images that are pushed to the _mirror registry for Red Hat OpenShift_ for bootstrapping purposes are covered by valid subscriptions for each respective product. A list of exceptions to further enable the bootstrap experience can be found on the link:https://www.redhat.com/en/resources/self-managed-openshift-sizing-subscription-guide[Self-managed Red Hat OpenShift sizing and subscription guide]. 
 
-* Images that are not intended for bootstrapping are not supported by the _mirror registry for Red Hat OpenShift_. 
-
 * Content built by customers should not be hosted by the _mirror registry for Red Hat OpenShift_. 
 
 * Using the _mirror registry for Red Hat OpenShift_ with more than one cluster is discouraged because multiple clusters can create a single point of failure when updating your cluster fleet. It is advised to leverage the _mirror registry for Red Hat OpenShift_ to install a cluster that can host a production-grade, highly-available registry such as {quay}, which can serve {product-title} content to other clusters.