From 5fc1ae711862f82cd149eff37ea69a8797f1ad2b Mon Sep 17 00:00:00 2001
From: mickogeary <mickogeary@gmail.com>
Date: Tue, 5 Mar 2024 19:03:00 +0000
Subject: [PATCH] more edits based on SME feedback

---
 ...n-openshift-disconnected-environments.adoc | 22 ++++---------------
 1 file changed, 4 insertions(+), 18 deletions(-)

diff --git a/doc-Service-Telemetry-Framework/modules/proc_deploying-stf-on-openshift-disconnected-environments.adoc b/doc-Service-Telemetry-Framework/modules/proc_deploying-stf-on-openshift-disconnected-environments.adoc
index 8c1e947c..5db7bb26 100644
--- a/doc-Service-Telemetry-Framework/modules/proc_deploying-stf-on-openshift-disconnected-environments.adoc
+++ b/doc-Service-Telemetry-Framework/modules/proc_deploying-stf-on-openshift-disconnected-environments.adoc
@@ -19,12 +19,11 @@ You can use the `oc-mirror` plugin to fetch the {ProjectShort} dependencies and
 
 .Procedure
 
-. Create an `ImageSetConfiguration` resource to retrieve the {ProjectShort} dependencies:
+. Create an imagesetconfig.yaml file in your local working directory:
 
 +
 [source,yaml,options="nowrap",role="white-space-pre"]
 ----
-$ oc create -f - <<EOF
 apiVersion: mirror.openshift.io/v1alpha2
 kind: ImageSetConfiguration
 storageConfig:
@@ -49,7 +48,6 @@ mirror:
       - name: cluster-observability-operator
         channels:
           - name: development
-EOF
 ----
 
 
@@ -63,7 +61,7 @@ You can use the `oc-mirror` plugin differently, depending on your environment, s
 * 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.
+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.
@@ -78,22 +76,10 @@ $ 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.
+. 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.] 
-
-
-
-
-
-
-////
-[role="_additional-resources"]
-.Next steps
-
-* Continue to install {ProjectShort} as in a non-restricted network environment.
-////
+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