Fix typos and explanations

Author: gnunn1

content/modules/ROOT/pages/03-configuration.adoc

@@ -86,15 +86,15 @@ few additional capabilities specific to OpenShift.
 [#config-health-checks]
 == Argo CD Health Checks
 
-Argo CD has the ability to monitor the health of resources that it has deployed. When an Argo CD detects that a deployed Resource
+Argo CD has the ability to monitor the health of resources that it has deployed. When Argo CD detects that a deployed Resource
 is in a non-Healthy state (Degrade, Progressing, etc) this is because the associated health check is reporting
 this status.
 
 [IMPORTANT]
 Argo CD Health Checks provide a quick and easy way to monitor the status of resources being managed by Argo CD. If you deploy
 some additional alerting in your monitoring for Argo CD Applications you essentially get resource alerting
-for free. OpenShift GitOps includes an alert for the Out-of-Sync status, but you can view an example of additional
-alerting on health status link:https://github.com/gnunn-gitops/acm-hub-bootstrap/blob/main/components/policies/gitops/base/manifests/gitops-alerting/base/prometheus-rules.yaml[here,window="_blank"].
+for free. OpenShift GitOps includes an alert for the Out-of-Sync status, but you can view a blog of how to create additional
+alerting based on health status link:https://developers.redhat.com/blog/2025/07/24/create-additional-alerts-openshift-gitops[here,window="_blank"].
 
 These health statuses are also used to support features like link:https://argo-cd.readthedocs.io/en/stable/user-guide/sync-waves[Sync Waves, window="_blank"]
 which deploy resources in a prescribed order. Argo CD will not deploy subsequent resources until earlier resources are in a Healthy state as determined by
@@ -114,9 +114,9 @@ these statuses of most to least healthy statuses: _Healthy_, _Suspended_, _Progr
 
 Argo CD health checks are sourced from three locations:
 
-1. _Native_. These health checks are for standard Kubernetes resources (Deployment, Job, etc) are written in Go. They can
+1. _Native_. These health checks are for standard Kubernetes resources (Deployment, Job, etc) and are written in Go. They can
 be reviewed in the link:https://github.com/argoproj/gitops-engine/tree/master/pkg/health[gitops-engine, window="_blank"] repository.
-2. _Included_. These health checks are written in LUA and a large number of custom health checks ship with Argo CD, these can be reviewed
+2. _Included_. These health checks are written in LUA with a large number of health checks shipped with Argo CD, these can be reviewed
 in the Argo CD repository in the link:https://github.com/argoproj/argo-cd/tree/master/resource_customizations[resource_customizations, window="_blank" ]
 folder.
 3. _Custom_. These are health checks that you create yourself and configure in Argo CD. This can be done for resources that do not have a
@@ -209,9 +209,10 @@ STATUS: Progressing
 MESSAGE
 ----
 
-Note the command confirms that Argo CD considers the PVC to be `Progressing`, let's change that with the following .
+Note the command confirms that Argo CD considers the PVC to be `Progressing`, let's change that with the following 
+custom health check writtin in LUA to override the default one:
 
-[source,yaml,subs="attributes",role=execute]
+[source,yaml,subs="+macros,attributes+"]
 ----
 hs = {}
 if (obj.status ~= nil and obj.status.phase ~= nil) then
@@ -271,7 +272,7 @@ resource.customizations.health.PersistentVolumeClaim: |
   return hs
 ----
 
-Now test the status that is returned using the Argo CD CLI again but using our new configmap:
+Now test the status that is returned using the Argo CD CLI again but using our new configmap with the updated PVC health check:
 
 [.console-input]
 [source,yaml,subs="attributes",role=execute]
@@ -288,20 +289,22 @@ STATUS: Healthy
 MESSAGE: Pending
 ----
 
-Great, our updated health check is working! Let's go ahead and patch it into ArgoCD Custom Resource on the cluster
-to take advantage of it:
+Great, our updated health check is working! The status is returned as `Healthy` to Argo CD but we set the message field to the 
+Kubernetes status of the PVC to provide additional context. 
+
+Let's go ahead and patch it into our ArgoCD Custom Resource on the cluster to take advantage of it:
 
 [.console-input]
 [source,yaml,subs="attributes",role=execute]
 ----
 oc patch -n user{usernum}-argocd argocd argocd --type=merge --patch-file=/home/lab-user/workshop/content/modules/ROOT/examples/health/health-check-patch.yaml
 ----
 
-Go back Argo CD and press the `Refresh` button
+Go back Argo CD and press the `Refresh` button to cause the heath check to be re-evaluated:
 
 image::argocd-refresh.png[]
 
-In twenty to thirty seconds you should see the Refresh complete and the Application properly sync'ed.
+In twenty to thirty seconds you should see the Refresh complete and the Application become properly synced.
 
 image::argocd-health-test-synced.png[]
 
@@ -346,6 +349,8 @@ include::ROOT:example$enable-applicationset/enable-applicationset-patch.yaml[]
 There are more configuraton options available then just `enabled`, feel free to explore them
 by running `oc explain argocd.spec.applicationSet`.
 
+Apply the patch:
+
 [.console-input]
 [source,yaml,subs="attributes",role=execute]
 ----
@@ -377,26 +382,28 @@ The `applicationset-controller` has now been deployed.
 == Enabling Terminal
 
 The Argo CD user interface, when viewing a pod, can optionally show a link:https://argo-cd.readthedocs.io/en/latest/operator-manual/web_based_terminal/[terminal, window="_blank"]
-tab similar to what you see in the OpenShift console. This can be useful for Organizations which use the Argo CD UI
-as a means for managing kubernetes resources.
+tab similar to what you see in the OpenShift console. This can be useful for organizations which use the Argo CD UI
+as the primary means for managing Kubernetes resources.
 
-By default this is not enabled, in the health application that was deployed previously click on the
-pod. 
+While we previously gave permissions for the terminal in the previous module, by default this is not enabled. To verify this, 
+in the health application that was deployed previously click on the pod. 
 
 image::argocd-select-pod.png[]
 
-Note that the only tabs available are `SUMMARY`, `EVENTS` and `LOGS`.
+Note that the only tabs available are `SUMMARY`, `EVENTS` and `LOGS` with no `TERMINAL` tab appearing.
 
 image::argocd-pod-tabs.png[]
 
-As mentioned previously, not all Argo CD settings are defined in the ArgoCD Custom Resource. For cases
-where a setting is not defined, we can use the `extraConfig` to have the operator add these items 
+As mentioned previously, not all Argo CD settings are defined in the ArgoCD Custom Resource and enabling
+the terminal is one of those cases. 
+
+For cases like this where a setting is not defined, we can use the `extraConfig` to have the operator add these items 
 directly to the `argocd-cm` ConfigMap. Whatever is defined, correctly or incorrectly, will be copied
-to this configmap so some care should be taken when using this feature.
+to this ConfigMap so some care should be taken when using this feature.
 
 [IMPORTANT]
 Before using `extraConfig`, you should always validate the option you want to set is not in fact
-available in the Operator. Also never edit the `argocd-cm` ConfigMap directly, the operator will
+available in the Operator. Also as a reminder never edit the `argocd-cm` ConfigMap directly, the operator will
 revert any manual changes.
 
 Review the patch that we are going to apply:
@@ -414,12 +421,12 @@ Apply the patch:
 oc patch -n {user}-argocd argocd argocd --type=merge --patch-file=/home/lab-user/workshop/content/modules/ROOT/examples/pod-exec/enable-terminal-patch.yaml
 ----
 
-Verify that you can now see the terminal tab for the pod resource:
+Verify that you can now see the terminal tab for the pod resource, note that you will need to close the Pod view and then re-open it:
 
 image::argocd-terminal.png[]
 
 [IMPORTANT]
-As per the Argo CD Documentation, the `argocd-server` ServiceAccount must be granted additional permissions with Kubernetes RBAC
+As per the link:https://argo-cd.readthedocs.io/en/latest/operator-manual/web_based_terminal/[Argo CD Documentation, window="_blank"], the `argocd-server` ServiceAccount must be granted additional permissions with Kubernetes RBAC
 to enable the terminal. These permissions have already been applied by specifying a custom ClusterRole for the GitOps Operator. 
 
 [#config-conclusion]