Wms id 11643 eli edits (#416)

* Minor fixes

* Clean-up of a few minor typos.

oci-pulumi-self-service/livelabs/ocw24-livelabs/01-prepare-tenancy/prepare.md

@@ -164,13 +164,7 @@ To simplify the remaining steps in the workshop, we recommend using an OCI comup
 
     >Note: You can copy the entire block of commands and paste it in your terminal. You might be prompted a few times to press enter to accept the defaults, or type `Y` to agree.
 
-4. Restart the shell session.
-
-    ```bash
-    <copy>
-    source ~/.profile
-    </copy>
-    ```
+4. Part of the code block above alters the permissions for the Ubuntu user. To instantiate the changes, you must exit and reconnect to your SSH session.
 
     >Note: The best way to check permissions is to run `docker ps` - if you get an error, you'll need to disconnect from the server, then reconnect (to fully recycle your user session)
 

oci-pulumi-self-service/livelabs/ocw24-livelabs/02-deploy-infra/deploy-infra.md

@@ -50,7 +50,7 @@ Estimated time: 20 minutes
     For more information, please visit the project page: https://www.pulumi.com/docs/
     ```
 
-## Create a Python virtual environment and install the Pulumi OCI provider
+## Task 2: Create a Python virtual environment and install the Pulumi OCI provider
 
 1. Create a new Python virtual environment with Python 3.10
 
@@ -105,7 +105,7 @@ Estimated time: 20 minutes
 
 4. Provide a name the stack (e.g. OCW-2024) and press enter.
 
-## Task 2: Build out your Pulumi project
+## Task 3: Build out your Pulumi project
 
 1. Now that you have a Pulumi stack, you'll need to provide some environment configuration details. Copy the commands below to a text file and replace the `<placeholder>` values with the data you gathered in lab 1.
 
@@ -180,7 +180,7 @@ Estimated time: 20 minutes
 
     ![View the Backstage dashboard](images/backstage-dashboard.png)
 
-## Task 3: Create a new Pulumi Environment
+## Task 4: Create a new Pulumi Environment
 Pulumi environments, secrets, and configuration - or ESC for short - enables teams to centralize secrets and configuration data in a central repository. ESC is intended to provide frictionless security, improve developer efficiency, enhance compliance, and mitigate sprawl. On top of that, ESC easiliy integrates with a variety of platforms, making it a cinch to add to your IaC efforts.
 
 1. Return to the app.pulumi.com portal, making sure you're logged in, and click **Environments** on the left navigation menu.
@@ -202,11 +202,11 @@ Pulumi environments, secrets, and configuration - or ESC for short - enables tea
       oracle:
         default:
           userOcid: <you user OCID here>>
-            fingerprint: <your API key fingerprint here>>
-            tenancyOcid: <your tenancy OCID here>
-            region: <your selected region here>
-            privateKey:
-              fn::secret: "<paste API private key contents here>"
+          fingerprint: <your API key fingerprint here>>
+          tenancyOcid: <your tenancy OCID here>
+          region: <your selected region here>
+          privateKey:
+            fn::secret: "<paste API private key contents here>"
       # Configuration nested under the "pulumiConfig" key will be available to Pulumi stacks that
       # reference this Environment during `pulumi up/preview/refresh/destroy`
       pulumiConfig:
@@ -218,7 +218,7 @@ Pulumi environments, secrets, and configuration - or ESC for short - enables tea
     </copy>
     ```
 
-    >Note: Your pasted values should look something like this:
+    >Note: Your pasted values should look something like the following. You may need to indent the contents of your API key to align with `fn::secret` as shown below:
 
     ```bash
     # values is a required top-level key

oci-pulumi-self-service/livelabs/ocw24-livelabs/03-first-template/first-template.md

@@ -30,21 +30,9 @@ Estimated time: 20 minutes
 
 4. Click **`[NEXT]`** and fill in the Pulumi template details.
 
-    * **Organization** - Enter somethign like, "Workshop"
+    * **Organization** - This is your Pulumi organization name. More than likely, it is the same as your Pulumi ID
     * **Pulumi ESC** - **`oci-pulumi-self-service`**
-    * **Select stack** - Pick one [Development | QA | Production]
-    * **Website content** - Copy and paste the following: 
-
-        ```
-        <copy>
-        <html>
-        <head>
-        <title>OCI + Pulumi + Backstage = Self Service Portal</title>
-        <h1>Well done - your first template deployment!</h1>
-        </head>
-        </html>
-        </copy>
-        ```
+    * **Select stack** - Pick one [Oracle-CloudWorld2024 | Development | QA | Production]
 
 5.  Click **`[NEXT]`** and fill in the Repository Location (where Backstage will store your output code).
 

oci-pulumi-self-service/livelabs/ocw24-livelabs/04-oke-template/oke-template.md

@@ -56,7 +56,6 @@ In this lab you will register additional templates from a Github repository, the
 
 2. Given the addition of two entities in the first task, we can now track component ownership. As you provision additional components related to particular groups, it is easy to explore the relationships between the different entities.
 
-3. 
 
 You may now **proceed to the next lab**.