mintlify · ethanpalm · Jun 18, 2026 · Jun 18, 2026 · Jun 18, 2026
diff --git a/advanced-support.mdx b/advanced-support.mdx
@@ -11,7 +11,7 @@
 | | Standard | Advanced Slack | Dedicated CSM |
 |---|---|---|---|
 | **Tier** | 1 (included) | 2 (add-on) | 3 (add-on) |
 | **How issues reach us** | Email or dashboard | AI routing from Slack | CSM escalates from Slack |
 | **Response time targets** | Best effort | P0–P3 | P0–P3 |
 | **Named contact** | No | No | Yes |
 | **Monthly check-ins** | No | No | Yes |
@@ -61,17 +61,17 @@

 ### Response time targets

 Tiers 2 and 3 include the same response time targets. Mintlify will use commercially reasonable efforts to meet the following service levels:
 
 | 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>
@@ -100,7 +100,7 @@
  </Accordion>

  <Accordion title="How does feature request tracking work?">
    Every Tier 3 customer gets a shared tracker where you can submit feature requests with context and priority, see status updates as requests move through review and development, and provide feedback as features are scoped. Your CSM reviews this regularly and escalates priority items directly to our product team.
  </Accordion>
 </AccordionGroup>

@@ -116,19 +116,19 @@
   </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>
 

diff --git a/agent/integrations.mdx b/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.

diff --git a/ai/contextual-menu.mdx b/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 |

diff --git a/api/analytics/assistant-conversations.mdx b/api/analytics/assistant-conversations.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Get assistant conversations"
 openapi: /analytics.openapi.json GET /v1/analytics/{projectId}/assistant
 keywords: ["analytics", "assistant", "conversations", "export", "AI"]

 ---
@@ -21,6 +21,6 @@
 - **query**: The user's question
 - **response**: The assistant's answer
 - **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.
diff --git a/create/changelogs.mdx b/create/changelogs.mdx
@@ -64,7 +64,7 @@
 
 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"]}>
@@ -101,7 +101,7 @@
  Using `custom`, `center`, or `wide` page modes hides the table of contents and changelog filters. Learn more about [page modes](/organize/pages#page-mode).
 </Tip> 

 ### Subscribable changelogs

 <Note>RSS feeds are only available on public documentation.</Note>


diff --git a/credits.mdx b/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.
 

diff --git a/editor/branching-and-publishing.mdx b/editor/branching-and-publishing.mdx
@@ -124,7 +124,7 @@
 
 ### 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 @@
 
 ### 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
 
@@ -152,13 +152,13 @@

 ## Collaborate in real time

 When multiple people open the same page on the same branch, they edit together in real time. Each person's cursor and edits are visible to everyone, with avatars shown in the toolbar.

 - Changes from all collaborators merge automatically. Two people editing the same section won't create conflicts.
 - Undo only affects your own edits.
 - If you lose your connection, edits save locally and sync when you reconnect.

 When the [Mintlify agent](/agent) edits a page through the API or MCP, it appears in the editor like any other collaborator. You see the agent's avatar in the toolbar and a live cursor at its most recent edit location. The cursor clears automatically after the agent finishes.

 ## Git sync


diff --git a/editor/configurations.mdx b/editor/configurations.mdx
@@ -22,7 +22,7 @@
   />
 </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
 
@@ -81,7 +81,7 @@
 Display an announcement bar across the top of every page.

 - **Content**: The banner text. Supports basic MDX formatting like links, bold, and italic. Custom components are not supported.
 - **Dismissible**: Show a dismiss button on the right side of the banner.
 - **Type**: Visual style. `info` uses the primary brand color, `warning` uses an amber background, and `critical` uses a red background. Defaults to `info`.
 - **Color**: Override the banner background color with a custom hex color. Set separate light and dark values for theme-aware colors.

@@ -119,7 +119,7 @@

 Tune navigation behavior across your site.

 - **Drilldown**: Auto-navigate to the first page when a user clicks a navigation group.

 ## Search

@@ -176,7 +176,7 @@

 Configure metatags and indexing for search engines.

 - **Metatags**: Custom `<meta>` tags applied across your site. Add key-value pairs for tags like `og:image` or `twitter:card`.
 - **Indexing**: Choose whether to index hidden pages.

 ## Analytics
@@ -189,7 +189,7 @@
 
 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.
 

diff --git a/editor/pages.mdx b/editor/pages.mdx
@@ -22,7 +22,7 @@
 - **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
 
@@ -48,13 +48,13 @@
 - **Link to another page**: Right-click a page in the navigation tree, click **Copy link**, then paste the link into your content. The editor recognizes internal links to other pages and converts them.
 - **Insert media from your project**: Drag an image or video from the navigation tree into the page to embed it inline. Supported formats include PNG, JPG, JPEG, GIF, WebP, SVG, MP4, and WebM.
 - **Insert an emoji**: Type <kbd>:</kbd> followed by a keyword to open the emoji picker.
 - **Edit a table**: When your cursor is inside a table, use the floating toolbar to add or remove rows and columns, or merge cells.

 **Source mode** gives you direct access to the MDX source. Use it for precise control over component properties and frontmatter.

 For a full list of components, see [Components](/components). For MDX syntax, see [Format text](/create/text) and [Format code](/create/code).

 ### Diff view

 To compare your current page against the last published version, click the <Icon icon="file-diff" /> **View diff** button in the toolbar, or press <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>D</kbd> (macOS) or <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>D</kbd> (Windows). In visual mode this shows a visual diff. In source mode it shows a text diff. Click **Exit diff** or press the shortcut again to return to editing.

@@ -101,7 +101,7 @@

 Hover over a page and click the gear icon, or right-click and select **Settings**, to configure:

 - **Title**, **Slug**, and **Sidebar title**: Control how the page appears in navigation and its URL.
 - **Description** and **Keywords**: Improve search and SEO.
 - **Layout**: Choose from standard, wide, centered, or custom.

@@ -113,7 +113,7 @@

 Type <kbd>/image</kbd> to upload a new image or select an existing one from your repository. Type <kbd>/video</kbd> to upload or select a video.

 You can also drag and drop files from your computer directly onto a page. In visual mode, the file inserts inline. In source mode, the editor inserts the file path at your cursor position. Images save to your `images/` folder and videos to `videos/`.

 To reuse media that already lives in your project, drag an image or video file from the navigation tree onto the page. The editor embeds the asset inline.


diff --git a/editor/tutorial.mdx b/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>

diff --git a/es/advanced-support.mdx b/es/advanced-support.mdx
@@ -77,13 +77,13 @@ Los niveles 2 y 3 incluyen los mismos objetivos de tiempo de respuesta. Mintlify
 
 | Prioridad | Definición | Respuesta inicial | Resolución objetivo |
 |---|---|---|---|
-| **P0 – Crítico** | Interrupción completa del servicio o incidente de seguridad | 15 minutos | 1 hora |
-| **P1 – Alto** | Funcionalidad principal bloqueada sin solución alternativa disponible | 1 hora | 3 horas |
-| **P2 – Medio** | Degradación parcial o problema de funcionalidad con solución alternativa | 6 horas | 48 horas |
-| **P3 – Bajo** | Problemas menores, errores cosméticos o consultas generales sobre el producto | 12 horas | 96 horas |
+| **P0–Crítico** | Interrupción completa del servicio o incidente de seguridad | 15 minutos | 1 hora |
+| **P1–Alto** | Capacidad importante bloqueada sin solución alternativa disponible | 1 hora | 3 horas |
+| **P2–Medio** | Degradación parcial o problema de característica con solución alternativa | 6 horas | 48 horas |
+| **P3–Bajo** | Problemas menores, errores cosméticos o consultas generales sobre el producto | 12 horas | 96 horas |
 
 <Note>
-  **P0 es el único nivel de prioridad con cobertura de respuesta 24/7.** Los incidentes P0 (interrupción completa del servicio o incidente de seguridad) son gestionados directamente por el equipo de ingeniería de Mintlify. Publicamos actualizaciones de estado en tiempo real y el progreso de los incidentes en [status.mintlify.com](https://status.mintlify.com).
+  **P0 es el único nivel de prioridad con cobertura de respuesta 24/7.** El equipo de ingeniería de Mintlify gestiona directamente los incidentes P0 (interrupción completa del servicio o incidente de seguridad). Publicamos actualizaciones de estado en tiempo real y el progreso de los incidentes en [status.mintlify.com](https://status.mintlify.com).
 
   **Los tiempos de respuesta P1–P3 se aplican únicamente durante el horario laboral de Mintlify: 9 a. m.–5 p. m. PT, de lunes a viernes, excluyendo los días festivos de EE. UU.**
 </Note>
@@ -134,7 +134,7 @@ Los niveles 2 y 3 incluyen los mismos objetivos de tiempo de respuesta. Mintlify
   </Accordion>
 
   <Accordion title="¿Cómo funciona el enrutamiento por IA?">
-    Cuando envías un mensaje en tu canal de Slack dedicado, nuestra herramienta de IA detecta si se trata de un problema relacionado con soporte y lo enruta automáticamente a nuestra bandeja de entrada de soporte. Esto garantiza que tus problemas se capturen y clasifiquen sin requerir intervención manual.
+    Cuando envías un mensaje en tu canal de Slack dedicado, nuestra herramienta de IA detecta si se trata de un problema relacionado con soporte y lo enruta automáticamente a nuestra bandeja de entrada de soporte. Esto garantiza que capturemos y clasifiquemos tus problemas sin requerir intervención manual.
   </Accordion>
 </AccordionGroup>
 
@@ -144,11 +144,11 @@ Los niveles 2 y 3 incluyen los mismos objetivos de tiempo de respuesta. Mintlify
 
 <AccordionGroup>
   <Accordion title="¿Qué se considera un incidente P0?">
-    Un P0 es una interrupción completa del servicio o un incidente de seguridad que afecta a tu implementación de Mintlify. La clasificación P0 la determina Mintlify. Supervisamos nuestros sistemas de forma continua y abrimos proactivamente incidentes P0 cuando se cumplen los criterios. El estado en tiempo real está siempre disponible en [status.mintlify.com](https://status.mintlify.com).
+    Un P0 es una interrupción completa del servicio o un incidente de seguridad que afecta a tu implementación de Mintlify. Mintlify determina la clasificación P0. Supervisamos nuestros sistemas de forma continua y abrimos proactivamente incidentes P0 cuando nuestros criterios coinciden. El estado en tiempo real está siempre disponible en [status.mintlify.com](https://status.mintlify.com).
   </Accordion>
 
   <Accordion title="¿Cuál es el horario laboral de Mintlify?">
-    Los objetivos de tiempo de respuesta P1–P3 se aplican durante las **9 a. m.–5 p. m. PT, de lunes a viernes, excluyendo los días festivos de EE. UU.** Los incidentes P0 se cubren 24/7 y los gestiona el equipo de ingeniería de Mintlify.
+    Los objetivos de tiempo de respuesta P1–P3 se aplican durante las **9 a. m.–5 p. m. PT, de lunes a viernes, excluyendo los días festivos de EE. UU.** El equipo de ingeniería de Mintlify cubre y gestiona los incidentes P0 24/7.
   </Accordion>
 </AccordionGroup>
 

diff --git a/es/agent/integrations.mdx b/es/agent/integrations.mdx
@@ -12,7 +12,7 @@ Las integraciones del agente dan al agente acceso al contexto de otras herramien
 
 Las integraciones se conectan de una de dos formas:
 
-- **Las integraciones compartidas** se conectan una sola vez para toda tu organización. Cualquier miembro del equipo puede pedirle al agente que las use. Slack, Notion, Linear, Jira, Confluence, Salesforce, Intercom y Plain son compartidas.
+- **Las integraciones compartidas** se conectan una sola vez para toda tu organización. Cualquier miembro del equipo puede pedirle al agente que las use. Slack, Notion, Linear, Jira, Confluence, Salesforce, Intercom y Plain se conectan todas de esta manera.
 - **Las integraciones personales** se conectan por usuario. Cada miembro autoriza su propia cuenta, y el agente solo puede usar una integración personal en nombre del usuario que la conectó. Google Calendar es personal.
 
 Las integraciones personales mantienen los datos específicos del usuario, como los eventos del calendario, acotados al usuario que conectó la integración en lugar de compartirse en toda la organización.

diff --git a/es/ai/contextual-menu.mdx b/es/ai/contextual-menu.mdx
@@ -31,7 +31,7 @@ El menú contextual incluye varias opciones preconfiguradas que puedes habilitar
 | **Abrir en Grok**                                  | `grok`        | Crea una conversación en Grok con la página actual como contexto                      |
 | **Abrir en Google AI Studio**                      | `aistudio`    | Crea una conversación en Google AI Studio con la página actual como contexto          |
 | **Abrir en Devin**                                 | `devin`       | Crea una sesión de Devin con la página actual como contexto                           |
-| **Abrir en Devin Desktop**                         | `windsurf`    | Abre Devin Desktop con la página actual como contexto. Requiere que Devin Desktop esté instalado. |
+| **Abrir en Devin Desktop**                         | `windsurf`    | Abre Devin Desktop con la página actual como contexto. Requiere instalar Devin Desktop. |
 | **Copiar URL del servidor MCP**                    | `mcp`         | Copia la URL de tu servidor MCP al portapapeles                                       |
 | **Copiar comando de instalación del servidor MCP** | `add-mcp`     | Copia el comando `npx add-mcp` para instalar el servidor MCP                          |
 | **Conectar con Cursor**                            | `cursor`      | Instala tu servidor MCP alojado en Cursor                                             |