Untitled draft

.vale.ini

@@ -2,7 +2,7 @@
 
 StylesPath = .vale/styles
 MinAlertLevel = suggestion
-IgnoredScopes = code, tt, img, url, a
+IgnoredScopes = code, code, tt, img, url, a
 SkippedScopes = script, style, pre, figure, code
 
 Vocab = Mintlify
@@ -20,24 +20,43 @@ TokenIgnores = (?m)((?:import|export) .+?$), \
 (?<!`)(<\w+ ?.+ ?\/>)(?!`), \
 (<[A-Z]\w+>.+?<\/[A-Z]\w+>), \
 (<[^>]*>), \
-\{(?!/\*)[^}]*\}, \
-(`[^`]*`), \
-(?m)^openapi: .+$, \
+\{(?!/\*)(?!/\*)[^}]*\}, \
+(`[^`]*`), \, \
+(?m)^openapi: .+$, \(?m)^openapi: .+$, \
+([\w-]+\.)+(?:json|jsonl|png|jpe?g|gif|svg|mdx?|txt|ya?ml|xml|com|dev|io|ts|js|tsx|jsx), \
+[\w-]+="[^"\n]*", \
+[\w.+-]+@[\w.-]+, \
+\(/[^)\s]*\)
+
 ([\w-]+\.)+(?:json|jsonl|png|jpe?g|gif|svg|mdx?|txt|ya?ml|xml|com|dev|io|ts|js|tsx|jsx), \
 [\w-]+="[^"\n]*", \
 [\w.+-]+@[\w.-]+, \
 \(/[^)\s]*\)
 
 BlockIgnores = (?sm)^(<\w+\n .*\s\/>)$, \
-(?sm)^({(?!/\*).+?})$, \
-(?sm)^[ \t]*```[\s\S]*?```$
+(?sm)^({(?!/\*)(?!/\*).+??})$, \
+(?sm)^[ \t]*[ \t]*```[\s\S]*?```$
 
 CommentDelimiters = {/*, */}
 
 [changelog.mdx]
 BasedOnStyles = ""
 
 # Code-generator snippet with no prose content
+# Code-generator snippet with no prose content
+[snippets/vercel-json-generator.mdx]
+BasedOnStyles = ""
+
+# Component docs use dotted JSX names (Color.Row, Tree.Folder) that
+# false-positive the sentence-spacing rule
+[components/{color,tree}.mdx]
+Mintlify.Spacing = NO
+
+# Vale lints /api-playground/... link targets in these files in a pass
+# that ignores in-document toggles
+[{api-playground/asyncapi-setup.mdx,organize/settings-reference.mdx}]
+Vale.Terms = NO
+
 [snippets/vercel-json-generator.mdx]
 BasedOnStyles = ""
 

advanced-support.mdx

@@ -4,12 +4,16 @@ description: "Get premium support with faster response times, a dedicated custom
 keywords: ["support", "CSM", "enterprise"]
 ---
 
+import LocalSnippet from '/es/folder/local-snippet.mdx';
+
 ## Support tiers
 
 Mintlify offers three support tiers. The right tier depends on the level of commitment, response time, and relationship you need.
 
-| | Standard | Advanced Slack | Dedicated CSM |
-|---|---|---|---|
+<LocalSnippet />
+
+|  | 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 |
@@ -21,23 +25,26 @@ Mintlify offers three support tiers. The right tier depends on the level of comm
   <Card title="Tier 1 · Standard" icon="laptop" href="#tier-1-standard-support-included">
     Included with all plans. Reach us via the dashboard. Best-effort response with no time target commitments.
   </Card>
+
   <Card title="Tier 2 · Advanced Slack Support" icon="slack" href="#tier-2-advanced-slack-support-add-on">
     Dedicated Slack channel with AI-powered routing to our support inbox. Includes response time targets for P0–P3 issues.
   </Card>
+
   <Card title="Tier 3 · Dedicated CSM" icon="handshake" href="#tier-3-dedicated-csm-add-on">
     An assigned CSM owns your channel, responds directly, and escalates to support internally. The highest level of hands-on support we offer.
   </Card>
 </CardGroup>
 
 ### Tier 1: Standard support (included)
 
-Included with all Enterprise plans. Reach us through the dashboard or at support@mintlify.com. We do our best to respond and resolve issues quickly.
+Included with all Enterprise plans. Reach us through the dashboard or at [support@mintlify.com](mailto:support@mintlify.com). We do our best to respond and resolve issues quickly.
 
 ### Tier 2: Advanced Slack Support (add-on)
 
 We set up a dedicated Slack channel for your team. An AI tool monitors the channel, detects support-related messages, and automatically routes them into our support inbox where our team responds.
 
 **What you get:**
+
 - Dedicated Slack channel connected to our support team
 - Automatic AI-powered issue detection and routing to our support inbox
 - Priority-based response time targets (see table below)
@@ -50,6 +57,7 @@ We set up a dedicated Slack channel for your team. An AI tool monitors the chann
 You get an assigned Customer Success Manager who owns your dedicated Slack channel. Your CSM responds to questions directly and manually escalates issues to the support team when needed (enabling faster internal coordination and resolution by working alongside support in real time).
 
 **What you get:**
+
 - Assigned CSM as your primary contact and channel owner
 - Manual escalation to the support team with direct internal coordination
 - Priority-based response time targets (see table below)
@@ -61,21 +69,21 @@ You get an assigned Customer Success Manager who owns your dedicated Slack chann
 
 ### Response time targets
 
-Tiers 2 and 3 include the same response time targets. {/* vale Mintlify.Will = NO */}
-Mintlify will use commercially reasonable efforts to meet the following service levels:
+Tiers 2 and 3 include the same response time targets. {/* vale Mintlify.Will = NO */} Mintlify will use commercially reasonable efforts to meet the following service levels:
+
 {/* vale Mintlify.Will = YES */}
 
 | Priority | Definition | Initial response | Target resolution |
-|---|---|---|---|
+| --- | --- | --- | --- |
 | **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.** 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).
+  **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.**
+  **P1–P3 response times apply during Mintlify business hours only: 9 AM–5 PM PT, Monday–Friday, excluding US holidays.**
 </Note>
 
 ## FAQ
@@ -137,5 +145,7 @@ Mintlify will use commercially reasonable efforts to meet the following service
 ## Get started
 
 {/* vale Vale.Terms = NO */}
-Contact your Mintlify account team to add Advanced Slack Support (Tier 2) or a Dedicated CSM (Tier 3), or email gtm@mintlify.com.
-{/* vale Vale.Terms = YES */}
+
+Contact your Mintlify account team to add Advanced Slack Support (Tier 2) or a Dedicated CSM (Tier 3), or email [gtm@mintlify.com](mailto:gtm@mintlify.com).
+
+{/* vale Vale.Terms = YES */}

ai-native.mdx

@@ -2,9 +2,14 @@
 title: "AI-native documentation"
 sidebarTitle: "AI-native"
 description: "Discover how AI-native features enhance reading, writing, and discovering your documentation with the assistant, agent, and MCP server."
-keywords: ["AI","assistant","agent","llms.txt","MCP","llms-full.txt"]
+keywords: ["AI", "assistant", "agent", "llms.txt", "MCP", "llms-full.txt"]
 ---
 
+| rob |  |  |
+| --- | --- | --- |
+|  |  |  |
+|  |  |  |
+
 When you host your documentation on Mintlify, built-in AI features help your users find answers and your team maintain content more efficiently. Your content provides the context for these AI-native features to improve the experiences of reading, writing, and discovering your documentation.
 
 ## What makes your documentation AI-native
@@ -49,10 +54,12 @@ Select any of the following cards for more information.
   <Card title="Assistant" icon="bot-message-square" href="/assistant/configure">
     Configure the assistant to search external sites or direct people to your support team if it can't answer their questions.
   </Card>
+
   <Card title="Automations" icon="message-circle-plus" href="/automations/index">
     Get documentation updates automatically on a schedule or when a push event occurs.
   </Card>
+
   <Card title="Contextual menu" icon="sparkles" href="/ai/contextual-menu">
     Add a menu to pages that lets users query AI tools, connect to your MCP server, and copy pages as context with one click.
   </Card>
-</CardGroup>
+</CardGroup>

ai/llmstxt.mdx

@@ -9,7 +9,7 @@ import { PreviewButton } from "/snippets/previewbutton.jsx"
 
 The [llms.txt file](https://llmstxt.org) is an industry standard that helps LLMs index content more efficiently, similar to how a sitemap helps search engines. AI tools can use this file to understand your documentation structure and find content relevant to user queries.
 
-Mintlify automatically hosts an `llms.txt` file at the root of your project that lists all available pages in your documentation. This file is always up to date and requires zero maintenance. You can optionally add a custom `llms.txt` file to the root of your project.
+Mintlify   automatically hosts an `llms.txt` file at the root of your project that lists all available pages in your documentation. This file is always up to date and requires zero maintenance. You can optionally add a custom `llms.txt` file to the root of your project.
 
 <Note>
   Authentication affects `llms.txt` and `llms-full.txt` differently depending on your site configuration:
@@ -80,4 +80,4 @@ Mintlify automatically hosts an `llms-full.txt` file at the root of your project
 
 To add a custom `llms.txt` or `llms-full.txt` file, create an `llms.txt` or `llms-full.txt` file at the root of your project. Adding a custom file overrides the automatically generated file of the same name. If you delete a custom file, Mintlify restores the automatically generated file.
 
-Your custom `llms.txt` or `llms-full.txt` file must have a site title as an H1 heading. Other content is optional. See [Format](https://llmstxt.org/#format) in the `llms.txt` specification for more information on optional sections and best practices.
+Your custom `llms.txt` or `llms-full.txt` file must have a site title as an H1 heading. Other content is optional. See [Format](https://llmstxt.org/#format) in the `llms.txt` specification for more information on optional sections and best practices.