trying to fix the htmltest errors

abhatt-rh · abhatt-rh · commit b1913b37dc90 · 2023-11-17T19:46:47.000Z
diff --git a/content/blog/2021-12-31-medical-diagnosis.md b/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/med-getting-started/) page.
+To deploy this pattern, follow the instructions outlined on the [Getting started](/patterns/medical-diagnosis/med-getting-started/) page.
 
 ### What's happening?
 
diff --git a/content/patterns/ansible-edge-gitops/installation-details.md b/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/validatedpatterns/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/validatedpatterns/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.
 
diff --git a/content/patterns/medical-diagnosis/_index.adoc b/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
 
-* link:med-getting-started[Deploy the pattern]
+* link:med-getting-started/#med-deploy-pattern[Deploying the Medical Diagnosis pattern]
diff --git a/content/patterns/medical-diagnosis/med-troubleshooting.adoc b/content/patterns/medical-diagnosis/med-troubleshooting.adoc
@@ -7,7 +7,6 @@ aliases: /medical-diagnosis/med-troubleshooting/
 :toc:
 :imagesdir: /images
 :_content-type: REFERENCE
-
 include::modules/comm-attributes.adoc[]
 
 include::modules/med-about-makefile.adoc[leveloffset=+1]
diff --git a/modules/med-deploying-med-diag-pattern.adoc b/modules/med-deploying-med-diag-pattern.adoc
@@ -1,7 +1,7 @@
 :_content-type: PROCEDURE
 :imagesdir: ../../../images
 
-[id="med-deploy-pattern_{context}"]
+[id="med-deploy-pattern"]
 = Deploying the {med-pattern}
 
 . To apply the changes to your cluster, run the following command:
diff --git a/modules/med-preparing-for-deployment.adoc b/modules/med-preparing-for-deployment.adoc
@@ -106,7 +106,7 @@ Replace instances of PROVIDE_ with your specific configuration
 ----
 +
 Save the values-global.yaml file and commit it to your branch:
-
++
 [source,terminal]
 ----
 $ git add values-global.yaml

Original file line number	Diff line number	Diff line change
`@@ -106,7 +106,7 @@ Replace instances of PROVIDE_ with your specific configuration`
`106`	`106`	`----`
`107`	`107`	`+`
`108`	`108`	`Save the values-global.yaml file and commit it to your branch:`
`109`		`-`
	`109`	`++`
`110`	`110`	`[source,terminal]`
`111`	`111`	`----`
`112`	`112`	`$ git add values-global.yaml`