updates

Signed-off-by: Fortune-Ndlovu <[email protected]>

Author: Fortune-Ndlovu

modules/installation/proc-install-rhdh-airgapped-environment-ocp-helm.adoc

@@ -17,7 +17,7 @@ To install {product-short} in an air-gapped environment, you must have access to
 * You have access to the {ocp-brand-name} image registry of your cluster. For more information about exposing the image registry, see the {ocp-brand-name} documentation about https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/registry/index#securing-exposing-registry[Exposing the registry].
 * You have installed the {openshift-cli} on your workstation.
 * You have installed the `podman` command line tools on your workstation.
-* You have installed the `oc-mirror`, for more information see https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin].
+* You have installed the oc-mirror {openshift-cli} plugin, for more information see https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin].
 * You have an account in https://developers.redhat.com/[{rhdeveloper-name}] portal.
 
 .Procedure
@@ -60,7 +60,7 @@ podman login registry.redhat.io
 +
 For more information about registry authentication, see https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
 
-. Create an `ImageSetConfiguration` ffile to specify the resources that you want to mirror. For example:
+. Create an `ImageSetConfiguration` file to specify the resources that you want to mirror. For example:
 +
 
 +
@@ -78,41 +78,34 @@ mirror:
         url: https://charts.openshift.io
         charts:
           - name: redhat-developer-hub
-            version: "1.4.1"
+            version: "{product-version}"
 ----
-. Initiate the mirroring process using the `ImageSetConfiguration` file. The `oc-mirror` command mirrors the specified resources as defined in the configuration file and generates a `.tar` archive containing all the mirrored resources.
+. Mirror the resources specified in the`ImageSetConfiguration` file by running the following command:
 +
 [source,terminal]
 ----
 oc-mirror --config=mirror-config.yaml file://mirror-archive
 ----
-. Transfer the generated archive (e.g.,
-`mirror++_++seq1++_++000000.tar`) to the air-gapped environment using
-`scp` or another file transfer tool.
+. Transfer the generated `.tar` archive file (for example, `mirror++_++seq1++_++000000.tar`) to the air-gapped environment using `scp` or another file transfer tool. For example:
 +
 [source,terminal]
 ----
 scp ./mirror-archive/mirror_seq1_000000.tar /tmp
 ----
-. Extract the contents of the archive into a directory before proceeding
-with deployment.
+. Extract the contents of the archive into a directory by running the following command:
 +
 [source,terminal]
 ----
 tar -xvf /mirror-archive/mirror_seq1_000000.tar -C /tmp
 ----
-. Deploy the Helm chart in the air-gapped environment using the `helm`
-command.
+. Deploy the Helm chart in the air-gapped environment by running the following command:
 +
 [source,terminal]
 ----
 helm install rhdh ./mirror-archive/oc-mirror-workspace/src/charts/redhat-developer-hub-1.4.1.tgz --namespace rhdh --create-namespace
 ----
 
 .Verification
-1. Verify that all resources are successfully deployed and running:
-   - Check the status of your deployments and pods in the cluster.
-2. Validate the route:
-   - Ensure the route matches the expected URL based on the cluster's router base.
-   - If necessary, update the route to align with your expected configuration.
-
+. To verify that all resources are successfully deployed and running, check the status of your deployments and pods in the cluster.
+. To validate the route, ensure that the route matches the expected URL based on the router base of the cluster.
+.. If necessary, update the route to align with your expected configuration.