cleanup lab02.adoc

content/modules/ROOT/pages/index.adoc

@@ -34,15 +34,29 @@ The diagram will be simplifed and explained in more detail in later chapters.
 The lab instructions will help you prepare the `jump` system to download the installation content, configure the `highside` system to host the content, and create the `openshift.disco.lab` cluster (it doesn't exist yet.)
 
 The *salsa* network and its systems are built automically when the workshop environment is created.
-You can log into the *salsa* systems to compare your systems with functioning disconnected systems.
+You can log into the *salsa* systems to compare your systems with functional disconnected systems.
 
 image::disco-4.svg[disco diagram,800]
 
 === Lab Access and Documentation notes
 
-The terminal window to your right is *already* logged into the [.lowside]#`jump`# system.
-The right-hand side of this browser can also show the [.lowside]#`jump`# system's graphical desktop by clicking on the *Desktop* button.
+The terminal window to your right is *already* logged into the `jump` system.
+The right-hand side of this browser can also show the `jump` system's graphical desktop by clicking on the *Desktop* button.
 The lab instructions should be run as the `{bastion_ssh_user_name}` user.
+Commands that should be run on the `jump` system will appear in this color.
+
+[.lowside,source,bash,role=execute,subs="attributes"]
+----
+echo "Run this command on the jump system"
+echo "FYI - the jump system may also be referred to as the _lowside_ system"
+----
+
+Commands that should be run on the `highside` system will appear in this color.
+
+[.highside,source,html,role=execute]
+----
+echo "Run this command on the highside system"
+----
 
 If you prefer to use your own terminal, you can log into the [.lowside]#`jump`# system using SSH like this:
 
@@ -61,4 +75,4 @@ If you prefer to use your own VNC viewer, you can connect to the [.lowside]#`jum
 vncviewer -via {bastion_ssh_command} 127.0.0.1:0
 ----
 
-//TODO - replace {bastion_ssh_command} with the correct variable
+**TODO** - replace {bastion_ssh_command} with the correct variable

content/modules/ROOT/pages/lab02.adoc

@@ -19,30 +19,16 @@ The basic steps are:
 5. Modify some settings after OpenShift has been installed
 ** e.g. where to look for apps/Operators and updates
 
-== Preparing the Low Side
+== Preparing the `jump` system
 
-A disconnected installation begins by downloading the `oc-mirror` tool and installation content to a system we refer to as the `jump` system.
-In this workshop environement the  that has outbound access to the Internet.
-This server resides in a network environment commonly referred to as the *Low Side* due to its low security profile.
-Compliance requirements usually prevent the low side from housing sensitive data or private information.
+The `jump` system lives in the *lowside* network which allows it to access resources on the public internet.
+The network is called *lowside* because it has a low security profile, and shouldn't be used to store sensitive information.
 
-// TODO remove the "glue" when I copied lab04 into lab02
-== GLUE
+image::disco-0.svg[disco diagram,800]
 
-== Preparing the Low Side
+=== Downloading Tooling
 
-In this lab, we will prepare the low side.
-
-== Accessing the Prep System
-
-Now that our prep system is up, let's SSH into it and download the content
-
-* {bastion_ssh_command} 
-* {bastion_ssh_password}
-
-== Downloading Tooling
-
-Let's grab the tools we'll need for the [.highside]#*highside* system# - we will also be using some of them on the [.lowside]#*jump* system#. 
+Let's grab the tools we need for the [.highside]#*highside* system# - we will also be using some of them on the [.lowside]#*jump* system#. 
 Before we begin, `cd` into the `/mnt/low-side-data/` directory:
 [.lowside,source,bash,role=execute,subs="attributes"]
 ----