@mastra/mcp-docs-server 1.2.11 → 1.2.12-alpha.3

package/.docs/guides/getting-started/astro.md

@@ -74,7 +74,7 @@ export default defineConfig({
 })
 ```
 
-Lastly, edit the `tsconfig.json` to resolve paths:
+Edit the `tsconfig.json` to resolve paths:
 
 ```jsonc
 {

package/.docs/guides/getting-started/electron.md

@@ -432,7 +432,7 @@ This connects [`useChat()`](https://ai-sdk.dev/docs/reference/ai-sdk-ui/use-chat
 
 ## Test your agent
 
-In order to test your agent with the chat interface, you need to run both the Mastra server and the Electron app.
+To test your agent with the chat interface, run both the Mastra server and the Electron app.
 
 1. Start the mastra development server:
 

package/.docs/guides/getting-started/nestjs.md

@@ -199,11 +199,11 @@ export class AgentService {
 
 `MastraService` exposes:
 
-- `getMastra()` — returns the underlying `Mastra` instance
-- `getAgent(id)` — shorthand for `mastra.getAgent(id)`
-- `getWorkflow(id)` — shorthand for `mastra.getWorkflow(id)`
-- `getOptions()` — returns the module configuration
-- `isShuttingDown` — `true` after graceful shutdown begins
+- `getMastra()`: Returns the underlying `Mastra` instance
+- `getAgent(id)`: Shorthand for `mastra.getAgent(id)`
+- `getWorkflow(id)`: Shorthand for `mastra.getWorkflow(id)`
+- `getOptions()`: Returns the module configuration
+- `isShuttingDown`: `true` after graceful shutdown begins
 
 ### MASTRA token
 

package/.docs/guides/getting-started/vite-react.md

@@ -353,7 +353,7 @@ It renders the response text using the [`<MessageResponse>`](https://ai-sdk.dev/
 
 ## Test your agent
 
-In order to test your agent with the chat interface, you need to run both the Mastra server and the Vite development server.
+To test your agent with the chat interface, run both the Mastra server and the Vite development server.
 
 1. Start the Mastra development server:
 

package/.docs/guides/guide/ai-recruiter.md

@@ -49,7 +49,7 @@ Set up the Workflow, define steps to extract and classify candidate data, and th
      id: 'recruiter-agent',
      name: 'Recruiter Agent',
      instructions: `You are a recruiter.`,
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
    })
 
    const gatherCandidateInfo = createStep({

package/.docs/guides/guide/chef-michel.md

@@ -4,7 +4,7 @@
 
 In this guide, you'll create a "Chef Assistant" agent that helps users cook meals with available ingredients.
 
-You'll learn how to create the agent and register it with Mastra. Next, you'll interact with the agent through your terminal and get to know different response formats. Lastly, you'll access the agent through Mastra's local API endpoints.
+You'll learn how to create the agent and register it with Mastra. Next, you'll interact with the agent through your terminal and get to know different response formats. You'll then access the agent through Mastra's local API endpoints.
 
 ## Prerequisites
 
@@ -27,7 +27,7 @@ To create an agent in Mastra use the `Agent` class to define it and then registe
      instructions:
        'You are Michel, a practical and experienced home chef' +
        'You help people cook with whatever ingredients they have available.',
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
    })
    ```
 

package/.docs/guides/guide/code-review-bot.md

@@ -2,7 +2,7 @@
 
 # Building a code review bot
 
-In this guide, you'll build a code review bot that automatically reviews pull requests using workspace skills. The bot loads coding standards from skill files and provides structured feedback. You'll learn how to create a workspace with a skills directory, define an [Agent Skill](https://agentskills.io) with review instructions and reference files, and connect it to an agent that performs automated reviews.
+In this guide, you'll build a code review bot that automatically reviews pull requests using workspace skills. The bot loads coding standards from skill files and provides structured feedback. You'll create a workspace with a skills directory and define an [Agent Skill](https://agentskills.io) with review instructions and reference files. Then you'll connect the skill to an agent that performs automated reviews.
 
 ## Prerequisites
 
@@ -124,7 +124,7 @@ When asked to review code:
 2. Follow the review process from the skill
 3. Check against the style guide in skill references
 4. Be constructive and specific with line numbers`,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
 })
 ```
 

package/.docs/guides/guide/coding-agent.md

@@ -55,7 +55,7 @@ import { basename } from 'node:path'
 import { buildBasePrompt, createCodingAgent } from '@mastra/core/coding-agent'
 
 export const projectPath = process.cwd()
-const model = 'openai/gpt-5.5'
+const model = 'openai/gpt-5.6-sol'
 
 const instructions = buildBasePrompt({
   projectPath,
@@ -146,7 +146,7 @@ Open [Studio](https://mastra.ai/docs/studio/overview), select **Coding Agent**,
 Inspect project-notes.md and report the project name, status, and owner. Do not modify files.
 ```
 
-The response should identify the Acme support portal, its development status, and the Platform team without changing the file. Model wording may vary.
+The response should identify the Acme support portal and describe its development status. It should report that the Platform team owns the project and leave the file unchanged. Model wording may vary.
 
 ## Create the agent controller
 
@@ -191,13 +191,13 @@ export async function createCodingAgentSession() {
 }
 ```
 
-This example uses one mode and disables the controller's additional built-in tools so the introductory UI can focus on workspace execution. This is a tutorial simplification, not a production recommendation. In a production application, enable the built-in tools your product needs and implement their UI flows: interactive tools such as `ask_user` and `submit_plan` suspend until your interface resumes them, while task and subagent tools have their own lifecycle events. See [tool approvals and suspensions](https://mastra.ai/docs/agent-controller/tool-approvals).
+This example uses one mode and disables the controller's additional built-in tools so the introductory UI can focus on workspace execution. The simplified setup is intended for this tutorial. In a production application, enable the built-in tools your product needs and implement their UI flows: interactive tools such as `ask_user` and `submit_plan` suspend until your interface resumes them, while task and subagent tools have their own lifecycle events. See [tool approvals and suspensions](https://mastra.ai/docs/agent-controller/tool-approvals).
 
 The example also omits storage, so the conversation lasts only for the current process. You can add storage later when you want to resume sessions.
 
 ## Build the terminal UI
 
-Create `src/coding-agent-tui.ts`. The UI renders assistant message updates, shows tool activity, and asks the user to approve or decline each workspace tool call.
+Create `src/coding-agent-tui.ts`. The UI renders assistant message updates and shows tool activity. It also asks the user to approve or decline each workspace tool call.
 
 ```typescript
 import { pathToFileURL } from 'node:url'
@@ -334,7 +334,7 @@ if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href)
 }
 ```
 
-The optional `Terminal` parameter supports automated tests while using `ProcessTerminal` during normal execution. The UI intentionally renders only the latest response; the `Session` still maintains the conversation context for follow-up prompts.
+The optional `Terminal` parameter supports automated tests while using `ProcessTerminal` during normal execution. The UI intentionally renders only the latest response. The `Session` still maintains the conversation context for follow-up prompts.
 
 ## Run the coding agent
 

package/.docs/guides/guide/dev-assistant.md

@@ -9,7 +9,7 @@ In this guide, you'll build a complete development assistant that combines all w
 - [Skills](https://mastra.ai/docs/workspace/skills) for coding standards
 - [Search](https://mastra.ai/docs/workspace/search) for finding examples
 
-You'll set up a workspace with a sample project, add coding standards as a skill, and create an agent that writes code following TDD practices. By the end, you'll have an agent that can read existing code, write new implementations, run tests in a sandbox, and iterate based on results.
+You'll set up a workspace with a sample project and add coding standards as a skill. Then you'll create an agent that writes code following TDD practices. By the end, the agent can read existing code and write new implementations, then run tests in a sandbox and iterate based on the results.
 
 ## Prerequisites
 
@@ -197,7 +197,7 @@ When adding features:
 For every new feature: Write code → Write tests → Run tests → Update docs
 
 Always explain your reasoning and steps.`,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
 })
 ```
 

package/.docs/guides/guide/docs-manager.md

@@ -2,7 +2,7 @@
 
 # Building a docs manager
 
-In this guide, you'll build a documentation manager that maintains your project's docs. It creates well-structured markdown files, keeps documentation organized, and prevents accidental overwrites. You'll learn how to set up a workspace filesystem, create an agent with document management instructions, and use it to generate and update documentation through conversational prompts.
+In this guide, you'll build a documentation manager that maintains your project's docs. It creates well-structured markdown files and keeps documentation organized while preventing accidental overwrites. You'll set up a workspace filesystem and create an agent with document management instructions. Then you'll use conversational prompts to generate and update documentation.
 
 ## Prerequisites
 
@@ -40,7 +40,7 @@ Inside the `workspace` directory, create the following folders:
 - `docs/api/`: For API reference documentation
 - `docs/tutorials/`: For step-by-step tutorials
 
-Create a `workspace/docs/README.md` file that serves as the documentation index:
+Create `workspace/docs/README.md` as the documentation index:
 
 ```markdown
 # Project Documentation
@@ -105,7 +105,7 @@ When updating existing docs:
 
 Use kebab-case naming for files (getting-started.md).
 Always explain what you're creating and why.`,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
 })
 ```
 
@@ -217,7 +217,7 @@ Try updating an existing document:
 Update the getting started guide to include a section on configuration after the Quick Example
 ```
 
-The agent should read the existing `getting-started.md` file, find the right insertion point, and add the new section without disrupting existing content.
+The agent should read the existing `getting-started.md` file and find the right insertion point. It should add the new section without disrupting existing content.
 
 ### Organize documentation
 

package/.docs/guides/guide/firecrawl.md

@@ -109,7 +109,7 @@ Create a tool file that exposes Firecrawl search and scrape to Mastra.
      id: 'web-agent',
      name: 'Web Agent',
      instructions: 'Use Firecrawl tools to search and scrape web pages, then summarize the results.',
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
      tools: { firecrawlSearch, firecrawlScrape },
    })
    ```

package/.docs/guides/guide/github-actions-pr-description.md

@@ -99,7 +99,7 @@ Output format:
 
 - [Same changes in Japanese]
 `,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
 })
 ```
 
@@ -121,11 +121,11 @@ The agent will return a formatted description with sections in English, Spanish,
 
 ## GitHub actions
 
-GitHub Actions run your workflows in short-lived environments on GitHub's infrastructure. Each run starts with a clean virtual machine, checks out your code, installs dependencies, runs your workflow steps, and then shuts down. Nothing persists between runs unless you explicitly save it as an artifact or cache.
+GitHub Actions run your workflows in short-lived environments on GitHub's infrastructure. Each run starts with a clean virtual machine and checks out your code. It installs dependencies before running your workflow steps. The environment shuts down when the run completes. Nothing persists between runs unless you explicitly save it as an artifact or cache.
 
 ### Create the workflow
 
-GitHub Actions workflows live in the `.github/workflows` directory. Create a `.github` directory at the root of your project, then create a `workflows` directory inside it. Add a file named `pr-description.yml`.
+GitHub Actions workflows live in the `.github/workflows` directory. Create a `.github` directory at the root of your project, then create a `workflows` directory inside it. Add `pr-description.yml`.
 
 This workflow runs whenever a pull request is opened or updated. It generates a diff for the PR, calls the Mastra agent to describe the changes, and writes the description directly into the PR in the GitHub UI.
 
@@ -187,7 +187,7 @@ jobs:
 
 ### Create the workflow script
 
-Create a `scripts` directory inside `.github` and add a file named `generate-description.ts`.
+Create a `scripts` directory inside `.github` and add `generate-description.ts`.
 
 This script reads the PR diff from `PR_DIFF_FILE`, generates a description using the Mastra agent, and writes the result to `PR_DESCRIPTION_FILE` for the workflow to publish to the pull request.
 
@@ -229,7 +229,7 @@ ${readFileSync(process.env.PR_DIFF_FILE!, 'utf-8')}
 
 You now have a GitHub Action that generates multi-language PR descriptions using a Mastra agent. Once the workflow and supporting files are merged into your main branch, the agent will run automatically the next time a pull request is created or updated. You can monitor the run in the **Actions** tab of your repository.
 
-From here, you can customize the agent instructions, change the output languages, or extend the workflow to handle other events.
+From here, customize the agent instructions or change the output languages. You can also extend the workflow to handle other events.
 
 To learn more:
 

package/.docs/guides/guide/research-assistant.md

@@ -4,7 +4,7 @@
 
 In this guide, you'll create an AI research assistant that can analyze academic papers and answer specific questions about their content using Retrieval Augmented Generation (RAG).
 
-You'll use the foundational Transformer paper ["Attention Is All You Need"](https://arxiv.org/html/1706.03762) as your example. As a database you'll use a local libSQL database.
+You'll use the original Transformer paper ["Attention Is All You Need"](https://arxiv.org/html/1706.03762) as your example. As a database you'll use a local libSQL database.
 
 ## Prerequisites
 
@@ -101,7 +101,7 @@ Let's define the agent's behavior, connect it to your Mastra project, and create
        and provide accurate, well-supported answers based on the retrieved content.
        Focus on the specific content available in the tool and acknowledge if you cannot find sufficient information to answer a question.
        Base your responses only on the content provided, not on general knowledge.`,
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
      tools: {
        vectorQueryTool,
      },
@@ -155,7 +155,7 @@ Let's define the agent's behavior, connect it to your Mastra project, and create
 
 ## Processing documents
 
-In the following steps you'll fetch the research paper, split it into smaller chunks, generate embeddings for them, and store these chunks of information into the vector database.
+In the following steps, you'll fetch the research paper and split it into smaller chunks. You'll then generate embeddings and store the chunks in the vector database.
 
 1. In this step the research paper is retrieved by providing an URL, then converted to a document object, and split into smaller, manageable chunks. By splitting into chunks the processing is faster and more efficient.
 
@@ -201,7 +201,7 @@ In the following steps you'll fetch the research paper, split it into smaller ch
 
    > **Note:** This metadata is crucial as it allows for returning the actual content when the vector store finds relevant matches.
 
-   This allows the agent to efficiently search and retrieve relevant information.
+   The agent uses the vector index to search for and retrieve relevant information.
 
    Open the `src/store.ts` file and add the following:
 

package/.docs/guides/guide/research-coordinator.md

@@ -2,9 +2,9 @@
 
 # Build a research coordinator with supervisor agents
 
-In this guide, you'll build a research coordinator that orchestrates multiple specialized agents using supervisor agents. The coordinator will delegate research tasks to a research agent and writing tasks to a writing agent, then synthesize the results into a comprehensive report.
+In this guide, you'll build a research coordinator that orchestrates multiple specialized agents using supervisor agents. The coordinator will delegate research tasks to a research agent and writing tasks to a writing agent, then synthesize the results into a detailed report.
 
-You'll learn how to set up subagents with clear roles, configure a supervisor agent to coordinate them, use delegation hooks to control execution, and validate task completion with scorers.
+You'll set up subagents with clear roles and configure a supervisor agent to coordinate them. You'll also use delegation hooks to control execution and scorers to validate task completion.
 
 ## Prerequisites
 
@@ -96,7 +96,7 @@ Success criteria:
 - Information is accurate and well-sourced
 - Final output is well-formatted and complete
 - If anything is missing or uncertain, continue gathering information`,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   agents: {
     researchAgent,
     writingAgent,
@@ -172,7 +172,7 @@ export const mastra = new Mastra({
 The `defaultOptions` on the supervisor agent configure delegation hooks and iteration monitoring:
 
 - `onDelegationStart` modifies the research agent's prompt to request recent data
-- `onDelegationComplete` logs completion, bails on errors, and provides feedback
+- `onDelegationComplete` logs completion and stops on errors, then provides feedback
 - `messageFilter` limits context to the last 10 messages for efficiency
 - `onIterationComplete` monitors progress after each iteration
 
@@ -290,7 +290,7 @@ Success criteria:
 - Information is accurate and well-sourced
 - Final output is well-formatted and complete
 - If anything is missing or uncertain, continue gathering information`,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   agents: {
     researchAgent,
     writingAgent,

package/.docs/guides/guide/signal-provider.md

@@ -119,7 +119,7 @@ export const devAgent = new Agent({
   id: 'dev-agent',
   name: 'Dev Agent',
   instructions: 'Help the user triage CI build failures.',
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   signals: [ciSignals],
 })
 ```

package/.docs/guides/guide/slack-assistant.md

@@ -160,7 +160,7 @@ Select **Save Changes**. Slack requires you to reinstall the app after changing
 
 ## Test the agent
 
-Before testing with Slack, you can refine your agent's behavior in [Studio](https://mastra.ai/docs/studio/overview). Open <http://localhost:4111/> to chat with your agent directly, adjust its instructions, and inspect traces to see how responses are generated.
+Before testing with Slack, you can refine your agent's behavior in [Studio](https://mastra.ai/docs/studio/overview). Open <http://localhost:4111/> to chat with your agent and adjust its instructions. Inspect traces to see how responses are generated.
 
 Once you're happy with the agent's responses, test the Slack integration. Invite the bot to a channel in Slack:
 

package/.docs/guides/guide/stock-agent.md

@@ -2,7 +2,7 @@
 
 # Building an AI stock agent
 
-In this guide, you're going to create an agent that fetches the last day's closing stock price for a given symbol. You'll learn how to create a tool, add it to an agent, and use the agent to fetch stock prices.
+In this guide, you'll create an agent that fetches the previous day's closing stock price for a symbol. You'll create a tool and add it to an agent, then use the agent to fetch stock prices.
 
 ## Prerequisites
 
@@ -24,7 +24,7 @@ To create an agent in Mastra use the `Agent` class to define it and then registe
      name: 'Stock Agent',
      instructions:
        'You are a helpful assistant that provides current stock prices. When asked about a stock, use the stock price tool to fetch the stock price.',
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
    })
    ```
 
@@ -83,7 +83,7 @@ The Stock Agent doesn't yet know anything about current stock prices. To change
      name: 'Stock Agent',
      instructions:
        'You are a helpful assistant that provides current stock prices. When asked about a stock, use the stock price tool to fetch the stock price.',
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
      tools: {
        stockPrices,
      },

package/.docs/guides/guide/web-search.md

@@ -130,7 +130,7 @@ Some LLM providers include built-in web search capabilities that can be used dir
      id: 'search-agent',
      name: 'Search Agent',
      instructions: 'You are a search agent that can search the web for information.',
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
    })
    ```
 
@@ -159,7 +159,7 @@ Some LLM providers include built-in web search capabilities that can be used dir
      id: 'search-agent',
      name: 'Search Agent',
      instructions: 'You are a search agent that can search the web for information.',
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
      tools: {
        webSearch: openai.tools.webSearch(),
      },
@@ -243,7 +243,7 @@ For more control over search behavior, you can integrate external search APIs as
      id: 'search-agent',
      name: 'Search Agent',
      instructions: 'You are a search agent that can search the web for information.',
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
    })
    ```
 
@@ -295,7 +295,7 @@ For more control over search behavior, you can integrate external search APIs as
      id: 'search-agent',
      name: 'Search Agent',
      instructions: 'You are a search agent that can search the web for information.',
-     model: 'openai/gpt-5.5',
+     model: 'openai/gpt-5.6-sol',
      tools: {
        webSearch,
      },

package/.docs/guides/guide/whatsapp-chat-bot.md

@@ -119,7 +119,7 @@ export const chatAgent = new Agent({
 
     Always aim to be helpful while maintaining a friendly, approachable conversation style.
   `,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   memory: new Memory({
     storage: new LibSQLStore({
       id: 'agent-storage',
@@ -157,7 +157,7 @@ export const textMessageAgent = new Agent({
 
     Always return exactly 5-8 messages in the messages array.
   `,
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   memory: new Memory({
     storage: new LibSQLStore({
       id: 'agent-storage',

package/.docs/guides/index.md

@@ -2,7 +2,7 @@
 
 # Mastra Guides
 
-Mastra offers a variety of guides to help you build and work with Mastra, from building agents and workflows to using the Mastra SDK and API, and implementing different UI frameworks. Explore the guides below to find the resources you need to get started and build with Mastra.
+Mastra offers guides for building agents and workflows, using the Mastra SDK and API, and implementing different UI frameworks. Explore these guides to find the resources you need to get started and build with Mastra.
 
 ## New project
 

package/.docs/guides/migrations/agentnetwork.md

@@ -29,7 +29,7 @@ const agent = new AgentNetwork({
   name: 'agent-network',
   agents: [agent1, agent2],
   tools: { tool1, tool2 },
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   instructions: 'You are a network agent that can help users with a variety of tasks.',
 })
 
@@ -49,7 +49,7 @@ const agent = new Agent({
   name: 'agent-network',
   agents: { agent1, agent2 },
   tools: { tool1, tool2 },
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   instructions: 'You are a network agent that can help users with a variety of tasks.',
   memory,
 })
@@ -70,7 +70,7 @@ const agent = new NewAgentNetwork({
   agents: { agent1, agent2 },
   workflows: { workflow1 },
   tools: { tool1, tool2 },
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   instructions: 'You are a network agent that can help users with a variety of tasks.',
 })
 
@@ -91,7 +91,7 @@ const agent = new Agent({
   agents: { agent1, agent2 },
   workflows: { workflow1 },
   tools: { tool1, tool2 },
-  model: 'openai/gpt-5.5',
+  model: 'openai/gpt-5.6-sol',
   instructions: 'You are a network agent that can help users with a variety of tasks.',
   memory,
 })

package/.docs/guides/migrations/ai-sdk-v4-to-v5.md

@@ -13,7 +13,7 @@ This guide covers only the Mastra-specific aspects of the migration.
 
 ## Memory and storage
 
-Mastra automatically handles AI SDK v4 data using its internal `MessageList` class, which manages format conversion—including v4 to v5. No database migrations are required; your existing messages are translated on the fly and continue working after you upgrade.
+Mastra automatically handles AI SDK v4 data using its internal `MessageList` class, which manages format conversion, including v4 to v5. No database migrations are required. Your existing messages are translated on the fly and continue working after you upgrade.
 
 ## Message format conversion
 

package/.docs/guides/migrations/mastra-cloud.md

@@ -60,7 +60,7 @@ The Mastra platform replaces Mastra Cloud with separate Studio and Server produc
 
 Mastra Cloud provided a managed libSQL database, backed by [Turso](https://turso.tech). The Mastra platform doesn't host a database for you, so you need to point your storage at an externally hosted instance.
 
-If you were already using a hosted database ("bring your own"), no changes are needed. Ensure the connection string is set as an environment variable in the dashboard rather than hardcoded.
+If you were already using a hosted database ("bring your own"), keep the existing database configuration. Ensure the connection string is set as an environment variable in the dashboard rather than hardcoded.
 
 If you were using Cloud Store, follow the steps below to export your data and load it into a new libSQL database that you control.
 
@@ -68,7 +68,7 @@ If you were using Cloud Store, follow the steps below to export your data and lo
 
 You can export your Cloud Store data in two ways: download it from the dashboard, or create a manual dump with the Turso CLI.
 
-#### Option A — Export from the dashboard (recommended)
+#### Option A: Export from the dashboard (recommended)
 
 Open your project in the [Mastra dashboard](https://projects.mastra.ai) and navigate to **Runtime → Settings → Storage**. Click the **Export Database** button. The dashboard generates a full `.sql` dump of your Cloud Store and downloads it directly to your Downloads folder.
 
@@ -80,7 +80,7 @@ sqlite3 mydb.db < ~/Downloads/mastra-cloud-dump.sql
 
 You now have a portable `mydb.db` file you can inspect locally, back up, or use as the source for the new database in the steps that follow.
 
-#### Option B — Export via the Turso CLI
+#### Option B: Export via the Turso CLI
 
 If you prefer to work from the command line, or need to script the export, you can dump the database directly using the [Turso CLI](https://docs.turso.tech/cli). This approach requires the database URL and an auth token, both surfaced in the dashboard.
 
@@ -269,7 +269,7 @@ Deploy your hosted Studio instance:
 mastra studio deploy
 ```
 
-The CLI builds your project, uploads the artifact, and deploys it. On first deploy, a `.mastra-project.json` file is created to link your local project to the platform. Commit this file to your repository.
+The CLI builds your project and uploads the artifact before deploying it. On first deploy, a `.mastra-project.json` file is created to link your local project to the platform. Commit this file to your repository.
 
 A local env file is optional. When a `.env` or `.env.*` file is present in the project directory, the deploy bundles its environment variables.
 
@@ -283,14 +283,14 @@ See [Studio deployment](https://mastra.ai/docs/studio/deployment) for details.
 
 ### Multiple environments
 
-A single Mastra platform project runs the same codebase across multiple named [environments](https://mastra.ai/docs/mastra-platform/environments), such as `production` and `staging`. Deploy to each with the unified [`mastra deploy`](https://mastra.ai/docs/mastra-platform/deploy) command:
+A single Mastra platform project runs the same codebase across multiple [environments](https://mastra.ai/docs/mastra-platform/environments), such as `production` and `staging`. Deploy to each with the unified [`mastra deploy`](https://mastra.ai/docs/mastra-platform/deploy) command:
 
 ```bash
 mastra deploy --env production --yes
 mastra deploy --env staging --env-file .env.staging --yes
 ```
 
-Each environment gets its own URL, its own environment variables, and its own deploy history.
+Each environment has a dedicated URL and environment variables, along with a separate deploy history.
 
 ## Deploy Server (optional)
 

package/.docs/guides/migrations/network-to-supervisor.md

@@ -4,11 +4,11 @@
 
 Supervisor agents using `Agent.stream()` and `Agent.generate()` are the recommended approach for coordinating multiple agents, replacing the older `.network()` API. This guide walks you through each step of the migration.
 
-> **.network() Deprecation:** `.network()` is deprecated and will be removed in a future release. While existing code will continue to work until then, no new features will be added to it. Migrate to supervisor agents as soon as possible.
+> **.network() Deprecation:** `.network()` is deprecated and will be removed in a future release. Existing code will continue to work until then, but development now focuses on supervisor agents. Migrate to supervisor agents as soon as possible.
 
 ## Replace `.network()` with `.stream()` or `.generate()`
 
-The core change is replacing `.network()` calls with `.stream()` (for streaming) or `.generate()` (for non-streaming). The agent configuration stays the same -- you still define `agents`, `workflows`, `tools`, and `memory` on the agent. The difference is how you call it and how you process the results.
+The core change is replacing `.network()` calls with `.stream()` (for streaming) or `.generate()` (for non-streaming). The agent configuration stays the same. You still define `agents`, `workflows`, `tools`, and `memory` on the agent. The difference is how you call it and how you process the results.
 
 With `.network()`, you iterated over custom event types like `network-execution-event-step-finish`. With `.stream()`, you use the standard `textStream` or `fullStream` iterators.
 
@@ -50,9 +50,9 @@ console.log(result.text)
 
 ## Write clear supervisor instructions
 
-With `.network()`, the routing agent relied on generic instructions and primitive descriptions to decide what to call. Supervisor agents work the same way, but clear and specific instructions significantly improve delegation accuracy.
+With `.network()`, the routing agent relied on generic instructions and primitive descriptions to decide what to call. Supervisor agents work the same way, but clear and specific instructions improve delegation accuracy.
 
-Your supervisor's `instructions` should specify what resources are available, when to use each one, how to coordinate them, and when the task is complete.
+Your supervisor's `instructions` should identify the available resources and when to use each one. They should also explain how to coordinate those resources and recognize when the task is complete.
 
 **Before:**
 
@@ -92,7 +92,7 @@ Success criteria:
 
 ## Add descriptions to subagents
 
-Each subagent should have a `description` field that explains what it does, what format it returns, and when it should be used. The supervisor uses these descriptions to decide which agent to delegate to.
+Each subagent should have a `description` field that explains its purpose and return format. The description should also state when to use the subagent. The supervisor uses these descriptions to decide which agent to delegate to.
 
 ```typescript
 const researchAgent = new Agent({
@@ -129,7 +129,7 @@ If you were handling specific `.network()` events, update them to use the standa
 
 Supervisor agents let you hook into the delegation lifecycle to monitor, modify, or reject delegations. These hooks can be configured in the agent's `defaultOptions` or passed per-call.
 
-`onDelegationStart` is called before the supervisor delegates to a subagent. You can modify the prompt, limit the subagent's steps, or reject the delegation entirely:
+`onDelegationStart` is called before the supervisor delegates to a subagent. You can modify the prompt or limit the subagent's steps. The hook can also reject the delegation entirely:
 
 ```typescript
 const stream = await supervisorAgent.stream('Research AI in education', {
@@ -159,7 +159,7 @@ const stream = await supervisorAgent.stream('Research AI in education', {
 })
 ```
 
-`onDelegationComplete` is called after a delegation finishes. You can inspect the result, call `context.bail()` to stop the supervisor loop, and return feedback that gets saved to the supervisor's memory:
+`onDelegationComplete` is called after a delegation finishes. Inspect the result and call `context.bail()` when the supervisor loop should stop. You can also return feedback that gets saved to the supervisor's memory:
 
 ```typescript
 const stream = await supervisorAgent.stream('Research AI in education', {
@@ -179,7 +179,7 @@ const stream = await supervisorAgent.stream('Research AI in education', {
 
 ## Add message filtering
 
-By default, subagents receive the full conversation context from the supervisor. Use `messageFilter` to control what messages are shared -- for example, to remove sensitive data or limit the number of messages:
+By default, subagents receive the full conversation context from the supervisor. Use `messageFilter` to control what messages are shared. For example, remove sensitive data or limit the number of messages:
 
 ```typescript
 const stream = await supervisorAgent.stream('Research AI in education', {
@@ -200,7 +200,7 @@ const stream = await supervisorAgent.stream('Research AI in education', {
 
 ## Add iteration monitoring
 
-`onIterationComplete` is called after each iteration of the supervisor loop. You can use it to log progress, provide feedback to guide the agent, or stop execution early:
+`onIterationComplete` is called after each iteration of the supervisor loop. Use it to log progress or provide feedback that guides the agent. The hook can also stop execution early:
 
 ```typescript
 const stream = await supervisorAgent.stream('Research AI in education', {