fixed linking issues due to updated filenames

Author: abhatt-rh

modules/med-about-customizing-pattern.adoc

@@ -2,7 +2,7 @@
 :imagesdir: ../../images
 
 [id="about-customizing-pattern-med"]
-= About customizing the pattern {med-pattern}
+= About customizing the {med-pattern}
 
 One of the major goals of the {solution-name-upstream} development process is to create modular and customizable demos. The {med-pattern} is just an example of how AI/ML workloads built for object detection and classification can be run on OpenShift clusters. Consider your workloads for a moment - how would your workload best consume the pattern framework? Do your consumers require on-demand or near real-time responses when using your application? Is your application processing images or data that is protected by either Government Privacy Laws or HIPAA?
 The {med-pattern} can answer the call to either of these requirements by using  {serverless-short} and {ocp-data-short}.

modules/med-about-medical-diagnosis.adoc

@@ -43,4 +43,4 @@ The {med-pattern} uses the following products and technologies:
 * {rh-serverless-first} for event-driven applications
 * {rh-ocp-data-first} for cloud native storage capabilities
 * {grafana-op} to manage and share Grafana dashboards, data sources, and so on
-* S3 storage
+* Storage, such as AWS S3 buckets

modules/med-ocp-cluster-sizing.adoc

@@ -2,7 +2,7 @@
 :imagesdir: ../../images
 
 [id="med-openshift-cluster-size"]
-== About {med-pattern} OpenShift cluster size
+== About OpenShift cluster size for the {med-pattern}
 
 The {med-pattern} has been tested with a defined set of configurations that represent the most common combinations that {ocp} customers are using for the x86_64 architecture.
 

modules/med-troubleshooting-deployment.adoc

@@ -1,8 +1,8 @@
 :_content-type: REFERENCE
-:imagesdir: ../../images
+:imagesdir: ../../../images
 
 [id="troubleshooting-the-pattern-deployment-troubleshooting"]
-=== Troubleshooting the Pattern Deployment
+=== Troubleshooting the pattern deployment
 
 Occasionally the pattern will encounter issues during the deployment. This can happen for any number of reasons, but most often it is because of either a change within the operator itself or something has changed in the {olm-first} which determines which operators are available in the operator catalog. Generally, when an issue occurs with the {olm-short}, the operator is unavailable for installation. To ensure that the operator is in the catalog, run the following command: