reorg the getting started sections for better flow of info

Author: abhatt-rh

content/blog/2021-12-31-medical-diagnosis.md

@@ -30,7 +30,7 @@ For a recorded demo deploying the pattern and seeing the dashboards available to
 
 ---
 
-To deploy this pattern, follow the instructions outlined on the [getting-started](https://validatedpatterns.io/medical-diagnosis/getting-started/) page.
+To deploy this pattern, follow the instructions outlined on the [getting-started](https://validatedpatterns.io/medical-diagnosis/med-getting-started/) page.
 
 ### What's happening?
 

content/learn/importing-a-cluster.adoc

@@ -110,15 +110,15 @@ If you use the command line tools above you need to explicitly indicate that the
 
 We do this by adding the label referenced in the managedSite's `clusterSelector`.
 
-1. Find the new cluster.
+. Find the new cluster.
 
 +
 [source,terminal]
 ----
 oc get managedclusters.cluster.open-cluster-management.io
 ----
 
-1. Apply the label.
+. Apply the label.
 
 +
 [source,terminal]

content/learn/vault.adoc

@@ -12,12 +12,12 @@ aliases: /secrets/vault/
 = Deploying HashiCorp Vault in a validated pattern
 
 [id="prerequisites"]
-= Prerequisites
+== Prerequisites
 
 You have deployed/installed a validated pattern using the instructions provided for that pattern. This should include setting having logged into the cluster using `oc login` or setting you `KUBECONFIG` environment variable and running a `make install`.
 
 [id="setting-up-hashicorp-vault"]
-= Setting up HashiCorp Vault
+== Setting up HashiCorp Vault
 
 Any validated pattern that uses HashiCorp Vault already has deployed Vault as part of the `make install`.  To verify that Vault is installed you can first see that the `vault` project exists and then select the Workloads/Pods:
 

content/patterns/ansible-edge-gitops/installation-details.md

@@ -93,7 +93,7 @@ OpenShift GitOps is central to this pattern as it is responsible for installing
 
 # ODF (OpenShift Data Foundations)
 
-ODF is the storage framework that is needed to provide resilient storage for OpenShift Virtualization.  It is managed via the helm chart [here](https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/tree/main/charts/hub/openshift-data-foundations). This is basically the same chart that our Medical Diagnosis pattern uses (see [here](/patterns/medical-diagnosis/getting-started/) for details on the Medical Edge pattern's use of storage).
+ODF is the storage framework that is needed to provide resilient storage for OpenShift Virtualization.  It is managed via the helm chart [here](https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/tree/main/charts/hub/openshift-data-foundations). This is basically the same chart that our Medical Diagnosis pattern uses (see [here](/patterns/medical-diagnosis/med-getting-started/) for details on the Medical Edge pattern's use of storage).
 
 Please note that this chart will create a Noobaa S3 bucket named nb.epoch_timestamp.cluster-domain which will not be destroyed when the cluster is destroyed.
 

content/patterns/medical-diagnosis/_index.adoc

@@ -32,4 +32,4 @@ include::modules/med-architecture-schema.adoc[leveloffset=+1]
 [id="next-steps_med-diag-index"]
 == Next steps
 
-* Getting started link:getting-started[Deploy the Pattern]
+* link:med-getting-started[Deploy the pattern]

content/patterns/medical-diagnosis/med-cluster-sizing.adoc

@@ -1,7 +1,7 @@
 ---
-title: Cluster Sizing
+title: Cluster sizing
 weight: 20
-aliases: /medical-diagnosis/cluster-sizing/
+aliases: /medical-diagnosis/med-cluster-sizing/
 ---
 
 :toc: