Merge pull request #37297 from apinnick/bz2011514-disconnected-installation

BZ2011514: Disconnected installation improvement

Author: apinnick

migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc

@@ -8,15 +8,15 @@ toc::[]
 
 You can install the {mtc-full} ({mtc-short}) on {product-title} 3 and 4 in a restricted network environment by performing the following procedures:
 
-* Create a xref:../operators/admin/olm-restricted-networks.adoc#olm-mirror-catalog_olm-restricted-networks[mirrored Operator catalog].
+. Create a xref:../operators/admin/olm-restricted-networks.adoc#olm-mirror-catalog_olm-restricted-networks[mirrored Operator catalog].
 +
 This process creates a `mapping.txt` file, which contains the mapping between the `registry.redhat.io` image and your mirror registry image. The `mapping.txt` file is required for installing the Operator on the source cluster.
-* Install the {mtc-full} Operator on the {product-title} {product-version} target cluster by using Operator Lifecycle Manager.
+. Install the {mtc-full} Operator on the {product-title} {product-version} target cluster by using Operator Lifecycle Manager.
 +
 By default, the {mtc-short} web console and the `Migration Controller` pod run on the target cluster. You can configure the `Migration Controller` custom resource manifest to run the {mtc-short} web console and the `Migration Controller` pod on a link:https://access.redhat.com/articles/5064151[source cluster or on a remote cluster].
 
-* Install the _legacy_ {mtc-full} Operator on the {product-title} 3 source cluster from the command line interface.
-* Configure object storage to use as a replication repository.
+. Install the _legacy_ {mtc-full} Operator on the {product-title} 3 source cluster from the command line interface.
+. Configure object storage to use as a replication repository.
 
 include::modules/migration-compatibility-guidelines.adoc[leveloffset=+1]
 include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]