Updated Acrolinx flagger spelling and grammar during PR review

Author: ChrisHowd

learn-pr/wwl-azure/develop-code-features-using-github-copilot-tools/includes/5-generate-code-github-copilot-chat.md

@@ -92,10 +92,10 @@ The Plan agent is designed to help you research and plan a task before writing a
 
 ### Use the Agent to generate code
 
-When using the Agent, GitHub Copilot acts as an autonomous agent that can take actions on your behalf. You can ask GitHub Copilot to perform specific tasks, and it generates code based on your requests.
+When you use GitHub Copilot in Agent mode, GitHub Copilot acts as an autonomous agent that can take actions on your behalf. You can ask GitHub Copilot to perform specific tasks, and it generates code based on your requests.
 
 > [!IMPORTANT]
-> When you use the Agent, GitHub Copilot may make multiple premium requests to complete a single task. Premium requests can be used by user-initiated prompts and follow-up actions GitHub Copilot takes on your behalf. The total premium requests used depends on the complexity of the task, the number of steps involved, and the model selected.
+> When you use the Agent mode, GitHub Copilot may make multiple premium requests to complete a single task. Premium requests can be used by user-initiated prompts and follow-up actions GitHub Copilot takes on your behalf. The total premium requests used depends on the complexity of the task, the number of steps involved, and the model selected.
 
 1. Open the Chat view and select **Agent** from the agent picker.
 

learn-pr/wwl-azure/develop-unit-tests-using-github-copilot-tools/includes/2-examine-github-copilot-support-unit-tests.md

@@ -55,7 +55,7 @@ Alternatively, you can:
 1. Follow GitHub Copilot's suggestions to fix the test
 
 > [!TIP]
-> When using agents, the agent monitors the test output when running tests, and automatically attempts to fix and rerun failing tests.
+> When using GitHub Copilot in Agent mode, the agent monitors the test output when running tests, and automatically attempts to fix and rerun failing tests.
 
 ### Maintain consistency
 

learn-pr/wwl-azure/generate-documentation-using-github-copilot-tools/includes/2-review-github-copilot-explain-document-features.md

@@ -16,11 +16,11 @@ The following GitHub Copilot features can be used to analyze and explain code:
 
 The following GitHub Copilot features can be used to generate inline code documentation:
 
-- Ask mode: Use the ask mode to suggest inline code documentation for a code file, class, or method. Review the suggested inline documentation in the Chat view. Request updates as needed in the chat conversation. Once you're satisfied with the proposed documentation, you can insert the suggested documentation into the corresponding code file.
+- Ask mode: Use the Ask agent mode to suggest inline code documentation for a code file, class, or method. Review the suggested inline documentation in the Chat view. Request updates as needed in the chat conversation. Once you're satisfied with the proposed documentation, you can insert the suggested documentation into the corresponding code file.
 
-- Plan mode: Use the Plan mode to create a detailed implementation plan for your documentation tasks. The Plan mode can be used to analyze the codebase, identify documentation requirements, and produce a step-by-step plan. Once the plan is approved, you can hand it off to agent mode for execution.
+- Plan mode: Use the Plan mode to create a detailed implementation plan for your documentation tasks. The Plan mode can be used to analyze the codebase, identify documentation requirements, and produce a step-by-step plan. Once the plan is approved, you can hand it off to Agent mode for execution.
 
-- Agent mode: Use the agent mode to autonomously generate inline code documentation for specified code projects, files, classes, or methods. Have the agent perform other tasks during or after the documentation process. Accept or reject the updates when the agent has completed the assigned tasks.
+- Agent mode: Use the Agent mode to autonomously generate inline code documentation for specified code projects, files, classes, or methods. Have the agent perform other tasks during or after the documentation process. Accept or reject the updates when the agent has completed the assigned tasks.
 
 - Inline chat - Use an inline chat session to work directly in the code editor. The inline chat is useful when you want to document specific code (classes, methods, or code blocks) without leaving the editor. You can provide specific instructions in the prompt or use the `/doc` slash command without specific information if you want. Updates are displayed in the code editor and can be accepted or rejected. You can also choose the option to rerun the prompt with or without updates.
 

learn-pr/wwl-azure/generate-documentation-using-github-copilot-tools/includes/3-examine-github-copilot-prompts-keywords.md

@@ -103,7 +103,7 @@ About the `@workspace` keyword:
 - The `@workspace` keyword is a chat participant that's dedicated to answering questions about your codebase.
 - The `@workspace` keyword takes control of the user prompt and uses the codebase to provide an answer.
 - The `@workspace` keyword can't invoke other tools.
-- The `@workspace` keyword can only be used when you're using the ask mode.
+- The `@workspace` keyword can only be used when you're using the Ask agent mode.
 - Example: "`@workspace how can I validate a date?`"
 
 About the `#codebase` keyword:

learn-pr/wwl-azure/generate-documentation-using-github-copilot-tools/includes/4-analyze-explain-code-using-github-copilot.md

@@ -7,13 +7,13 @@ Each of the following GitHub Copilot features can be used to analyze or explain
 - Smart actions: Run the Explain smart action to explain selected code without even having to write a prompt.
 - Quick Chat: Ask a quick question and get back into what you're doing.
 
-## Use the Chat view in ask mode to analyze and explain code
+## Use the Chat view in Ask agent mode to analyze and explain code
 
 The Chat view in Visual Studio Code is used to manage chat conversations between you and the AI pair programmer. By default, the Chat view is located in the Secondary Side Bar on the right side of the Visual Studio Code window. When you submit a prompt, the AI pair programmer responds with natural language descriptions, code snippets, and other relevant information. Responses are displayed in the Chat view.
 
-To access the Chat view, you can select the **Toggle Chat** button (Copilot icon), select **Open Chat** from the GitHub Copilot menu, or use the **Ctrl+Alt+I** keyboard shortcut. The Chat view defaults to ask mode, but retains the most recently selected mode when you toggle between open and hidden.
+To access the Chat view, you can select the **Toggle Chat** button (Copilot icon), select **Open Chat** from the GitHub Copilot menu, or use the **Ctrl+Alt+I** keyboard shortcut. The Chat view defaults to Ask agent mode, but retains the most recently selected mode when you toggle between open and hidden.
 
-You can use the Chat view in ask mode for a wide range of topics. For example:
+You can use the Chat view in Ask agent mode for a wide range of topics. For example:
 
 - Ask questions about coding and technology concepts ("`What is a linked list?`", "`top 10 popular web frameworks`")
 - Brainstorm ideas on how to best solve a coding problem ("`How to add auth to my project?`")
@@ -23,17 +23,17 @@ You can use the Chat view in ask mode for a wide range of topics. For example:
 
 ![Screenshot showing the Chat view asking about the Singleton pattern.](../media/explain-chat-view-workspace-explain-singleton-pattern.png)
 
-The ask mode supports the following interface features:
+The Ask agent mode supports the following interface features:
 
 - Chat view toolbar: The Chat view toolbar is located in the top right corner of the Chat view. You can use the toolbar to manage the chat history, start a new chat, open the Chat view in another location, or hide the Chat view. Hover your mouse pointer over the toolbar button icons to see a description.
 
 - Chat response area: The Chat response area is the space below the Chat view toolbar where GitHub Copilot displays responses. Responses include code suggestions, explanations, interactive elements, and other information related to your prompt.
 
 - Attach Context button: The Attach Context button (paperclip icon) is located in the bottom section of the Chat view. You can use this button to attach files, selections, symbols, or other resources from your workspace as context for your chat prompt.
 
-- Ask Copilot: The Ask Copilot text box is where you enter your prompts. When you're using ask mode, prompts can include chat participants, slash commands, and chat variables.
+- Ask Copilot: The Ask Copilot text box is where you enter your prompts. When you're using Ask agent mode, prompts can include chat participants, slash commands, and chat variables.
 
-    In ask mode, you can use chat participants to specify the context of your questions. For example, you can use `@workspace` to indicate that the context is your workspace files.
+    In Ask agent mode, you can use chat participants to specify the context of your questions. For example, you can use `@workspace` to indicate that the context is your workspace files.
 
 - Start Voice Chat button: The Start Voice Chat button is located to the left of the Ask Copilot textbox. You can use this button to enable or disable voice interactions with GitHub Copilot. When voice interactions are enabled, you can use your voice to ask GitHub Copilot questions.
 
@@ -81,11 +81,11 @@ The Quick Chat feature allows you to ask a quick question and get back into what
 
 To access the Quick Chat window, you can select **Quick Chat** from the GitHub Copilot menu, or use the **Ctrl+Shift+Alt+L** keyboard shortcut.
 
-The Quick Chat window supports the same context features provided by the Chat view in ask mode, but it doesn't provide a way to manage the chat history. The Quick Chat window is designed for quick questions and answers, so it doesn't include all of the features provided by the Chat view.
+The Quick Chat window supports the same context features provided by the Chat view in Ask agent mode, but it doesn't provide a way to manage the chat history. The Quick Chat window is designed for quick questions and answers, so it doesn't include all of the features provided by the Chat view.
 
 ![Screenshot showing the Quick Chat window.](../media/explain-quick-chat-explain-issue.png)
 
-You can use the Quick Chat for the same types of questions as the Chat view in ask mode. However, the Quick Chat is best suited for quick questions that aren't part of a larger conversation.
+You can use the Quick Chat for the same types of questions as the Chat view in Ask agent mode. However, the Quick Chat is best suited for quick questions that aren't part of a larger conversation.
 
 ## Summary
 

learn-pr/wwl-azure/implement-code-improvements-using-github-copilot-tools/includes/6-refactor-code-github-copilot-chat-modes.md

@@ -130,7 +130,7 @@ Consider the following criteria to choose between Plan and Agent:
 - Task complexity: The Agent is better suited for complex tasks that require both code edits and the invocation of tools or terminal commands.
 - Duration: The Agent uses multiple steps to process a request, so it might take longer to generate a response. For example, to determine the relevant context and files to edit, determine the plan of action, and more.
 - Self-healing: The Agent evaluates the outcome of the generated edits and might iterate multiple times to resolve intermediate issues.
-- Request quota: When using the Agent mode, depending on the complexity of the task, one prompt might result in many requests to the backend.
+- Request quota: When you're using the Agent mode, depending on the complexity of the task, one prompt might result in many requests to the backend.
 
 ## Summary