updated exercise 2 - analyze and document

Author: ChrisHowd

Instructions/Labs/LAB_AK_02_analyze_document_code.md

@@ -102,7 +102,7 @@ Use the following steps to set up the library application:
 
     For example, in the SOLUTION EXPLORER view, right-click **AccelerateDevGHCopilot**, and then select **Build**.
 
-    You'll see some Warnings, but there shouldn't be any Errors.
+    You may see some Warnings, but there shouldn't be any Errors.
 
 ## Use GitHub Copilot to explain the library application codebase
 
@@ -112,9 +112,9 @@ GitHub Copilot can help you to understand an unfamiliar codebase by generating e
 
 GitHub Copilot's Chat view includes a chat-based interface that allows you to interact with GitHub Copilot using natural language prompts. When evaluating an existing codebase for the first time, you can create prompts that generate an explanation at the workspace or project level, or at the code block or code line level. To assist you in specifying the context of your prompt, GitHub Copilot provides chat participants, chat variables, and slash commands.
 
-- Chat participants are used to scope your prompt to a specific domain.
-- Chat variables are used to include specific context in your prompt.
-- Slash commands are used to avoid writing complex prompts for common scenarios.
+- Use chat participants in your prompts to invoke a domain-specific expert. Experts provide the most accurate responses.
+- Use chat variables in your prompts to include specific context. Context helps GitHub Copilot generate more relevant responses.
+- Use slash commands in your prompts to invoke specific actions or to set the intent of your prompt.
 
 Use the following steps to complete this section of the exercise:
 
@@ -124,25 +124,21 @@ Use the following steps to complete this section of the exercise:
 
     To open the Chat view, select the **Toggle Chat** button at the top of the Visual Studio Code window.
 
-    ![Screenshot showing the GitHub Copilot status menu.](./Media/m02-github-copilot-toggle-chat.png)
-
     You can also open the Chat view using the **Ctrl+Alt+I** keyboard shortcut.
 
-1. In the Chat view, enter a prompt that uses GitHub Copilot's **@workspace** Chat participant to generate a description of the project.
+1. In the Chat view, enter a prompt that uses the **#codebase** chat variable to include the full context of the codebase when generating a description of your code.
 
     For example, enter the following prompt in the Chat view:
 
     ```plaintext
-    @workspace describe this project
+    #codebase describe this project
     ```
 
-    Use Chat participants, such as the **@workspace**, to improve the responses generated by GitHub Copilot. Chat participants work like domain experts who can help you in their specialized areas. Use **@workspace** when you want GitHub Copilot to consider the structure of your project, how different parts of your code interact, or design patterns in your project.
-
-    To see a list of all available chat participants, type **@** in the chat prompt box.
+    Use chat variables, such as **#codebase**, to include specific context in your prompt. Context helps GitHub Copilot generate more relevant responses.
 
 1. Take a minute to compare GitHub Copilot's response with the actual project files.
 
-    You should see a response that describes each of the projects in the solution:
+    You should see a response that describes all of the projects included in the solution:
 
     - **Library.ApplicationCore**
     - **Library.Console**
@@ -151,39 +147,31 @@ Use the following steps to complete this section of the exercise:
 
 1. Use the SOLUTION EXPLORER view to expand the project folders.
 
-1. Locate and then open the **ConsoleApp.cs** file.
-
-    The ConsoleApp.cs file is located in the **src/Library.Console** folder.
-
-1. Take a moment to review the code file.
+1. Take a moment to review the project files.
 
-1. Enter a prompt in the Chat view that generates a description of the **ConsoleApp** class.
+1. Enter a prompt in the Chat view that asks how to publish your codebase to a private GitHub repository.
 
     For example, enter the following prompt in the Chat view:
 
     ```plaintext
-    @workspace #usages How is the ConsoleApp class used?
+    @github #codebase What's the easiest way to publish my current codebase to a private GitHub repo from within Visual Studio Code? 
     ```
 
-    Use chat variables, such as **#usages**, to include specific context in your prompt. To see a list of the chat variables, type **#** in the chat prompt box.
+    Use chat participants, such as **@github**, to assign a domain expert for your prompt. Domain experts help GitHub Copilot generate accurate responses.
 
     > **NOTE**: GitHub Copilot considers your chat history and the code files you have open in Visual Studio Code when constructing a context for your prompt and generating a response.
 
-1. Take a minute to verify the accuracy of GitHub Copilot's response.
-
-    You should see a response that the describes where the **ConsoleApp** class is defined and how it's used in the codebase. The ConsoleApp.cs and Program.cs files are referenced in the response, along with line numbers
-
 1. Open the **Program.cs** file and examine the code.
 
 1. Enter a prompt in the Chat view that generates an explanation of the Program.cs file.
 
     For example, enter the following prompt in the Chat view:
 
     ```plaintext
-    @workspace /explain Explain the Program.cs file
+    /explain #codebase Explain the Program.cs file
     ```
 
-    Use Slash commands, such as **/explain**, to avoid writing complex prompts for common scenarios. To see a list of all available slash commands, type **/** in the chat prompt box. Available slash commands may vary, depending on your environment and the context of your chat.
+    Use slash commands, such as **/explain**, to specify the intent of your prompt. Communicating your intent helps GitHub Copilot understand the type of response that it needs to generate. The list of available slash commands may vary depending on your environment and the context of your chat.
 
 1. Take a minute to review the detailed response generated by GitHub Copilot.
 
@@ -193,28 +181,26 @@ Use the following steps to complete this section of the exercise:
 
 ### Improve chat responses by adding context
 
-GitHub Copilot uses context to generate more relevant responses.
+GitHub Copilot uses context to generate relevant responses.
 
-Opening files in the code editor is one way to establish context, but you can also add files to the Chat context using drag-and-drop operations or by using the **Attach Context** button in the Chat view.
+Opening files in the code editor is one way to establish context, but you can also add files to the Chat context using drag-and-drop operations or by using the **Add Context** button in the Chat view.
 
 Use the following steps to complete this section of the exercise:
 
 1. Expand the **Library.Infrastructure** project, and then expand the **Data** folder.
 
 1. Use a drag-and-drop operation to add the following files from the SOLUTION EXPLORER view to the Chat context: **JsonData.cs**, **JsonLoanRepository.cs**, and **JsonPatronRepository.cs**.
 
-    GitHub Copilot uses the Chat Context to understand the code files that are relevant to your prompt. You can add files to the Chat context using drag-and-drop operations, or you can use the **Attach Context** button in the Chat view.
-
-    Instead of adding individual files manually, you can let Copilot find the right files from your codebase automatically. This can be useful when you don't know which files are relevant to your question.
+    GitHub Copilot uses the Chat context to understand the code files that are relevant to your prompt. You can add files to the Chat context using drag-and-drop operations, or you can use the **Add Context** button in the Chat view.
 
-    To let Copilot find the right files automatically, add #codebase in your prompt or select Codebase from the list of context types.
+    Instead of adding individual files manually, you can let Copilot find the right files from your codebase. This approach can be useful when you don't know which files are relevant to your question, but it does slow down the response time.    To let Copilot find the right files automatically, add #codebase in your prompt.
 
 1. Enter a prompt in the Chat view that generates an explanation of the data access classes.
 
     For example, enter the following prompt in the Chat view:
 
     ```plaintext
-    @workspace /explain Explain how the data access classes work
+    /explain Explain how the data access classes work
     ```
 
 1. Take a couple minutes to read through the response.
@@ -237,7 +223,7 @@ Use the following steps to complete this section of the exercise:
 
 1. Ensure that you have the **Solution Explorer** view open.
 
-    The Solution Explorer view is not the same as the Explorer view. The Solution Explorer view uses project and solution files as "directory" nodes to display the structure of the solution.
+    The Solution Explorer is a dedicated view added to Visual Studio Code's primary sidebar by the C# Dev Kit extension. It provides a structured, solution-centric view of your .NET application that's similar to the Solution Explorer in the Visual Studio IDE. It's more informative and organized than the plain folder/file tree that the built-in Explorer view.
 
 1. To run the application, right-click **Library.Console**, select **Debug**, and then select **Start New Instance**.
 
@@ -302,13 +288,13 @@ Use the following steps to complete this section of the exercise:
 
 1. Add a new file named **README.md** to the root folder of the **AccelerateDevGHCopilot** solution.
 
-1. Open the Chat view.
+1. Open the Chat view, and select the **Ask** agent mode.
 
 1. To generate project documentation for your README file, enter the following prompt:
 
     ```plaintext
 
-    @workspace Generate the contents of a README.md file for a code repository. Use "Library App" as the project title. The README file should include the following sections: Description, Project Structure, Key Classes and Interfaces, Usage, License. Format all sections as raw markdown. Use a bullet list with indents to represent the project structure. Do not include ".gitignore" or the ".github", "bin", and "obj" folders.
+    #codebase I need you to generate the contents of a README.md file that I can use for the current code repository. Use "Library App" as the project title. The README file should include the following sections: Description, Project Structure, Key Classes and Interfaces, Usage, License. Format all sections as raw markdown. Use a bullet list with indents to represent the project structure. Do not include ".gitignore" or the ".github", "bin", and "obj" folders. I want add the suggested content to the README.md file that's open in the editor.
 
     ```