Minor syntax clean up

doc-Service-Telemetry-Framework/modules/proc_deploying-stf-on-openshift-disconnected-environments.adoc

@@ -19,9 +19,9 @@ You can use the `oc-mirror` plugin to fetch the {ProjectShort} dependencies and
 
 .Procedure
 
-. Create an imagesetconfig.yaml file in your local working directory:
-
+. Create an `imagesetconfig.yaml` file in your local working directory:
 +
+.imagesetconfig.yaml
 [source,yaml,options="nowrap",role="white-space-pre"]
 ----
 apiVersion: mirror.openshift.io/v1alpha2
@@ -52,44 +52,35 @@ mirror:
 
 
 . (Optional) If your mirror registry is not reachable, you can save the manifests and images that you fetched with `oc-mirror` and physically transfer them to the mirror registry and {OpenShift} cluster. Otherwise you can run `oc-mirror` and point to the mirror registry.  
-
 +
 You can use the `oc-mirror` plugin differently, depending on your environment, such as:
-
++
 * mirroring between mirrors.
 * mirror from mirror to disk.
 * mirror from disk to mirror.
-
 +
 For more information about different `oc-mirror` scenarios, see link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{NextSupportedOpenShiftVersion}/html/installing/disconnected-installation-mirroring#mirroring-image-set-full[Mirroring an image set in a fully disconnected environment] in the {OpenShift} _Installing_ guide.
 
-
 . Push the {ProjectShort} operators and their dependencies from the mirror registry and generate the manifest for the {OpenShift} cluster.
-
 +
 [source,bash,options="nowrap",role="white-space-pre"]
 ----
 $ oc-mirror --config imagesetconfig.yaml <mirror_registry_location>
 ----
-
 +
 * Replace <mirror_registry_location> with the filepath to the mirror registry that you want to use.
 
-+
 . Locate the generated manifests and apply them to the target {OpenShift} cluster. For more information, see link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{NextSupportedOpenShiftVersion}/html/installing/disconnected-installation-mirroring#oc-mirror-updating-cluster-manifests_installing-mirroring-disconnected[Configuring your cluster to use the resources generated by oc-mirror] in the {OpenShift} _Installing_ guide.
-
 +
 NOTE: The manifests that you generate with `oc-mirror` produce catalogs with the full index name, such as `redhat-operator-index` instead of `redhat-operators` for `CatalogSource`. Ensure that you use the correct index name for the {ProjectShort}  subscriptions. For more information, see xref:deploying-stf-to-the-openshift-environment_assembly-installing-the-core-components-of-stf[]. For more information about customizing Operators with oc mirror, see the Red Hat Knowledgebase solution link:https://access.redhat.com/solutions/7016714[How to customize the catalog name and tags of Operators mirrored to the mirror registry using the oc mirror plugin.] 
 
 .Verification
 
 * Check that the catalog sources are applied. You can return the entries for new catalogs that reference the {ProjectShort} operators and their dependencies:
-
 +
 [source,bash,options="nowrap",role="white-space-pre"]
 ----
 $ oc get catalogsources
 ----
 
 * You have deployed {ProjectShort} in a disconnected {OpenShift} cluster and therefore cannot access external networks.
-