Smaller cleanups

content/patterns/industrial-edge/application.md

@@ -62,8 +62,8 @@ every 2-3 minutes), you will see an anomaly and alert on it.
 
 [![app-line-dashboard-before](/images/industrial-edge/app-line-dashboard-before.png)](/images/industrial-edge/app-line-dashboard-before.png)
 
-Now let's turn on the temperature sensor. Go to the gitea link on the nine box login using the 
-`gitea_admin` user and the autogenerated password that can be found in the secret called 
+Now let's turn on the temperature sensor. Go to the gitea link on the nine box login using the
+`gitea_admin` user and the autogenerated password that can be found in the secret called
 `gitea-admin-secret` in the `vp-gitea` namespace:
 
 [![gitea-signin](/images/industrial-edge/gitea-signin.png)](/images/industrial-edge/gitea-signin.png)
@@ -101,9 +101,9 @@ Sometimes a page/tab refreshed is needed for the change to be picked up.
 The `line-dashboard` application has temperature sensors. In this demonstration
 we are going to make a simple change to that application, rebuild and redeploy
 it. In the `manuela-dev` repository there is a file
-`components/iot-frontend/src/app/app.component.html`. Let's change the 
-`<ion-title>IoT Dashboard</ion-title>` to something else, say, 
-`<ion-title>IoT Dashboard - DEVOPS was here!</ion-title>`. We do this in the 
+`components/iot-frontend/src/app/app.component.html`. Let's change the
+`<ion-title>IoT Dashboard</ion-title>` to something else, say,
+`<ion-title>IoT Dashboard - DEVOPS was here!</ion-title>`. We do this in the
 gitea web interface directly clicking on the editing icon for the file:
 
 [![gitea-iot-edit](/images/industrial-edge/gitea-iot-edit.png)](/images/industrial-edge/gitea-iot-edit.png)
@@ -133,7 +133,7 @@ The pipeline will also have created a PR in gitea, like the following one:
 [![gitea-pipeline-pr](/images/industrial-edge/gitea-pipeline-pr.png)](/images/industrial-edge/gitea-pipeline-pr.png)
 
 Now an operator can verify that the change is correct on the datacenter in the
-`manuela-tst-all` line dashboard and if deemed correct, he can merge the PR in 
+`manuela-tst-all` line dashboard and if deemed correct, he can merge the PR in
 gitea which will roll out the change to the production factory!
 
 ## Application AI model changes with DevOps
@@ -148,7 +148,7 @@ be taken to the project which will contain a couple of workbenches and a model:
 
 [![rhoai-ml-development](/images/industrial-edge/rhoai-ml-development.png)](/images/industrial-edge/rhoai-ml-development.png)
 
-Clicking on the `JupyterLab` workbench you'll be taken to the notebook where data analysis for this 
+Clicking on the `JupyterLab` workbench you'll be taken to the notebook where data analysis for this
 pattern is being done. The `manuela-dev` code will be preloaded in the notebook and you can click
 on the left file browser on `manuela-dev/ml-models/anomaly-detection/1-preprocessing.ipynb`:
 

content/patterns/industrial-edge/demo-script.md

@@ -2,8 +2,9 @@
 
 ## Objectives
 
-There's no experience like hands-on experience and being able to see industrial edge scenarios. This is a demo for the Industrial Edge Validated Pattern using the latest product and technology improvements.
-
+There's no experience like hands-on experience and being able to see industrial
+edge scenarios. This is a demo for the Industrial Edge Validated Pattern using
+the latest product and technology improvements.
 
 * Show Red Hat Operators being deployed
 * Show available Red Hat Pipelines for the Industrial Edge pattern
@@ -13,20 +14,19 @@ There's no experience like hands-on experience and being able to see industrial
 * Show the datacenter-gitops-server view
 * Show the factory-gitops-server view
 
-
 #### For Information on the Red Hat Validated Patterns, visit our [website](https://validatedpatterns.io)
 
 ## See the pattern in action
 
 Watch the following video for a demonstration of [OpenShift Pipelines in the Industrial Edge Pattern](https://www.youtube.com/watch?v=BMUiaCm6pZ8)
 
-In this article, we give an overview of the demo and step by step instructions on how to get started. 
+In this article, we give an overview of the demo and step by step instructions on how to get started.
 
 ## Getting Started
 
 **_NOTE:_** This demo takes a "bring your own cluster" approach, which means this pattern/demo will not deploy any OpenShift clusters.
 
-This demo script begins after the completion of you running `./pattern.sh make install` from our [Getting Started Guide](../getting-started) 
+This demo script begins after the completion of you running `./pattern.sh make install` from our [Getting Started Guide](../getting-started)
 
 ### Demo: Quick Health Check
 **_NOTE:_** This is a complex setup, and sometimes things can go wrong. Do a quick check of the essentials:
@@ -68,7 +68,8 @@ If you run into any problems, checkout the potential/Known issues list: http://v
 
 ## Summary
 
-In this demo we: , we show you how to get started with the Industrial Edge Validated Pattern. In 
+In this demo we show you how to get started with the Industrial Edge Validated Pattern.
+More specifically, we:
 
 * Show you how to get started with the Industrial Edge Pattern
 * Make configuration changes with GitOps