Resolve vale errors

.vale.ini

@@ -6,7 +6,6 @@ IgnoredScopes = code, tt, img, url, a
 SkippedScopes = script, style, pre, figure, code
 
 Packages = Google
-
 Vocab = Mintlify
 
 # This is required since Vale doesn't officially support MDX
@@ -23,9 +22,16 @@ Vale.Avoid = NO # Too aggressive about common technical terms
 TokenIgnores = (?sm)((?:import|export) .+?$), \
 (?<!`)(<\w+ ?.+ ?\/>)(?!`), \
 (<[A-Z]\w+>.+?<\/[A-Z]\w+>), \
-(<[^>]*>)
+(<[^>]*>), \
+\{[^}]*\}, \
+(`[^`]*`), \
+(```[\s\S]*?```)
 
 BlockIgnores = (?sm)^(<\w+\n .*\s\/>)$, \
-(?sm)^({.+.*})
+(?sm)^({.+.*})$, \
+(?sm)^```[\s\S]*?```$
+
+CommentDelimiters = {/*, */}
 
-CommentDelimiters = {/*, */}
+[changelog.mdx]
+BasedOnStyles =

.vale/styles/config/vocabularies/Mintlify/accept.txt

@@ -3,12 +3,14 @@
 # =============================================================================
 # MINTLIFY-SPECIFIC TERMS
 # =============================================================================
+APISection
 autoplay
 bearerAuth
 borderRadius
 camelCase
 discoverability
 (?i)callouts?
+CTAs
 drilldown
 expandables
 favicon
@@ -17,9 +19,11 @@ isHidden
 (?i)modetoggle
 myName
 myObject
+navbar
 onboarding
 (?i)openapi
 repo
+Ronan
 topbar
 (?i)tooltips?
 url
@@ -40,6 +44,7 @@ CircleCI
 Clearbit
 Ctrl
 Cypress
+Docusaurus
 Django
 DynamoDB
 Elasticsearch
@@ -76,6 +81,7 @@ Mocha
 MongoDB
 MySQL
 Next.js
+nginx
 Node.js
 NodeJS
 npx
@@ -115,6 +121,7 @@ Webflow
 WebKit
 (?i)webpack
 WebStorm
+Windsurf's
 Zapier
 
 # =============================================================================
@@ -123,21 +130,22 @@ Zapier
 agentic
 allowlist
 APIs
+API's
 args
 async
-autogenerated
-autogenerating
+autogenerat(e|ed|ing)?
 await
 bool
 boolean
 Blockquote
 Blockquotes
 cdn
 cli
+CNAME
+cpu
 config
 const
 cors
-CNAME
 csrf
 css
 ctx
@@ -171,6 +179,7 @@ lang
 len
 localhost
 md
+(?i)Memoize
 middleware
 Multiline
 mvc
@@ -186,6 +195,7 @@ orm
 params
 pnpm
 png
+prefill(ing|ed)?
 prepend
 prepended
 prev
@@ -234,8 +244,9 @@ ux
 val
 var
 vars
+waypoints
 webhook
-websocket
+websockets?
 xhr
 xhr2
 yaml

analytics/feedback.mdx

@@ -54,13 +54,13 @@
 Best practices for setting feedback statuses:
 
 * **Pending**: Feedback is awaiting review.
 * **In Progress**: Feedback has been validated and is being worked on.
 * **Resolved**: Feedback has been resolved.
 * **Dismissed**: Feedback has been dismissed as not actionable, irrelevant, or inaccurate.
 
 ### Filtering by status
 
-Use the status filter to control which feedback is displayed. Uncheck a status to hide all feedback with that status. By default, all feedback is displayed.
+Use the status filter to control which feedback is displayed. Clear a status to hide all feedback with that status. By default, all feedback is displayed.
 
 ### Adding internal notes
 

authentication-personalization/overview.mdx

@@ -27,8 +27,7 @@
 
 **Choose partial authentication when:**
 - Offering public getting-started guides with private advanced features
-- Running a freemium product where premium users get additional documentation
 - Publishing open-source docs with private enterprise sections
 
 **Choose personalization when:**
 - Creating public API documentation that shows user-specific examples
@@ -41,7 +40,7 @@
 
 | Method | Available for | Setup complexity | Best for |
 |:-------|:--------------|:-----------------|:----------|
 | **JWT** | All approaches | Medium | Custom login flows, maximum security control |
 | **OAuth 2.0** | All approaches | High | Third-party auth providers, enterprise security |
 | **Mintlify Dashboard** | Authentication only | Low | Teams already using Mintlify dashboard |
 | **Password** | Authentication only | Low | Simple shared access without personalization |
@@ -49,15 +48,15 @@
 
 ### When to use each method
 
 **JWT**: Use when you have an existing authentication system and want full control over the login flow. Ideal for custom user management or when you need to decouple documentation access from your main application.
 
 **OAuth 2.0**: Use when you want to leverage third-party authentication providers (Google, GitHub, etc.) or need enterprise-grade security standards. Best for organizations already using OAuth infrastructure.
 
 **Mintlify Dashboard**: Use when your documentation editors are also your documentation readers. Perfect for internal teams who already manage content through the Mintlify dashboard.
 
 **Password**: Use for simple access control when you don't need to track individual users or personalize content. Good for contractors, beta users, or temporary access scenarios.
 
 **Shared Session**: Use when you want seamless login between your application and documentation. Ideal when users are already authenticated in your main application and you want to personalize their documentation experience.
 
 ## Content customization
 

contact-support.mdx

@@ -1,27 +1,27 @@
 ---
 title: "Contact support"
 icon: "circle-help"
 description: "We're here to help you get the most out of Mintlify"
 ---
 
 ## Ask our docs
 
 Select <kbd>Command</kbd> + <kbd>I</kbd> to start a chat with our AI assistant trained on our documentation.
 
 ## Watch video tutorials
 
 Visit our [YouTube](https://www.youtube.com/@GetMintlify/videos) channel for tutorials and guides on using Mintlify.
 
 ## Message support
 
 Send us a message from your [dashboard](https://dashboard.mintlify.com/) by selecting **Support** in the sidebar.
 
-![Gif showing how to access support from the dashboard by selecting the Support button, then selecting an option and typing a question in the support modal that pops up.](https://mintlify.s3.us-west-1.amazonaws.com/mintlify/images/support-flow.gif)
+![GIF showing how to access support from the dashboard by selecting the Support button, then selecting an option and typing a question in the support modal that pops up.](https://mintlify.s3.us-west-1.amazonaws.com/mintlify/images/support-flow.gif)
 
 <Info>
 We aim to respond to all requests within 24 hours, but delays may occur during busy times.
 </Info>
 
 ## Email support
 
 If you can't access your dashboard, please email us at <a href="mailto:[email protected]">[email protected]</a>.

guides/claude-code.mdx

@@ -11,7 +11,7 @@
 ## Getting started
 
 **Prerequisites:**
 - Active Claude subscription (Pro, Max, or API access)
 
 **Setup:**
 1. Install Claude Code:
@@ -19,7 +19,7 @@
   npm install -g @anthropic-ai/claude-code
   ```
 2. Navigate to your docs directory.
 3. (Optional) Add the `CLAUDE.md` file below to your project.
 4. Run `claude` to start.
 
 ## CLAUDE.md template
@@ -34,7 +34,7 @@
 ## Working relationship
 - You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
 - ALWAYS ask for clarification rather than making assumptions
-- NEVER lie, guess, or make up information
+- NEVER lie, guess, or make up anything
 
 ## Project context
 - Format: MDX files with YAML frontmatter
@@ -43,9 +43,9 @@
 
 ## Content strategy
 - Document just enough for user success - not too much, not too little
-- Prioritize accuracy and usability of information
+- Prioritize accuracy and usability
 - Make content evergreen when possible
-- Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
+- Search for existing content before adding anything new. Avoid duplication unless it is done for a strategic reason
 - Check existing patterns for consistency
 - Start by making the smallest reasonable changes
 
@@ -117,12 +117,12 @@
 Create code examples for [your API endpoint] in JavaScript, Python, and cURL with error handling
 ```
 
 ## Extending Claude Code
 
 Beyond manually prompting Claude Code, you can integrate it with your existing workflows.
 
 ### Automation with GitHub Actions
 Run Claude Code automatically when code changes to keep docs up to date. You can trigger documentation reviews on pull requests or update examples when API changes are detected.
 
 ### Multi-instance workflows
 Use separate Claude Code sessions for different tasks - one for writing new content and another for reviewing and quality assurance. This helps maintain consistency and catch issues that a single session might miss.

guides/hidden-pages.mdx

@@ -4,7 +4,7 @@
 icon: "eye-closed"
 ---
 
 Hidden pages are removed from your site's navigation but remain publicly accessible to anyone who knows their URL.
 
 Use hidden pages for content that you want to be accessible on your site or referenced as context for AI tools, but not discoverable through the navigation.
 
@@ -14,9 +14,9 @@
 
 ## Hiding a page
 
 A page is hidden if it is not included in your `docs.json` navigation. To hide a page, remove it from your navigation structure.
 
-Hidden pages use the same URL structure as regular pages based on their file path.  For example,  `guides/hidden-page.mdx` would be accessible at `docs.yoursite.com/guides/hidden-page`.
+Hidden pages use the same URL structure as regular pages based on their file path. For example,  `guides/hidden-page.mdx` would be accessible at `docs.yoursite.com/guides/hidden-page`.
 
 See an [example of a hidden page](/guides/hidden-page-example).
 
@@ -26,7 +26,7 @@
 
 ## Hiding a group of pages
 
 A group of pages is hidden if the `hidden` property is set to `true` in your `docs.json` file:
 
 ```json highlight={4}
 "groups": [
@@ -47,7 +47,7 @@
   }
 ]
 ```
 In this example, the `Getting started` group is hidden, but the `Guides` group is visible.
 
 ### Hiding a tab
 
@@ -66,9 +66,9 @@
 ]
 ```
 
 ## Search, SEO, and AI indexing
 
 By default, hidden pages are excluded from indexing for search engines, internal search within your docs, and as context for the AI assistant. To include hidden pages in search results and as context for the assistant, add the `seo` property to your `docs.json`:
 
 ```json
 "seo": {

settings.mdx

@@ -197,7 +197,7 @@
 
   <Expandable title="Fonts">
     <ResponseField name="family" type="string" required>
-      Font family, such as "Open Sans", "Playfair Display."
+      Font family, such as "Open Sans."
     </ResponseField>
     <ResponseField name="weight" type="number">
       Font weight, such as 400 or 700. Variable fonts support precise weights  such as 550.
@@ -219,7 +219,7 @@
           Font weight, such as 400, 700. Variable fonts support precise weights such as 550.
         </ResponseField>
         <ResponseField name="source" type="string (uri)">
           URL to your font source, such as https://mintlify-assets.b-cdn.net/fonts/Hubot-Sans.woff2. [Google Fonts](https://fonts.google.com) are loaded automatically when you specify a Google Font `family` name, so no source URL is needed.
         </ResponseField>
         <ResponseField name="format" type="&quot;woff&quot; | &quot;woff2&quot;">
           Font file format.
@@ -343,7 +343,7 @@
 
   <Expandable title="Navigation">
     <ResponseField name="global" type="object">
-      Global navigation elements that appear accross all pages and sections.
+      Global navigation elements that appear across all pages and sections.
 
       <Expandable title="Global">
         <ResponseField name="languages" type="array of object">
@@ -495,7 +495,7 @@
 
   <Expandable title="Interaction">
     <ResponseField name="drilldown" type="boolean">
       Control automatic navigation behavior when selecting navigation groups. Set to `true` to force navigation to the first page when a navigation group is expanded. Set to `false` to prevent navigation and only expand or collapse the group. Leave unset to use the theme's default behavior.
     </ResponseField>
   </Expandable>
 </ResponseField>
@@ -572,7 +572,7 @@
       Destination path to redirect to. Example: `/new-page`
     </ResponseField>
     <ResponseField name="permanent" type="boolean">
       Whether to use a permanent redirect (301). Defaults to `true`.
     </ResponseField>
   </Expandable>
 </ResponseField>
@@ -583,13 +583,13 @@
   <Expandable title="Contextual">
     <ResponseField name="options" type="array of &quot;copy&quot; | &quot;view&quot; | &quot;chatgpt&quot; | &quot;claude&quot; | &quot;perplexity&quot; | &quot;mcp&quot; | &quot;cursor&quot; | &quot;vscode&quot;" required>
       Actions available in the contextual menu. The first option appears as the default.
       - `copy`: Copy the current page as Markdown to the clipboard.
       - `view`: View the current page as Markdown in a new tab.
       - `chatgpt`: Send the current page content to ChatGPT.
       - `claude`: Send the current page content to Claude.
       - `perplexity`: Send the current page content to Perplexity.
       - `mcp`: Copies your MCP server URL to the clipboard.
       - `cursor`: Installs your hosted MCP server in Cursor.
       - `vscode`: Installs your hosted MCP server in VSCode.
 
       <img src="/images/page-context-menu.png" alt="Contextual Menu" className="rounded-xl" />
@@ -602,7 +602,7 @@
   </Expandable>
 </ResponseField>
 
 ### API Configurations
 
 <ResponseField name="api" type="object">
   API documentation and interactive playground settings.
@@ -698,10 +698,10 @@
   </Expandable>
 </ResponseField>
 
 ### SEO and search
 
 <ResponseField name="seo" type="object">
   SEO indexing configurations.
 
   <Expandable title="Seo">
     <ResponseField name="metatags" type="object">
@@ -937,7 +937,7 @@
       404 "Page not found" error handling.
       <Expandable title="404">
         <ResponseField name="redirect" type="boolean">
           Whether to automatically redirect to the home page when a page is not
           found.
         </ResponseField>
         <ResponseField name="title" type="string">
@@ -1493,7 +1493,7 @@
 
 </CodeGroup>
 
 If you already have the CLI installed, make sure it is up to date:
 
 ```bash
 mint update
@@ -1507,7 +1507,7 @@
 mint upgrade
 ```
 
 This command will create a `docs.json` file from your existing `mint.json`. Review the generated file to ensure all settings are correct.
 </Step>
 <Step title="Delete your mint.json file">
 After verifying your `docs.json` is configured properly, you can safely delete your old `mint.json` file.