diff --git a/content/patterns/medical-diagnosis/cluster-sizing.adoc b/content/patterns/medical-diagnosis/cluster-sizing.adoc
index e9813afb9..2cbc124f4 100644
--- a/content/patterns/medical-diagnosis/cluster-sizing.adoc
+++ b/content/patterns/medical-diagnosis/cluster-sizing.adoc
@@ -9,12 +9,15 @@ aliases: /medical-diagnosis/cluster-sizing/
 :_content-type: ASSEMBLY
 include::modules/comm-attributes.adoc[]
 
+:aws_node: xlarge
+
+
 //Module to be included
 //:_content-type: CONCEPT
 //:imagesdir: ../../images
 [id="about-openshift-cluster-sizing-med"]
 == About OpenShift cluster sizing for the {med-pattern}
-
+{aws_node}
 To understand cluster sizing requirements for the {med-pattern}, consider the following components that the {med-pattern} deploys on the datacenter or the hub OpenShift cluster:
 
 |===
diff --git a/content/patterns/medical-diagnosis/getting-started.adoc b/content/patterns/medical-diagnosis/getting-started.adoc
index ddc8f19e4..5914fee27 100644
--- a/content/patterns/medical-diagnosis/getting-started.adoc
+++ b/content/patterns/medical-diagnosis/getting-started.adoc
@@ -340,7 +340,7 @@ You can go to the command-line (make sure you have KUBECONFIG set, or are logged
 +
 [source,terminal]
 ----
-$ oc scale deploymentconfig/image-generator --replicas=1 -n xraylab-1
+$ oc scale deployment/image-generator --replicas=1 -n xraylab-1
 ----
 +
 Or you can go to the OpenShift UI and change the view from Administrator to Developer and select Topology. From there select the `xraylab-1` project.
@@ -357,7 +357,7 @@ image::medical-edge/dev-topology-pod-count.png[link="/images/medical-edge/dev-to
 +
 Alternatively, you can have the same outcome on the Administrator console.
 +
-Go to the OpenShift UI under Workloads, select Deploymentconfigs for Project `xraylab-1`.
+Go to the OpenShift UI under Workloads, select Deployments for Project `xraylab-1`.
 Click `image-generator` and increase the pod count to 1.
 +
 image::medical-edge/start-image-flow.png[link="/images/medical-edge/start-image-flow.png"]
@@ -375,14 +375,14 @@ You can change some of the parameters and watch how the changes effect the dashb
 +
 [source,terminal]
 ----
-$ oc scale deploymentconfig/image-generator --replicas=2
+$ oc scale deployment/image-generator --replicas=2
 ----
 +
 Check the dashboard.
 +
 [source,terminal]
 ----
-$ oc scale deploymentconfig/image-generator --replicas=0
+$ oc scale deployment/image-generator --replicas=0
 ----
 +
 Watch the dashboard stop processing images.
diff --git a/content/patterns/medical-diagnosis/troubleshooting.adoc b/content/patterns/medical-diagnosis/troubleshooting.adoc
index a7b59e0c4..f36b9b126 100644
--- a/content/patterns/medical-diagnosis/troubleshooting.adoc
+++ b/content/patterns/medical-diagnosis/troubleshooting.adoc
@@ -59,16 +59,16 @@ Use the grafana dashboard to assist with debugging and identifying the issue
 '''
 Problem:: No information is being processed in the dashboard
 
-Solution:: Most often this is due to the image-generator deploymentConfig needing to be scaled up. The image-generator by design is *scaled to 0*;
+Solution:: Most often this is due to the image-generator deployment needing to be scaled up. The image-generator by design is *scaled to 0*;
 +
 [source,terminal]
 ----
-$ oc scale -n xraylab-1 dc/image-generator --replicas=1
+$ oc scale -n xraylab-1 deploy/image-generator --replicas=1
 ----
 +
 Alternatively, complete the following steps:
 
-. Navigate to the {rh-ocp} web console, and select *Workloads → DeploymentConfigs*
+. Navigate to the {rh-ocp} web console, and select *Workloads → Deployments*
 . Select `image-generator` and scale the pod to 1 or more.
 //AI: Needs review