Fix titles

contents/create.rst

@@ -171,7 +171,7 @@ Spec Editables
 
 #. Edit the **specs/basiclinuxvm_cloudinit_data.yaml** file so that it contains the following.  Ensure indentation is exactly as shown below.
 
-   .. code-block:: yaml
+   .. code-block::
 
       #cloud-config
       users:

contents/launch.rst

@@ -54,11 +54,11 @@ Direct Launch
 
      .. note::
 
-    - Save the **runtime_variables.py** and exit using the following key sequence:
+        - Save the **runtime_variables.py** and exit using the following key sequence:
 
-      - ESC
-      - :wq
-      - ENTER
+        - ESC
+        - :wq
+        - ENTER
 
 #. As mentioned in previous steps, **HelloBlueprint_<initials>** was created with some default credentials in the form of an SSH key pair.  We don't need to generate our own and can now launch the blueprint, along with specifying the runtime variables file created in the previous step.  Enter the following command to launch the **HelloApp_<initials>** app.  Replace **<initials>** with your initials.
 
@@ -189,4 +189,4 @@ This section of the lab covered the high-level specifics of blueprint launches:
 - Publishing HelloBlueprint to the Calm Marketplace
 - Launching HelloBlueprint from the Calm Marketplace, via HelloApp_<initials>
 
-In the next section we'll take a look at some of the ways blueprints can be shared between application design and automation teams: Blueprint Decompile.
+In the next section we'll take a look at some of the ways blueprints can be shared between application design and automation teams: Blueprint Decompile.

index.rst

@@ -61,4 +61,4 @@ This lab can be run in a couple of different ways.  Primarily:
 Get Started
 ###########
 
-With all that out of the way, let's now start by looking at some of the `conventions that will be used <contents/master_follow/>`_.
+With all that out of the way, let's now start by looking at some of the `conventions that will be used <contents/master_follow.html>`_.