Finalize configuration module

Author: gnunn1

content/modules/ROOT/assets/images/argocd-terminal.png

@@ -15,6 +15,8 @@
 ** xref:03-configuration.adoc#config-introduction[Introduction]
 ** xref:03-configuration.adoc#config-health-checks[Health Checks]
 ** xref:03-configuration.adoc#enable-appset[Enable Application Sets]
+** xref:03-configuration.adoc#enable-terminal[Enable Terminal]
+** xref:03-configuration.adoc#config-conclusion[Conclusion]
 
 * xref:04-applicationsets.adoc[4. ApplicatonSets]
 

content/modules/ROOT/nav.adoc

@@ -416,9 +416,17 @@ oc patch -n {user}-argocd argocd argocd --type=merge --patch-file=/home/lab-user
 
 Verify that you can now see the terminal tab for the pod resource:
 
-
+image::argocd-terminal.png[]
 
 [IMPORTANT]
 As per the Argo CD Documentation, 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]
+== Conclusion
+
+In this module we have learned how to configure Argo CD, the importance of health checks and handling
+configuration options not available in the Operator.
+
+Clean-up your work by deleting the `health-test` Application using the default `Foreground` deletion option.
+