docs: fix Vale warnings from PRs merged in the last week (#6222)

* docs: fix Vale warnings from PRs merged in the last week

* docs: mirror Vale style fixes into es/fr/zh translations

---------

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>

Author: mintlify[bot]

advanced-support.mdx

@@ -65,13 +65,13 @@ Tiers 2 and 3 include the same response time targets. Mintlify will use commerci
 
 | Priority | Definition | Initial response | Target resolution |
 |---|---|---|---|
-| **P0 – Critical** | Complete service outage or security incident | 15 minutes | 1 hour |
-| **P1 – High** | Major functionality blocked with no available workaround | 1 hour | 3 hours |
-| **P2 – Medium** | Partial degradation or functionality issue with a workaround | 6 hours | 48 hours |
-| **P3 – Low** | Minor issues, cosmetic bugs, or general product inquiries | 12 hours | 96 hours |
+| **P0–Critical** | Complete service outage or security incident | 15 minutes | 1 hour |
+| **P1–High** | Major capability blocked with no available workaround | 1 hour | 3 hours |
+| **P2–Medium** | Partial degradation or feature issue with a workaround | 6 hours | 48 hours |
+| **P3–Low** | Minor issues, cosmetic bugs, or general product inquiries | 12 hours | 96 hours |
 
 <Note>
-**P0 is the only priority level with 24/7 response coverage.** P0 incidents (complete service outage or security incident) are managed directly by Mintlify engineering. We publish real-time status updates and incident progress at [status.mintlify.com](https://status.mintlify.com).
+**P0 is the only priority level with 24/7 response coverage.** Mintlify engineering manages P0 incidents (complete service outage or security incident) directly. We publish real-time status updates and incident progress at [status.mintlify.com](https://status.mintlify.com).
 
 **P1–P3 response times apply during Mintlify business hours only: 9 AM–5 PM PT, Monday–Friday, excluding US holidays.**
 </Note>
@@ -116,19 +116,19 @@ Tiers 2 and 3 include the same response time targets. Mintlify will use commerci
   </Accordion>
 
   <Accordion title="How does the AI routing work?">
-    When you send a message in your dedicated Slack channel, our AI tool detects whether it's a support-related issue and automatically routes it to our support inbox. This ensures your issues are captured and triaged without requiring manual intervention.
+    When you send a message in your dedicated Slack channel, our AI tool detects whether it's a support-related issue and automatically routes it to our support inbox. This ensures we capture and triage your issues without requiring manual intervention.
   </Accordion>
 </AccordionGroup>
 
 ### Coverage hours
 
 <AccordionGroup>
   <Accordion title="What counts as a P0 incident?">
-    A P0 is a complete service outage or security incident affecting your Mintlify deployment. P0 classification is determined by Mintlify. We monitor our systems continuously and proactively open P0 incidents when the criteria are met. Real-time status is always available at [status.mintlify.com](https://status.mintlify.com).
+    A P0 is a complete service outage or security incident affecting your Mintlify deployment. Mintlify determines P0 classification. We monitor our systems continuously and proactively open P0 incidents when our criteria match. Real-time status is always available at [status.mintlify.com](https://status.mintlify.com).
   </Accordion>
 
   <Accordion title="What are Mintlify business hours?">
-    P1–P3 response time targets apply during **9 AM–5 PM PT, Monday–Friday, excluding US public holidays.** P0 incidents are covered 24/7 and handled by Mintlify engineering.
+    P1–P3 response time targets apply during **9 AM–5 PM PT, Monday–Friday, excluding US public holidays.** Mintlify engineering covers and handles P0 incidents 24/7.
   </Accordion>
 </AccordionGroup>
 

agent/integrations.mdx

@@ -10,7 +10,7 @@ Agent integrations give the agent access to context from other tools that your t
 
 Integrations connect in one of two ways:
 
-- **Shared integrations** connect once for your entire organization. Anyone on the team can prompt the agent to use them. Slack, Notion, Linear, Jira, Confluence, Salesforce, Intercom, and Plain are shared.
+- **Shared integrations** connect once for your entire organization. Anyone on the team can prompt the agent to use them. Slack, Notion, Linear, Jira, Confluence, Salesforce, Intercom, and Plain all connect this way.
 - **Personal integrations** connect per user. Each teammate authorizes their own account, and the agent can only use a personal integration on behalf of the user who connected it. Google Calendar is personal.
 
 Personal integrations keep user-specific data, like calendar events, scoped to the user who connected the integration instead of shared across the organization.

ai/contextual-menu.mdx

@@ -29,7 +29,7 @@ The contextual menu includes several pre-built options that you can enable by ad
 | **Open in Grok** | `grok` | Creates a Grok conversation with the current page as context |
 | **Open in Google AI Studio** | `aistudio` | Creates a Google AI Studio conversation with the current page as context |
 | **Open in Devin** | `devin` | Creates a Devin session with the current page as context |
-| **Open in Devin Desktop** | `devin-desktop` | Opens Devin Desktop with the current page as context. Requires Devin Desktop to be installed. |
+| **Open in Devin Desktop** | `devin-desktop` | Opens Devin Desktop with the current page as context. Requires installing Devin Desktop. |
 | **Copy MCP server URL** | `mcp` | Copies your MCP server URL to the clipboard |
 | **Copy MCP install command** | `add-mcp` | Copies the `npx add-mcp` command to install the MCP server |
 | **Connect to Cursor** | `cursor` | Installs your hosted MCP server in Cursor |

api/analytics/assistant-conversations.mdx

@@ -23,4 +23,4 @@ Each conversation includes:
 - **sources**: Pages referenced in the response, with title and URL
 - **resolutionStatus**: Whether the assistant successfully answered the question. Either `answered` or `unanswered`. Use this field to track and analyze documentation gaps surfaced by user questions the assistant could not resolve.
 - **queryCategory**: Classification of the query type (if available)
-- **pageUrl**: Full URL of the documentation page where the conversation started, or `null` if no page path was captured. Use this field to attribute conversations to a specific page.
+- **pageUrl**: Full URL of the documentation page where the conversation started, or `null` if no page path is available. Use this field to attribute conversations to a specific page.

create/changelogs.mdx

@@ -64,7 +64,7 @@ Each `label` property for an `Update` automatically creates an entry in the righ
 
 Add `tags` to your `Update` components to replace the table of contents with tag filters. Users can filter the changelog by selecting one or more tags.
 
-When a user selects multiple tags, the changelog shows only updates that include every selected tag. Updates without any tags are hidden whenever a filter is active.
+When a user selects multiple tags, the changelog shows only updates that include every selected tag. The changelog hides updates without tags whenever a filter is active.
 
 ```mdx Tag filters example wrap
 <Update label="March 2025" description="v0.0.10" tags={["Wintergreen", "Spearmint"]}>

credits.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Credit pricing"
-description: "Understand how Mintlify credits work for assistant messages, agent runs, and workflows. How credit tiers, overages, and rollovers are billed."
+description: "Understand how Mintlify credits work for assistant messages, agent runs, and workflows, including how we bill credit tiers, overages, and rollovers."
 keywords: ["credits", "billing", "pricing", "AI chat", "messages", "tiers", "usage"]
 ---
 
@@ -25,17 +25,17 @@ For the most current pricing information, see the [Pricing page](https://mintlif
 
 If you need more than 108,500 credits per month, [contact sales](https://www.mintlify.com/contact/sales) to discuss a custom plan.
 
-**Overages** are charged per additional credit at $0.01 rather than triggering an automatic tier upgrade. You can set usage alerts to receive an email when you reach a certain percentage of your tier limit. Allowing overages can be cheaper than moving up a tier depending on your usage patterns.
+**Overages** cost an additional $0.01 per credit rather than triggering an automatic tier upgrade. You can set usage alerts to receive an email when you reach a certain percentage of your tier limit. Allowing overages can be cheaper than moving up a tier depending on your usage patterns.
 
 <Note>
-  Overages are disabled by default. You must enable them on the [Usage](https://app.mintlify.com/settings/organization/usage) page of your dashboard.
+  Overages default to off. You must enable them on the [Usage](https://app.mintlify.com/settings/organization/usage) page of your dashboard.
 </Note>
 
 **Rollovers** carry forward up to 50% of unused credits to the next month, so the maximum credits available in any month is 1.5 times your monthly limit. Rollovers reset if you change tiers.
 
 Higher tiers offer a lower effective cost per credit. If your usage consistently reaches the top of your current tier, upgrading is more economical than paying ongoing overage charges.
 
-Upgrades and downgrades take effect immediately and are prorated for the current billing cycle.
+Upgrades and downgrades take effect immediately, and we prorate the charges to the current billing cycle.
 
 For high-volume usage or custom credit packages, [contact sales](mailto:sales@mintlify.com). Custom credit packages are available on enterprise plans only.
 

editor/branching-and-publishing.mdx

@@ -124,7 +124,7 @@ After a reviewer approves a pull request, click **Merge and publish** to merge a
 
 ### Approve pull requests from the editor
 
-For GitHub repositories, reviewers can approve open pull requests in the editor. When a pull request is open, an **Approve pull request** button appears in the review panel if your account has permission to review it. Click **Approve pull request** when the changes are ready to be merged. The review status updates to **Approved** and the **Merge and publish** action becomes available.
+For GitHub repositories, reviewers can approve open pull requests in the editor. When a pull request is open, an **Approve pull request** button appears in the review panel if your account has permission to review it. Click **Approve pull request** when the changes are ready to merge. The review status updates to **Approved** and the **Merge and publish** action becomes available.
 
 The approve action is not available for draft pull requests, pull requests you have already approved, or GitLab merge requests. Click **Open in GitLab** to approve a merge request in GitLab.
 
@@ -134,7 +134,7 @@ The approve action is not available for draft pull requests, pull requests you h
 
 ### Review changes before merging
 
-Click any changed file in the publish menu to open it in diff view and compare your branch against the published version. In visual mode you see a visual diff; in source mode you see a text diff. Files that can't display a diff, such as images or deleted files, appear in the list but aren't clickable.
+Click any changed file in the publish menu to open it in diff view and compare your branch against the published version. In visual mode you see a visual diff. In source mode you see a text diff. Files that can't display a diff, such as images or deleted files, appear in the list but aren't clickable.
 
 ### Simultaneous publishing
 

editor/configurations.mdx

@@ -22,7 +22,7 @@ To open the panel, click the <Icon icon="sliders-horizontal" /> configurations i
   />
 </Frame>
 
-The panel is organized into sections that map to the top-level properties in your [`docs.json`](/organize/settings).
+The panel groups settings into sections that map to the top-level properties in your [`docs.json`](/organize/settings).
 
 ## General
 
@@ -189,7 +189,7 @@ Each entry renders as an inline row. Use the **X** icon to remove an integration
 
 Customize the experience when a user lands on a missing page.
 
-- **Redirect to home**: When on, missing pages redirect to your home page. When off, a 404 page is shown and you can customize the title and description below.
+- **Redirect to home**: When on, missing pages redirect to your home page. When off, the site shows a 404 page and you can customize the title and description below.
 - **Title**: Heading shown on the 404 page.
 - **Description**: Subheading shown on the 404 page.
 

editor/pages.mdx

@@ -22,7 +22,7 @@ Use the Files view to organize your content:
 - **Rename a file or folder**: Right-click the item and select **Rename**.
 - **Open unlisted files**: Click any file in the tree to open it, even if it isn't included in your navigation.
 
-Files that aren't in your navigation are unlisted. They exist in your repository but won't appear in the published sidebar.
+Files that aren't in your navigation remain unlisted. They exist in your repository but won't appear in the published sidebar.
 
 ## Create new pages
 

editor/tutorial.mdx

@@ -39,7 +39,7 @@ This tutorial walks you through a complete content update using the editor. You'
 
   </Step>
   <Step title="Publish your branch">
-    When you're ready for review, create a pull request from your branch. A pull request is a proposal to merge your changes into the branch that builds your live site. Your changes only go live if the pull request is approved and merged.
+    When you're ready for review, create a pull request from your branch. A pull request is a proposal to merge your changes into the branch that builds your live site. Your changes only go live after someone approves and merges the pull request.
 
     1. Click **Publish** in the toolbar to open the publish menu.
         <Frame>