Small markdown updates

Author: GeekTrainer

.gitignore

@@ -37,4 +37,6 @@ instance/
 .webassets-cache
 flask_session/
 .coverage
-htmlcov/
+htmlcov/
+
+test-results/

content/full-day/1-code-scanning.md

@@ -50,8 +50,8 @@ Regardless of the reason, even seemingly innocuous tokens can create a security
 Let's enable Secret scanning to detect any potential keys.
 
 1. On the same page (**Settings** > **Code security and analysis**), towards the very bottom, locate the **Secret scanning** section.
-1. Next to **Receive alerts on GitHub for detected secrets, keys or other tokens**, select **Enable**.
-1. Next to **Push protection**, select **Enable** to block pushes to the repository which contain a [supported secret][supported-secrets].
+2. Next to **Receive alerts on GitHub for detected secrets, keys or other tokens**, select **Enable**.
+3. Next to **Push protection**, select **Enable** to block pushes to the repository which contain a [supported secret][supported-secrets].
 
     ![Screenshot of fully configured secret scanning](./images/1-secret-scanning.png)
 

content/full-day/2-issues.md

@@ -26,9 +26,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**.
-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:
+1. If prompted for type, select **Blank issue**.
+1. Select **Create more** at the bottom of the page to streamline the creation process.
+1. Create new issues by adding the information indicated in the table below, selecting **Submit new issue** after creating each one:
 
     | Title                   | Description                                                                    |
     | ----------------------- | ------------------------------------------------------------------------------ |
@@ -42,9 +42,11 @@ Our project needs two main updates. We want to make the updates to support devel
 You've now defined all the issues for the workshop! You'll use these issues to help guide your progress through the workshop.
 
 ## Summary and next steps
+
 GitHub Issues are the core to project management on GitHub. Their flexibility allows your organization to determine the best course of action to support your development lifecycle's methodology. With your issues created, it's time to turn your attention to the first big change to the project, [defining a codespace][walkthrough-next].
 
 ## Resources
+
 - [GitHub Issues][issues-docs]
 - [Communicate using markdown][skills-markdown]
 - [GitHub Projects][projects-docs]

content/full-day/3-codespaces.md

@@ -104,8 +104,8 @@ 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. 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.
+2. Type **rebuild** and select **Codespaces: Rebuild container**.
+3. 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][codespace-prebuild] to ensure developers can spin one up within seconds.
@@ -149,9 +149,11 @@ Custom containers for GitHub Codespaces become part of the source code for the r
 
 
 ## Summary and next steps
+
 Congratulations! You have now defined a custom development environment including all services and extensions. This eliminates the initial setup hurdle normally required when contributing to a project. Let's use this codespace to [implement testing and continuous integration][walkthrough-next] for the project.
 
 ## Resources
+
 - [GitHub Codespaces][codespaces]
 - [Getting started with GitHub Codespaces][codespaces-docs]
 - [Defining dev containers][dev-containers-docs]

content/full-day/4-testing.md

@@ -54,10 +54,10 @@ Now that we have an overview of the structure of a workflow, let's ask Copilot t
 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.
+> [!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 by hovering over the suggested code and selecting the **Insert at cursor** button. The generated code should resemble the following:
+7. 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
@@ -154,6 +154,7 @@ You've now seen a workflow, and explore the details of a run!
 Congratulations! You've implemented automated testing, a standard part of continuous integration, which is critical to successful DevOps. Automating these processes ensures consistency and reduces the workload required for developers and administrators. You have created a workflow to run tests on any new code for your codebase. Let's explore [context with GitHub Copilot chat][walkthrough-next].
 
 ### Resources
+
 - [GitHub Actions][github-actions]
 - [GitHub Actions Marketplace][actions-marketplace]
 - [About continuous integration][about-ci]

content/full-day/5-context.md

@@ -127,4 +127,3 @@ Congratulations! You've explored context in GitHub Copilot, which is key to gene
 [walkthrough-codespaces]: ./3-codespaces.mdvisualstudio.com/docs/copilot/copilot-chat
 [walkthrough-next]: 6-code.md
 [walkthrough-previous]: 4-testing.md
-