acrolinx updates

Author: buzahid

learn-pr/wwl-data-ai/develop-multi-agent-azure-ai-foundry/5-knowledge-check.yml

@@ -22,18 +22,18 @@ quiz:
       explanation: "Correct. The main agent handles intent recognition and delegates work to connected agents."
     - content: "To monitor agent performance and generate logs"
       isCorrect: false
-      explanation: "Incorrect. Logging is not the role of the main agent."
+      explanation: "Incorrect. Logging isn't the role of the main agent."
   - content: "How do you connect an agent to a main agent using the Azure AI Projects client library?"
     choices:
     - content: "Add the agent as a `ConnectedAgentTool` to the main agent's tool definition."
       isCorrect: true
       explanation: "Correct. You register the agent as a tool and include it when configuring the main agent."
     - content: "Use the `link_agents()` method to bind the sub-agent to the main agent."
       isCorrect: false
-      explanation: "Incorrect. There is no such method; connected agents are registered as tools."
+      explanation: "Incorrect. There isn't such a method; connected agents are registered as tools."
     - content: "Set the main agent's parent_id to the sub-agent's agent ID."
       isCorrect: false
-      explanation: "Incorrect. Agent relationships are not configured through ID inheritance."
+      explanation: "Incorrect. Agent relationships aren't configured through ID inheritance."
   - content: "How does the main agent decide which connected agent to use?"
     choices:
     - content: "It uses prompt instructions and natural language understanding."

learn-pr/wwl-data-ai/develop-multi-agent-azure-ai-foundry/6-summary.yml

@@ -3,7 +3,7 @@ uid: learn.wwl.develop-multi-agent-azure-ai-foundry.summary
 title: Summary
 metadata:
   title: Summary
-  description: "Reflect on what you've learned about multi-agent systems."
+  description: "Reflect on what you learned about multi-agent systems."
   ms.date: 06/13/2025
   author: buzahid
   ms.author: buzahid

learn-pr/wwl-data-ai/develop-multi-agent-azure-ai-foundry/includes/1-introduction.md

@@ -2,4 +2,4 @@ Azure AI Foundry Agent Service can help you develop sophisticated, multi-agent s
 
 Imagine you're on an engineering team that receives a constant flow of support tickets including bugs, feature requests, and infrastructure issues. Manually reviewing and sorting each one takes time and slows down your team’s ability to respond quickly. With a multi-agent approach, you can build a triage assistant that assigns different tasks to specialized agents. The sub-agents might perform tasks such as classifying ticket type, setting priority, and suggesting the right team for the work. With a multi-agent approach, these specialized agents can work together to streamline the ticketing process.
 
-In this module, you'll learn how to use connected agents in Azure AI Foundry. You'll also practice building an intelligent ticket triage system using a collaborative mutli-agent solution.
+In this module, you learn how to use connected agents in Azure AI Foundry. You also practice building an intelligent ticket triage system using a collaborative mutli-agent solution.

learn-pr/wwl-data-ai/develop-multi-agent-azure-ai-foundry/includes/2-understand-connected-agents.md

@@ -2,9 +2,9 @@ As AI solutions become more advanced, managing complex workflows gets harder. A
 
 ## What are connected agents?
 
-Connected agents are a feature in the Azure AI Foundry Agent Service that allow you to break large tasks into smaller,specialized roles without building a custom orchestrator or hardcoding routing logic. Instead of relying on one agent to do everything, you can create multiple agents with clearly defined responsibilities that collaborate to accomplish tasks.
+Connected agents are a feature in the Azure AI Foundry Agent Service that allows you to break large tasks into smaller, specialized roles without building a custom orchestrator or hardcoding routing logic. Instead of relying on one agent to do everything, you can create multiple agents with clearly defined responsibilities that collaborate to accomplish tasks.
 
-At the center of this system is a main agent that interprets user input and delegates tasks to connected sub-agents. Each sub-agent is purpose-built to perform a specific function, such as summarizing a document, validating a policy, or retrieving data from a knowledge source.
+At the center of this system, there's a main agent that interprets user input and delegates tasks to connected sub-agents. Each sub-agent is designed to perform a specific function, such as to summarize a document, validate a policy, or retrieve data from a knowledge source.
 
 This division of labor helps you:
 

learn-pr/wwl-data-ai/develop-multi-agent-azure-ai-foundry/includes/3-design-multi-agent-solution.md

@@ -23,11 +23,11 @@ Connected agents should be designed with a single responsibility in mind. This m
 
 1. **Initialize the agents client**
 
-    First, you create a client that will connect to your Azure AI Foundry project.
+    First, you create a client that connects to your Azure AI Foundry project.
 
 1. **Create an agent to connect to the main agent**
 
-   Define an agent that will be connected to the main agent. You can do this using the `create_agent` method on the `AgentsClient` object. 
+   Define an agent you want to connect to the main agent. You can do this using the `create_agent` method on the `AgentsClient` object. 
 
    For example, your connected agent might retrieve stock prices, summarize documents, or validate compliance. Give the agent clear instructions that define its purpose.
 
@@ -41,7 +41,7 @@ Connected agents should be designed with a single responsibility in mind. This m
 
 1. **Create a thread and send a message**
 
-    Create the agent thread that will be used to manage the conversation context. Then create a message on the thread that contains the request you want the agent to fulfill.
+    Create the agent thread that is used to manage the conversation context. Then create a message on the thread that contains the request you want the agent to fulfill.
 
 1. **Run the agent workflow**