diff --git a/assets/middleware/rhoar-microservices/greeting-service-mini.png b/assets/middleware/rhoar-microservices/greeting-service-mini.png
index 70639f980..2ef33f850 100644
Binary files a/assets/middleware/rhoar-microservices/greeting-service-mini.png and b/assets/middleware/rhoar-microservices/greeting-service-mini.png differ
diff --git a/middleware/middleware-spring-boot/microservices-1/02-deploy-to-openshift.md b/middleware/middleware-spring-boot/microservices-1/02-deploy-to-openshift.md
index d975a4383..e80010236 100644
--- a/middleware/middleware-spring-boot/microservices-1/02-deploy-to-openshift.md
+++ b/middleware/middleware-spring-boot/microservices-1/02-deploy-to-openshift.md
@@ -32,9 +32,11 @@ Run the following command to deploy the application to OpenShift:
There's a lot that happens here so lets break it down:
-For the deployment to OpenShift we are using the [JKube](https://www.eclipse.org/jkube/) tool through the [`openshift-maven-plugin`](https://www.eclipse.org/jkube/docs/openshift-maven-plugin), which is configured in our ``pom.xml``{{open}} (found in the `` section).
+For the deployment to OpenShift we are using the [JKube](https://www.eclipse.org/jkube/) tool through the [`openshift-maven-plugin`](https://www.eclipse.org/jkube/docs/openshift-maven-plugin), which is configured in our ``pom.xml``{{open}} (found in the `` section). The deployment may take a few minutes to complete.
-Now that our application is deployed, navigate to our route in the OpenShift Web View or click [here](http://spring-boot-configmap-greeting-dev.[[HOST_SUBDOMAIN]]-80-[[KATACODA_HOST]].environments.katacoda.com/). We should see the following screen, meaning everything was successful:
+You can run the command ``oc rollout status -w dc/spring-boot-configmap-greeting``{{execute}} to watch and wait for the deployment to complete.
+
+Once the application deployment completes, navigate to our route in the OpenShift Web View or click [here](http://spring-boot-configmap-greeting-dev.[[HOST_SUBDOMAIN]]-80-[[KATACODA_HOST]].environments.katacoda.com/). We should see the following screen, meaning everything was successful:
diff --git a/middleware/middleware-spring-boot/microservices-1/03-modify-the-configmap.md b/middleware/middleware-spring-boot/microservices-1/03-modify-the-configmap.md
index c218fb181..b16545d0a 100644
--- a/middleware/middleware-spring-boot/microservices-1/03-modify-the-configmap.md
+++ b/middleware/middleware-spring-boot/microservices-1/03-modify-the-configmap.md
@@ -23,7 +23,7 @@ Change the `greeting.message` property to: `greeting.message=Bonjour, you picked
-Hit `Save` and that's all there is to it!
+Hit `Save` (at the bottom of the editor) and that's all there is to it!
**3. Test changes**
@@ -36,4 +36,4 @@ This means that we were able to modify our application behavior through External
## Congratulations
-You have now learned how to handle Externalized Configuration with ConfigMaps through OpenShift. By creating a configmap, we're able to modify application properties on the fly and simply rollout the new changes to our application.
\ No newline at end of file
+You have now learned how to handle Externalized Configuration with ConfigMaps through OpenShift. By creating a `ConfigMap`, we're able to modify application properties on the fly and simply rollout the new changes to our application.
\ No newline at end of file