Update guided workshop exercises for clarity and accuracy in instructions

Author: GeekTrainer

content/guided-workshop/exercises/1-code-scanning.md

@@ -24,12 +24,12 @@ Public repositories on GitHub automatically have Dependabot alerts. This feature
 
 1. Navigate to the repository you created for this workshop.
 1. Select the **Settings** tab.
-1. On the left side, select **Code security and analysis**.
-1. Locate the **Dependabot** section towards the middle of the page:
+2. On the left side, select **Code security**.
+3. Locate the **Dependabot** section towards the middle of the page:
 
     ![Screenshot of the dependabot section](./images/1-dependabot.png)
 
-1. Select **Enable** next to **Dependabot security updates** to configure Dependabot to create PRs to resolve alerts.
+4. Select **Enable** next to **Dependabot security updates** to configure Dependabot to create PRs to resolve alerts.
 
 You have now enabled Dependabot alerts and security updates! Should an insecure library be detected, you will both receive an alert, and Dependabot will create a new pull request to update the version number to a secure version of the library.
 

content/guided-workshop/exercises/2-issues.md

@@ -23,7 +23,9 @@ Our project needs two main updates. We want to make the updates to support devel
 1. Return to the repository you created at the beginning of this workshop.
 1. Select the **Issues** tab.
 1. Select **New issue**.
-1. Create new issues by adding the information indicated in the table below, selecting **Submit new issue** after creating each one (and using **New issue** to create a new one):
+2. If prompted for type, select **Blank issue**.
+3. Select **Create more** at the bottom of the page to streamline the creation process.
+4. Create new issues by adding the information indicated in the table below, selecting **Submit new issue** after creating each one:
 
     | Title                   | Description                                                                    |
     | ----------------------- | ------------------------------------------------------------------------------ |

content/guided-workshop/exercises/3-codespaces.md

@@ -21,20 +21,20 @@ One thing that's really great is the [default dev container](https://github.com/
 Let's create our own dev container! The [dev container is configured](https://docs.github.com/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers) by creating the Docker files Codespaces will use to create and configure the container, and providing any customizations in the `devcontainer.json` file. Customizations provided in `devcontainer.json` can include ports to open, commands to run, and extension to install in Visual Studio Code (either running locally on the desktop or in the browser). This configuration becomes part of the repository. All developers who wish to contribute can then create a new instance of the container based on the configuration you provided.
 
 1. Access the Command Palette (<kbd>F1</kbd> or clicking ☰ → View → Command Palette), then start typing **dev container**.
-1. Select **Codespaces: Add Development Container Configuration Files...** .
-2. Select **Add configuration to workspace**.
+2. Select **Codespaces: Add Development Container Configuration Files...** .
 3. Select **Create a new configuration...**.
-4. Select **From a predefined container configuration...**.
-5. Scroll down and select **Node.js & TypeScript**.
-6. Select **22-bookworm (default)**.
-7. Select the following features to add into your container:
+4. Scroll down and select **Node.js & TypeScript**.
+5. Select **22-bookworm (default)**.
+6. Select the following features to add into your container:
     - **GitHub CLI**
     - **Python**
 
     > [!NOTE]
     > You can type the name of the feature you want to filter the list.
 
-8.  Select **Keep defaults** to use the default configuration.
+7. Select **OK** to add the features.
+8. Select **Keep defaults** to use the default configuration.
+9. If you receive the prompt **File './.github/dependabot.yml' already exists, overwrite?**, select **Skip**.
 
 > [!IMPORTANT]
 > Your new container definition files will be created into the **.devcontainer** folder. **DO NOT** select **Rebuild Now**; we'll do that in just a moment.
@@ -98,11 +98,13 @@ You've now defined a custom container!
 
 Whenever someone uses the codespace you defined they'll have an environment with Node.js and Mongo DB, and the GitHub Copilot extension installed. Let's use this container!
 
-1. Open the command palette.
+1. Access the Command Palette (<kbd>F1</kbd> or clicking ☰ → View → Command Palette), then start typing **dev container**.
 1. Type **rebuild** and select **Codespaces: Rebuild container**.
 1. Select **Rebuild Container** on the dialog box. Your container now rebuilds.
 
 > **IMPORTANT:** Rebuilding the container can take several minutes. Obviously this isn't an ideal situation for providing fast access to your developers, even if it's faster than creating everything from scratch. Fortunately you can [prebuild your codespaces](https://docs.github.com/en/codespaces/prebuilding-your-codespaces) to ensure developers can spin one up within seconds.
+>
+> You may also be prompted to reload the window as extensions install. Reload the window as prompted.
 
 ## Interacting with the repository
 

content/guided-workshop/exercises/4-testing.md

@@ -46,14 +46,15 @@ Now that we have an overview of the structure of a workflow, let's ask Copilot t
 
 1. Create a new folder under **.github** named **workflows**.
 2. Create a new file named **server-test.yml** and ensure the file is open.
-3. Open GitHub Copilot Chat.
-4. Add the test file **test_app.py** to the context by using the `#` in the Chat dialog box and beginning to type **test_app.py**, and pressing <kbd>enter</kbd> when it's highlighted.
-5. Prompt Copilot to create a GitHub Action workflow to run the tests. Use natural language to describe the workflow you're looking to create (to run the tests defined in test_app.py), and that you want it to run on merge (for when new code is pushed), when a PR is made, and on demand.
+3. If prompted to install the **GitHub Actions** extension, select **Install**.
+4. Open GitHub Copilot Chat.
+5. Add the test file **test_app.py** to the context by using the `#` in the Chat dialog box and beginning to type **test_app.py**, and pressing <kbd>enter</kbd> when it's highlighted.
+6. Prompt Copilot to create a GitHub Action workflow to run the tests. Use natural language to describe the workflow you're looking to create (to run the tests defined in test_app.py), and that you want it to run on merge (for when new code is pushed), when a PR is made, and on demand.
 
   > [!IMPORTANT]
   > A prescriptive prompt isn't provided as part of the exercise is to become comfortable interacting with GitHub Copilot.
 
-6. Add the generated code to the new file. It should resemble the following:
+6. Add the generated code to the new file by hovering over the suggested code and selecting the **Insert at cursor** button. The generated code should resemble the following:
 
 ```yml
 name: Server Tests

content/guided-workshop/exercises/5-context.md

@@ -24,8 +24,9 @@ GitHub Copilot Chat has a set of available chat participants and extensions avai
 
 1. Return to your codespace, or reopen it by navigating to your repository and selecting **Code** > **Codespaces** and the name of your codespace.
 2. Open GitHub Copilot Chat.
-3. Type `@workspace` in the chat prompt window and hit <kbd>tab</kbd> to select or activate it, then continue by asking Copilot about your project. You can ask what technologies are in use, what the project does, where functionality resides, etc.
-4. Spend a few minutes exploring to find the answers to the following questions:
+3. Select the `+` icon towards the top to begin a new chat.
+4. Type `@workspace` in the chat prompt window and hit <kbd>tab</kbd> to select or activate it, then continue by asking Copilot about your project. You can ask what technologies are in use, what the project does, where functionality resides, etc.
+5. Spend a few minutes exploring to find the answers to the following questions:
     - What frameworks are currently in use?
     - Where's the database the project uses?
     - How is the frontend built?