Instruction fixes

content/modules/ROOT/pages/module-02-mtv.adoc

@@ -160,7 +160,7 @@ image::module-02-mtv/24_VM_Migration_Stages.png[link=self, window=blank, width=1
 +
 [IMPORTANT]
 ====
-Having many participants performing the same task in parallel in a simulated lab environment can cause this task to perform much slower than in a real environment. For this lab instance we have limited the number of in-flight VMs to 2 at a time. Please be patient with this process as it completes. You may continue with other sections in the roadshow as the migrations complete.
+Having many participants performing the same task in parallel in a simulated lab environment can cause this task to perform much slower than in a real environment. Please be patient with this process as it completes. You may continue with other sections in the roadshow as the migrations complete.
 
 Also the Migration Toolkit Documentation suggests at least a 10Gb connection between the data centers - which is not something that is available in this demo.
 ====

content/modules/ROOT/pages/module-04-storage.adoc

@@ -14,9 +14,9 @@ image::module-04-storage/00_disk_concepts.png[link=self, window=blank, width=100
 
 In this lab, we are going to take a closer look at the storage behind the virtual machine we just created *fedora01*.
 
-. Start by clicking on the left menu for *Storage* -> *Persistent Volume Claims*. Make sure you are in the *vmexamples-{user}* namespace, you should see the *fedora01* VM from the previous section listed.
+. Start by clicking on the left menu for *Storage* -> *Persistent Volume Claims*. Make sure you are in the *vmexamples-{user}* namespace, you should see the *fedora01* PVC that was created when you created the *fedora01* VM in the previous section.
 +
-. Click on the *fedora01* VM and you will be presented with a screen that shows additional details about the storage volume backing the VM.
+. Click on the *fedora01* PVC and you will be presented with a screen that shows additional details about the storage volume backing the VM.
 +
 . Notice the following information about the persistent volume claim:
 .. The PVC is currently bound successfuly
@@ -103,7 +103,7 @@ In the previous step, the operating system was shutdown from within the guest. H
 
 . Using the *Actions* dropdown menu or the shortcut button in the top right corner, *Stop* the VM. This process can take a long time since it attempts a graceful shutdown and the machine is in an unstable state. If you click on the *Actions* dropdown menu again you will have the option to *Force stop*. Please make use of this option in order to continue with the lab.
 
-. You can click on the *Overview* tab to confirm that the VM has stopped. You can also see the snapshot we recently took listed in the *Snapshots* tile. (You may need to Force Stop the VM via the dropdown. This is fine as we are about to restore the snapshot.)
+. You can click on the *Overview* tab to confirm that the VM has stopped. You can also see the snapshot we recently took listed in the *Snapshots* tile. (You may need to *Force Stop* the VM via the dropdown. This is fine as we are about to restore the snapshot.)
 +
 image::module-04-storage/11_VM_Stopped_Snapshot.png[link=self, window=blank, width=100%]
 

content/modules/ROOT/pages/module-07-tempinst.adoc

@@ -27,7 +27,7 @@ Now all VMs should be in *Stopped* state.
 
 By default pre-configured templates provided by Red Hat OpenShift Virtualization cannot be customized. However you can clone a template and make adjustments to it for your particular workload in order to make it easier to request specific types of virtual machines for specific workloads. In this section of the lab we are going to do just this, by creating a template that will provide a database server on demand for our end users.
 
-. To begin, navigate to *Virtualization* -> *Templates* and select *openshift* for your project.
+. To begin, navigate to *Virtualization* -> *Templates* and select *openshift* for your project (you may need to open the *Project* drop-down and click the radio button next to *Show default projects*).
 +
 image::module-07-tempinst/01_Template_List.png[link=self, window=blank, width=100%]