Merge pull request #13 from rguske/some-nit-picks

Correct some nit-picks in modules 07 and 08

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

@@ -25,7 +25,7 @@ Now all VMs should be in *Stopped* state.
 [[clone_customize_template]]
 == Clone and Customize a Template
 
-By default pre-configured the 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 preconfigured database server on demand for our end users.
+By default the 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 preconfigured database server on demand for our end users.
 
 . 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*).
 +
@@ -69,10 +69,10 @@ userData: |-
   password: ${CLOUD_USER_PASSWORD}
   chpasswd: { expire: False }
   packages:
-  - mariadb-server
+    - mariadb-server
   runcmd:
-  - systemctl enable mariadb
-  - systemctl start mariadb
+    - systemctl enable mariadb
+    - systemctl start mariadb
 ----
 +
 image::module-07-tempinst/10_Cloud_Init_Script.png[link=self, window=blank, width=100%]
@@ -324,7 +324,7 @@ image::module-07-tempinst/25_CD_Import.png[link=self, window=blank, width=100%]
 +
 image::module-07-tempinst/26_Windows_2k19_Console.png[link=self, window=blank, width=100%]
 
-. Once the VM installation process is complete (provisioning will take 3-5 minutes, starting and configuring will take about 10 minutes), go ahead and power it off with the stop button. 
+. Once the VM installation process is complete (provisioning will take 3-5 minutes, starting and configuring will take about 10 minutes), go ahead and power it off with the stop button.
 +
 image::module-07-tempinst/27_Stop_Button.png[link=self, window=blank, width=100%]
 
@@ -334,7 +334,7 @@ image::module-07-tempinst/27_Stop_Button.png[link=self, window=blank, width=100%
 +
 image::module-07-tempinst/28_Storage_PVC.png[link=self, window=blank, width=100%]
 
-. Find the *windows* PVC that is listed and using the three-dot menu on the right select *Clone PVC*. On the menu that pops up, name the new PVC *windows-2k19-sysprep-template*, and set the *Access mode* to *Shared access (RWX)* then click the *Clone* button. Select the *StorageClass* named *ocs-external-storagecluster-ceph-rbd-immediate*
+. Find the *windows* PVC that is listed and using the three-dot menu on the right select *Clone PVC*. On the menu that pops up, name the new PVC *windows-2k19-sysprep-template*, set the *Access mode* to *Shared access (RWX)* and change the *StorageClass* to *ocs-external-storagecluster-ceph-rbd-immediate*. Ultimately, click the *Clone* button.
 +
 image::module-07-tempinst/29_Clone_Menu.png[link=self, window=blank, width=100%]
 
@@ -346,7 +346,7 @@ image::module-07-tempinst/30_Windows_Template.png[link=self, window=blank, width
 
 . Configure BIOS and press *Create VirtualMachine*
 +
-image::module-07-tempinst/30_Windows_Template_BIOS.png
+image::module-07-tempinst/30_Windows_Template_BIOS.png[link=self, window=blank, width=100%]
 
 [[instance_types]]
 == Introduction to Instance Types
@@ -357,7 +357,7 @@ In order to simplify the deployment process for virtual machines, starting with
 +
 image::module-07-tempinst/31_Left_Menu_Catalog.png[link=self, window=blank, width=100%]
 
-. The first step to using an instance type is to select a volume to boot from. Similar to the templates that provide boot sources, those boot sources are available to use for guests provisioned with an InstanceType. You can see the included volumes by selecting the *openshift-virtualization-os-images* project, or you can upload your own with the *Add volume* button.
+. The first step in using an instance type is to select a volume to boot from. Similar to the templates that provide boot sources, these boot sources are available to use for guests provisioned with an InstanceType. You can see the included volumes by selecting the *openshift-virtualization-os-images* project, or you can upload your own with the *Add volume* button.
 +
 NOTE: The *Add Volume* option will be greyed out if you aren't in a project that you have read/write access to.
 
@@ -376,14 +376,14 @@ image::module-07-tempinst/34_Select_InstanceType.png[link=self, window=blank, wi
 ** n1: Designed for network intensive workloads like VNF
 ** cx1: Intended for compute intensive workloads
 ** u1: The most general and "universal" workloads
-** gn1: Dedicated for VMs making use of the nVidia GPU operator.
+** gn1: Dedicated for VMs making use of the Nvidia GPU operator.
 ** m1: Designed for memory intensive workloads.
 
 . Click on the *U series* tile to see a dropdown list of defined resources for general instance types. The default option here is *medium: 1 CPUs, 4 GiB Memory*. Select it.
 +
 image::module-07-tempinst/35_InstanceType_Resources.png[link=self, window=blank, width=100%]
 
-. The last section that needs to be completed to provision using an instance type is similar to the template section. You need to provide a name for the virtual machine, and select the storage class to be used for a backing disk. By default, a name will be generated for the VM, and the default storage class will be selected. When you are satisfied, click the *Create VirtualMachine* button.
+. The last section that needs to be completed when provisioning using an instance type is similar to the template section. You need to provide a name for the virtual machine, and select the storage class to be used for a backing disk. By default, a name will be generated for the VM, and the default storage class will be selected. When you are satisfied, click the *Create VirtualMachine* button.
 +
 image::module-07-tempinst/36_VM_Details.png[link=self, window=blank, width=100%]
 

content/modules/ROOT/pages/module-08-workingvms.adoc

@@ -7,13 +7,13 @@ This section of our lab is dedicated to the Day-2 operations that many administr
 [[service_route]]
 == Exposing an Application with a Service/Route
 
-By default, virtual machines are connected to the SDN, which is a convenient and easy way to give them access to the rest of the network, but can be challenging for the virtual machines, and other pods in the OpenShift cluster, to find and connect to the virtualized applications. To solve this, we will use a *Service* to balance connections across the two Windows-based web servers, and create a DNS entry for each service discovery, then create a *Route* to allow external clients to access the application hosted within the virtual machines.
+By default, virtual machines are connected to the SDN, which is a convenient and easy way to give them access to the rest of the network. However, it can be challenging for the virtual machines, and other pods in the OpenShift cluster, to find and connect to the virtualized applications. To solve this, we will use a *Service* to balance connections across the two Windows-based web servers, and create a DNS entry for each service discovery, then create a *Route* to allow external clients to access the application hosted within the virtual machines.
 
 IMPORTANT: If you have not completed the module *Migrating Existing Virtual Machines*, it is recommended that you do that module first. If you have not completed it, or the migration process is still pending, you can use pre-existing virtual machines that have been prepared for you, which are available in the *vmimported* project. If you are using these pre-imported virtual machines, please replace all instances of the *vmexamples* namespace with *vmimported* in the examples below.
 
 === Introduction to Services
 
-The *Service* identifies the source/target for traffic, and directs clients to, the endpoints based on labels. Currently, the VMs do not have a label assigned yet.
+The *Service* identifies the source/target for traffic, and directs clients to the endpoints based on labels. Currently, the VMs do not have a label assigned yet.
 
 In order to successfully associate the  VMs with the Service, we need to do the following:
 
@@ -33,7 +33,7 @@ image::module-08-workingvms/11_Imported_VMs_List.png[link=self, window=blank, wi
 NOTE: Ensure you select the correct project, *vmexamples-{user}* if you completed the *Migrating Existing Virtual Machines* module or *vmimported-{user}* if you did not.
 
 . Select to the *winweb01-{user}* VM and navigate to the *YAML* tab.
-. Find the *spec:* section and under the *template.metadata* add the following lines to *labels* section in the VM resources:
+. Find the *spec:* section and under the *template.metadata* add the following to the *labels* section:
 +
 [source,yaml,role=execute]
 ----
@@ -89,7 +89,7 @@ image::module-08-workingvms/16_Imported_VMs_Pods.png[link=self, window=blank, wi
 
 === Create the Route
 
-Now the Windows IIS servers are accessible from within the OpenShift cluster. Other virtual machines are able to access them using the DNS name *webapp.vmexamples*, which is determined by the name of the Service + the namespace. However, since these web servers are the front end to an application we want to be externally accessible, we will expose it using a *Route*.
+Now the Windows IIS servers are accessible from within the OpenShift cluster. Other virtual machines are able to access them using the DNS name *webapp.vmexamples*, which is determined by the name of the service + the namespace. However, since these web servers are the front end to an application, we want it to be externally accessible. This will be done by exposing it using a *Route*.
 
 . Navigate to *Networking* -> *Routes* in the left navigation menu, verify that you're using the correct project name. Press *Create Route*.
 +