additional cleanup

Author: jamesmontemagno

lab/part0-exploring-codebase.md

@@ -7,7 +7,6 @@ GitHub Copilot Chat allows you to ask questions about your code and get intellig
    ![Open chat window dialog](./images/1-open-copilot-chat.png)
 1. [] Try asking questions about the project structure:
    - `What projects are in this solution and how do things work together?`
-   - `What is the TinyShop application architecture?`
    - `How does the Products API work?`
 1. [] Notice how Copilot analyzes your codebase to provide contextual answers.
 

lab/part1-code-completion.md

@@ -25,7 +25,6 @@ In this section, you'll use GitHub Copilot's code completion to implement API en
    ![NES showing up](./images/1-nes.png)
 
 1. [] We now can implement the following endpoints using GitHub Copilot:
-   - GET product by ID
    - POST to create a new product
    - PUT to update a product
    - DELETE to remove a product
@@ -160,8 +159,7 @@ In this section, you'll use GitHub Copilot's code completion to implement API en
    }
    ```
 
-   > [!IMPORTANT]
-   >Because LLMs are probabilistic, not deterministic, the exact code generated can vary. The above is a representative example. If your code is different, that's just fine as long as it works!
+   > NOTE: Because LLMs are probabilistic, not deterministic, the exact code generated can vary. The above is a representative example. If your code is different, that's just fine as long as it works!
 
 1. [] Go back to **ProductEndpoints.cs**, and try changing the variable name of **id** to `productId` in the new **MapGet** method and see Next Edit Suggestions help out.
 

lab/part2-enhancing-ui.md

@@ -2,14 +2,13 @@
 
 Now, you'll improve the loading experience using Copilot's inline chat.
 
-> [!NOTE]
-> This exercise does supply specific prompts to type, but as part of the learning experience we encourage you to discover how to interact with Copilot. Feel free to talk in natural language, describing what you're looking for or need to accomplish.
+> NOTE: This exercise does supply specific prompts to type, but as part of the learning experience we encourage you to discover how to interact with Copilot. Feel free to talk in natural language, describing what you're looking for or need to accomplish.
 
 1. [] In the **Solution explorer** under the **Store** project open **Components/Pages/Products.razor**.
 1. [] Find the "Loading..." text in the code.
 1. [] Select this text and right-click.
 1. [] Choose "Ask Copilot" or press `Alt+/`.
-1. [] In the inline chat, type: "Update this to have a loading progress spinner and the text: Loading... under it"
+1. [] In the inline chat, type: `Update this to have a loading progress spinner`
 
     ![Screenshot of VS with inline chat](./images/2-inline-code.png)
 

lab/part3-referencing-files.md

@@ -18,7 +18,6 @@ In this section, you'll learn how to reference existing code files in your chat
 1. [] Type: `#ProductService.cs` to reference the ProductService file.
 1. [] Ask: `How would I implement getting and visualizing the products in a table using the code in #ProductService and the css required.`
 1. [] Review the code suggestion but don't implement it yet.
-1. [] Follow up with: `How would this look in a grid instead of a list?`
 1. [] Notice how Copilot can reference existing code to provide contextual suggestions.
 
 **Key Takeaway**: Referencing files in your chat provides Copilot with the context it needs to give more accurate, project-specific suggestions.

lab/part4-custom-instructions.md

@@ -21,8 +21,8 @@ Here are some guidelines to consider when creating a Copilot instructions file:
 
 ## Create a Copilot instructions file
 
-1. [] In the **Solution Explorer**, expand the **Solution Items** and open **copilot-instructions.mc**. 
-    > This file is located in the **.github* folder in the root of the repository.
+1. [] In the **Solution Explorer**, expand the **Solution Items** and open **copilot-instructions.md**
+
 1. [] Add project-specific information about your application:
 
     ```markdown
@@ -43,9 +43,8 @@ Here are some guidelines to consider when creating a Copilot instructions file:
    ![New chat](./images/5-new-edits.png)
 
 1. [] Go back to Copilot Chat and re-run the prompt from Part 3, you can do this by pressing the up key. or
-    i. [] Ask: `How would I implement getting and visualizing the products in a table using the code in #ProductService and the css required.`
-    i. [] Review the code suggestion but don't implement it yet.
-    i. [] Follow up with: `How would this look in a grid instead of a list?`
+1. [] Ask: `How would I implement getting and visualizing the products in a table using the code in #ProductService and the css required.`
+1. [] Review the code suggestion but don't implement it yet.
 1. [] Notice how the responses now incorporate your custom instructions.
 
 **Key Takeaway**: Custom instructions make Copilot's suggestions more aligned with your project standards and architecture preferences.

lab/part5-implementing-features.md

@@ -20,13 +20,11 @@ Let's add the ability to see a list of images into the app:
 
     ![Select Sonnet in Copilot](./images/5-select-sonnet.png)
 
-1. [] Type: `Implement a product listing page in Products.razor that fetches products from #ProductService and displays them in a list with product name, description, price, and image.`
+1. [] Type: `Implement a simple product listing page in Products.razor that fetches products from #ProductService and displays them in a simple list with product name, description, price, and image.`
 
-    > [!NOTE]
-    > You should use your own phrasing when generating the prompt. As highlighted previously, part of the exercise is to become comfortable creating prompts for GitHub Copilot. One key tip is it's always good to provide more guidance to ensure you get the code you are looking for.
+    > NOTE: You should use your own phrasing when generating the prompt. As highlighted previously, part of the exercise is to become comfortable creating prompts for GitHub Copilot. One key tip is it's always good to provide more guidance to ensure you get the code you are looking for.
 
-    > [!NOTE]
-    > If you are asked to **Enable Claude 3.5 Sonnet for all clients** click on **Enable** button.
+    > NOTE: If you are asked to **Enable Claude 3.5 Sonnet for all clients** click on **Enable** button.
 
 Copilot agent mode begins implementing the code suggestions!
 
@@ -36,7 +34,7 @@ Unlike our prior examples where we worked with an individual file, we're now wor
 
 GitHub Copilot will propose the following changes to the application including updating the Products.razor and adding a Products.razor.css and maybe more.
 
-1. [] Review the suggestions and click "Accept All" to implement the code.
+1. [] Review the code changes from Agent mode
 
     The code should look similar to the following:
     ```html

lab/part6-copilot-vision.md

@@ -3,7 +3,7 @@
 In this section, you'll use Copilot Vision. You can share screenshots of errors and Copilot will interpret the image and resolve the issue. Or share mockups of new designs, and Vision will help you bring them to life. Let's update our design based on a photo our design gave us.
 
 1. [] Open a new Copilot Chat thread in Agent mode.
-1. [] Click the **+** button in the chat, select **upload image**, and select the store application image that is found in the GitHub repo that is cloned called **eshop.png** inside of the **C:\Users\LabUser\Source\Repos\build-2025-lab300** directory.
+1. [] Click the **+** button in the chat, select **upload image**, and select the store application image that is found in the GitHub repo that is cloned called **eshop.png** inside of the `C:\Users\LabUser\Source\Repos\build-2025-lab300` directory.
 
     ![Attach image icon](./images/6-add-image.png)
 

lab/part7-debugging-with-copilot.md

@@ -2,16 +2,15 @@
 
 In this section, you'll learn how to use Copilot to debug an exception in your application.
 
-1. Launch the web application if it isn't yet
-1. Click on the **Go to About** button in the navigation menu.
-1. Observe that an exception occurs, and the application crashes.
-1. Press the **Ask Copilot** option in the pop up.
+1. [] Debug the **AppHost** project if it isn't yet, and open the **store** from teh .NET Aspire dashboard.
+1. [] Click on the **Go to About** button in the navigation menu.
+1. [] Observe that an exception occurs, and the application crashes.
+1. [] Press the **Ask Copilot** option in the pop up.
 
     ![Pop up for exception with Ask Copilot option](./images/7-ask-copilot-exception.png)
 
-1. Review how Copilot brings in debugger information, including stack traces and variable states.
-1. Note how Copilot recommends a fix for the issue or provides code suggestions to resolve it.
-1. Implement the suggested fix and re-run the application to verify the issue is resolved.
+1. [] Review how Copilot brings in debugger information, including stack traces and variable states.
+1. [] Note how Copilot recommends a fix for the issue or provides code suggestions to resolve it.
 
 **Key Takeaway**: Copilot can assist in diagnosing and fixing exceptions by analyzing debugger information and providing actionable recommendations.
 
@@ -30,15 +29,13 @@ In this subsection, you'll learn how to use Copilot to analyze variables using w
     >Note: you can also see these in the Locals or watch windows
 
 1. [] Observe how Copilot provides detailed information about the variable, including its value and potential issues.
-1. [] Use the insights provided by Copilot to verify or debug the behavior of the **imagePrefix** variable.
 1. [] Hover over the **products** collection and click the **View** button with the magnifier icon.
 
     ![View button on products](./images/7-view-products.png)
 
 1. [] Use the visualizer to inspect the contents of the **products** collection.
-1. [] Click the sparkle button and, in natural language, type:  
-    *"Products that have the name outdoor in them and are under 10 dollars"*.  
-    Observe how Copilot generates the appropriate expression automatically.
+1. [] Click the sparkle button and, in natural language, type:  `Products that have the name outdoor in them and are under 40 dollars`
+1. [] Observe how Copilot generates the appropriate expression automatically.
 
     ![Sparkle icon for visualizer](./images/7-visualizer-sparkle.png)
 

lab/part8-commit-summary-descriptions.md

@@ -8,17 +8,14 @@ In this section, you'll learn how to use GitHub Copilot to generate commit messa
    ![VS commit dialog with AI button](./images/8-commit.png)
 
 1. [] Navigate to **Tools -> Options -> GitHub -> Copilot -> Source Control Integration**.
-1. [] Update the commit message customization setting to:  
-   *"Summarize in a few sentences and then highlight the top 5 changes with emoji and short descriptions."*
+1. [] Update the commit message customization setting to: `Summarize in a few sentences and then highlight the top 5 changes with emoji and short descriptions`
 1. [] Return to the **Git Changes** view and generate a new commit message.
 1. [] Observe how the new commit message reflects the updated customization.
 
 **Key Takeaway**: Copilot can help you create meaningful and well-structured commit messages, saving time and improving collaboration.
 
 ## Code Reviews with Copilot
 
-1. [] Navigate to **Tools -> Options -> GitHub -> Copilot -> Source Control Integration**.
-1. [] Ensure the **Code Review Assistance** feature is turned on.  
 1. [] Before submitting your changes, use the **Code Review** feature to analyze your code for potential improvements and suggestions.
 
    ![Code Review Assistance toggle](./images/8-code-review.png)