mintlify · ethanpalm · Jun 19, 2025 · Jun 19, 2025 · Jun 19, 2025
diff --git a/advanced/dashboard/permissions.mdx b/advanced/dashboard/permissions.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Editor Permissions'
+title: 'Editor permissions'
 description: 'Allow more members of your team to update your docs'
 ---
 

diff --git a/advanced/dashboard/sso.mdx b/advanced/dashboard/sso.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Single Sign-On (SSO)"
+title: "Single sign-on (SSO)"
 description: "Customize how your team can login to your admin dashboard"
 ---
 
@@ -7,9 +7,9 @@
  SSO functionality is available on [Enterprise plan](https://mintlify.com/pricing?ref=sso).
 </Info>

 Use single sign-on to your dashboard via SAML and OIDC. If you use Okta, Google Workspace, or Microsoft Entra, we have provider-specific documentation for setting up SSO. If you use another provider, please [contact us](mailto:[email protected]).

 ## Okta

 <Tabs>
    <Tab title="SAML">
@@ -45,7 +45,7 @@
            </Step>
            <Step title="Send us your IdP information">
                Once the application is set up, navigate to the General tab and locate the client ID & client secret.
                Please securely provide us with these, along with your Okta instance URL (e.g. `<your-tenant-name>.okta.com`). You can send these via a service like 1Password or SendSafely.
            </Step>
        </Steps>
    </Tab>
@@ -91,7 +91,7 @@
    </Tab>
 </Tabs>

 ## Microsoft Entra

 <Tabs>
    <Tab title="SAML">

diff --git a/ai-ingestion.mdx b/ai-ingestion.mdx
@@ -1,6 +1,6 @@
 ---
-title: "AI Ingestion"
+title: "AI ingestion"
 description: "Prepare your documentation for LLMs and AI tools"
 icon: "bot-message-square"
 ---

@@ -12,7 +12,7 @@
  )
 }

 Mintlify generates optimized formats and provides shortcuts that help users get faster, more accurate responses when using your documentation as context for LLMs and AI tools.

 ## Contextual menu

@@ -40,8 +40,8 @@
   "options": [
     "copy",
     "view",
     "chatgpt",
     "claude"
   ]
 }
 }
@@ -49,7 +49,7 @@

 ## /llms.txt

 The [/llms.txt file](https://llmstxt.org) is an industry standard that helps general-purpose LLMs index more efficiently, similar to how a sitemap helps search engines.

 Every documentation site automatically hosts an `/llms.txt` file at the root that lists all available pages in your documentation. AI tools can use this file to understand your documentation structure and find relevant content to user prompts.

@@ -75,4 +75,4 @@

 ### Command \+ C shortcut

 Select Command \+ C (Ctrl \+ C on Windows) to copy any page as Markdown.
diff --git a/api-playground/asyncapi/setup.mdx b/api-playground/asyncapi/setup.mdx
@@ -1,18 +1,18 @@
 ---
-title: "AsyncAPI Setup"
+title: "AsyncAPI setup"
 description: "Create websocket reference pages with AsyncAPI"
 ---
 
 ## Add an AsyncAPI specification file

 To begin to create pages for your websockets, make sure you have a valid AsyncAPI schema document in either JSON or YAML format that follows the [AsyncAPI specification](https://www.asyncapi.com/docs/reference/specification/v3.0.0). Your schema must follow the AsyncAPI specification 3.0+.

 <Tip>
  To make sure your AsyncAPI schema is valid, you can paste it into the
  [AsyncAPI Studio](https://studio.asyncapi.com/)
 </Tip>

 ## Auto-populate websockets pages

 You can add an `asyncapi` field to any tab or group in the navigation of your `docs.json`. This field can contain either the path to an AsyncAPI schema document in your docs repo, the URL of a hosted AsyncAPI schema document, or an array of links to AsyncAPI schema documents. Mintlify will automatically generate a page for each AsyncAPI websocket channel.

@@ -73,7 +73,7 @@

 ## Channel page

 If you want more control over how you order your channels or if you want to just reference a single channel, you can create an MDX file with the `asyncapi` field in the frontmatter.

 ```mdx
 ---

diff --git a/api-playground/mdx/configuration.mdx b/api-playground/mdx/configuration.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'MDX Setup'
+title: 'MDX setup'
 description: 'Generate docs pages for your API endpoints using `MDX`'
 ---
 
@@ -160,7 +160,7 @@
 ```mdx Page Metadata
 ---
 title: "Your page title"
 authMethod: "none"
 ---
 ```
 </CodeGroup>
diff --git a/api-playground/openapi-setup.mdx b/api-playground/openapi-setup.mdx
@@ -1,5 +1,5 @@
 ---
-title: "OpenAPI Setup"
+title: "OpenAPI setup"
 description: "Reference OpenAPI endpoints in your docs pages"
 icon: "file-json"
 ---
@@ -25,7 +25,7 @@

 ### Specifying the URL for your API

 To enable Mintlify features like the API playground, add a `servers` field to your OpenAPI document with your API's base URL.

 ```json
 {
@@ -192,10 +192,10 @@

 ### Autogenerate `MDX` files

 Use our Mintlify [scraper](https://www.npmjs.com/package/@mintlify/scraping) to autogenerate `MDX` pages for large OpenAPI documents.

 <Note>
  Your OpenAPI document must be valid or the files will not autogenerate.
 </Note>

 The scraper generates:
@@ -207,12 +207,12 @@
 <Steps>
  <Step title="Generate `MDX` files.">
    ```bash
    npx @mintlify/scraping@latest openapi-file <path-to-openapi-file>
    ```
  </Step>
  <Step title="Specify an output folder.">
    ```bash
    npx @mintlify/scraping@latest openapi-file <path-to-openapi-file> -o api-reference
    ```

    Add the `-o` flag to specify a folder to populate the files into. If a folder is not specified, the files will populate in the working directory.

diff --git a/authentication-personalization/authentication-setup.mdx b/authentication-personalization/authentication-setup.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Authentication Setup"
+title: "Authentication setup"
 description: "Guarantee privacy of your docs by authenticating users"
 icon: "file-lock"
 ---
@@ -19,7 +19,7 @@
 <Tab title="JWT">
 ### Prerequisites

 * An authentication system that can generate and sign JWTs.
 * A backend service that can create redirect URLs.

 ### Implementation
@@ -54,20 +54,20 @@

 <CodeGroup>
 ```ts TypeScript
 import * as jose from 'jose';
 import { Request, Response } from 'express';

 const TWO_WEEKS_IN_MS = 1000 * 60 * 60 * 24 * 7 * 2;

 const signingKey = await jose.importPKCS8(process.env.MINTLIFY_PRIVATE_KEY, 'EdDSA');

 export async function handleRequest(req: Request, res: Response) {
  const user = {
    expiresAt: Math.floor((Date.now() + TWO_WEEKS_IN_MS) / 1000), // 2 week session expiration
    groups: res.locals.user.groups,
    content: {
      firstName: res.locals.user.firstName,
      lastName: res.locals.user.lastName,
    },
  };

@@ -168,8 +168,8 @@
 ```json
 {
  "content": {
    "firstName": "Jane",
    "lastName": "Doe"
  },
  "groups": ["engineering", "admin"]
 }

diff --git a/authentication-personalization/partial-authentication-setup.mdx b/authentication-personalization/partial-authentication-setup.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Partial Authentication Setup"
+title: "Partial authentication setup"
 description: "Control access to specific pages"
 icon: "file-lock-2"
 ---
@@ -14,7 +14,7 @@

 ## Making pages public

 By default, all pages are protected. Add the `public` property to the page's frontmatter to make it viewable without authentication:

 ```mdx
 ---

diff --git a/authentication-personalization/personalization-setup.mdx b/authentication-personalization/personalization-setup.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Personalization Setup"
+title: "Personalization setup"
 description: "Let users log in for customized documentation experiences"
 icon: "user-cog"
 ---
@@ -16,7 +16,7 @@
  <Tab title="JWT">
 ### Prerequisites

 * A login system that can generate and sign JWTs.
 * A backend service that can create redirect URLs.

 ### Implementation
@@ -124,8 +124,8 @@
 ```json
 {
  "content": {
    "firstName": "Jane",
    "lastName": "Doe"
  },
  "groups": ["engineering", "admin"]
 }
@@ -159,8 +159,8 @@
    * Uses your existing session authentication to identify users
    * Returns user data in the `User` format (see [Sending Data](/authentication-personalization/sending-data))
    * If the API domain and the docs domain **do not exactly match**:
      * Add the docs domain to your API's `Access-Control-Allow-Origin` header (must not be `*`).
      * Set your API's `Access-Control-Allow-Credentials` header to `true`.

      <Warning>
        Only enable CORS headers on this specific endpoint, not your entire dashboard API.

diff --git a/authentication-personalization/sending-data.mdx b/authentication-personalization/sending-data.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Sending Data"
+title: "Sending data"
 description: "User data format for personalizing your documentation"
 icon: "send"
 ---
@@ -26,8 +26,8 @@
  path="expiresAt"
  type="number"
 >
  Session expiration time in **seconds since epoch**. If the user loads a page after this time, their stored data is automatically deleted and they must reauthenticate.
  <Warning><b>For JWT handshakes:</b> This differs from the JWT's `exp` claim, which determines when a JWT is considered invalid. Set the JWT `exp` claim to a short duration (10 seconds or less) for security. Use `expiresAt` for the actual session length (hours to weeks).</Warning>
 </ParamField>
 <ParamField
  path="groups"
@@ -52,13 +52,13 @@
  ```mdx
  Welcome back, {user.firstName}! Your {user.plan} plan includes...
  ```
  With the example `user` data, this would render as: Welcome back, Ronan! Your Enterprise plan includes...
 </ParamField>
 <ParamField
  path="apiPlaygroundInputs"
  type="object"
 >
  User-specific values that will be prefilled in the API playground if supplied. Save users time when testing your APIs with their own data.

  **Example**:
  ```json
@@ -68,7 +68,7 @@
  "query": { "org_id": "12345" }
  }
  ```
  If a user makes requests at a specific subdomain, you can send `{ server: { subdomain: 'foo' } }` as an `apiPlaygroundInputs` field. This value will be prefilled on any API page with the `subdomain` value.

  <Note>The `header`, `query`, and `cookie` fields will only prefill if they are part of your [OpenAPI security scheme](https://swagger.io/docs/specification/authentication/). If a field is in either the `Authorization` or `Server` sections, it will prefill. Creating a standard header parameter named `Authorization` will not enable this feature.</Note>
 </ParamField>
@@ -77,11 +77,11 @@

 ```json
 {
  "expiresAt": 1735689600,
  "groups": ["admin", "beta-users"],
  "content": {
    "firstName": "Jane",
    "lastName": "Smith",
    "company": "TechCorp",
    "plan": "Enterprise",
    "region": "us-west"
@@ -89,7 +89,7 @@
  "apiPlaygroundInputs": {
    "header": {
      "Authorization": "Bearer abc123",
      "X-Org-ID": "techcorp"
    },
    "server": {
      "environment": "production",

diff --git a/changelog.mdx b/changelog.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Product Updates"
+title: "Product updates"
 description: "New updates and improvements"
 mode: "center"
 ---
@@ -83,7 +83,7 @@
  - Improved styling nits for dashboard border for mobile-tablet-desktop responsiveness
  - Show code examples even when in simple mode for API playground
  - Support "command \+ k" shortcut for search in web editor
  - Codeblocks within callouts expand to fill the width of the callout area
 </Update>

 <Update label="February 2025">
@@ -114,9 +114,9 @@

  Automatically lint your docs to find broken links, discover spelling and grammar issues, or enforce writing styles with your own Vale config. Learn more in our [docs](settings/ci).

  ## .md support for LLMs

  All documentation pages are now automatically available as plain Markdown files—just append `.md` to the URL. This makes it easier for LLMs to ingest individual pages from your documentation.

  ## More Themes

@@ -198,7 +198,7 @@
  <Frame>
    ![llms.txt support](/images/changelog/llms.jpg)
  </Frame>
  All docs instances are now automatically hosted at /llms.txt and /llms-full.txt so that LLMs can easily ingest your documentation. For more information, read the [docs on the new llms.txt standard.](https://llmstxt.org)

  ## Localization

@@ -270,7 +270,7 @@
  ## Dashboard Improvements

  - Added ability to change custom domain to be /docs directly through dashboard settings.
  - Consolidated the login and signup pages to decrease friction and confusion.
  - Implemented the discovery login flow so that users that are members of multiple organizations can now switch between them.
  - Added login with Google OAuth
  - Added ability to add new deployment through dashboard settings.
@@ -284,7 +284,7 @@
  - Don't allow search engines to crawl user-auth protected pages.
  - Revalidate the cache when an org is deleted.
  - We now use the Scalar OpenAPI parser to parse OpenAPI definitions which improves the performance, fixes parsing issues, and surfaces better error messages.
  - Top-level descriptions are now supported in API reference pages autogenerated from OpenAPI definitions.
  - Add in-line-style support for icons
  - Fixed the pop-in of custom CSS in docs.
  - Properly show in-line code styling in conjunction with links.
@@ -317,7 +317,7 @@
  <Frame>
    ![SEO Improvements](/images/changelog/seo-improvements.jpeg)
  </Frame>
  We've fixed  both the mobile and desktop layout of our docs so that they are more SEO-friendly - including adding proper aria tags to navbar and toggle elements.

  ## Dashboard Improvements

@@ -351,7 +351,7 @@

  ## File Uploads in API Playground

  By default, API playground requests are proxied by Mintlify. Now you can use
  `disableProxy` to disable this behavior and support request types like file
  uploads.

@@ -384,7 +384,7 @@
  </Frame>
  For `Pro` users, we introduced Mintlify Widget, an extension of your docs to
  answer your users' questions when and where they asked. You can add this
  AI-powered chatbot to any web page: your landing page, inside your product, or
  on your existing documentation pages.

  - [Read the blog announcement](https://mintlify.com/blog/widget)
@@ -419,7 +419,7 @@
 <Update label="May 2024">
  ## Okta SSO

  We now support sign-on via Okta SAML and OIDC.

  ## Mintlify REST API

@@ -442,7 +442,7 @@
 <Update label="March 2024">
  ## Mintlify MDX for VSCode

  Call snippets of our pre-built components and callouts without leaving VSCode. [Install the extension here](https://marketplace.visualstudio.com/items?itemName=mintlify.mintlify-snippets).
 </Update>

 <Update label="February 2024">
@@ -451,7 +451,7 @@
  - Dashboard upgrades: view update logs to see what's changed and status of an update, toggle between Mintlify projects to manage deployments
  - Versioning with tabs fully supported
  - Wildcard redirects now supported
  - CLI Error Detection: we now show the position of invalid frontmatter when there are parsing issues during local development
 </Update>

 <Update label="January 2024">

diff --git a/components/code-groups.mdx b/components/code-groups.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Code Groups"
+title: "Code groups"
 description: "The CodeGroup component lets you combine code blocks in a display separated by tabs"
 icon: "group"
 ---

diff --git a/components/responses.mdx b/components/responses.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Response Fields'
+title: 'Response fields'
 description: 'Display API response values'
 ---
 

diff --git a/contact-support.mdx b/contact-support.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Contact Support"
+title: "Contact support"
 icon: "circle-help"
 description: "We're here to help you get the most out of Mintlify"
 ---

diff --git a/editor.mdx b/editor.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Web Editor"
+title: "Web editor"
 description: "Build your documentation using the Mintlify web editor"
 icon: "mouse-pointer-2"
 ---

diff --git a/guides/assistant.mdx b/guides/assistant.mdx
@@ -1,5 +1,5 @@
 ---
-title: "AI Assistant"
+title: "AI assistant"
 description: "Help users succeed with your product and find answers faster"
 icon: "bot"
 ---
@@ -12,7 +12,7 @@

 The assistant answers questions about your documentation through natural language queries. When users ask a question, the assistant searches your content, cites relevant sources, and provides contextual answers sourced from your documentation.

 The assistant uses agentic RAG (retrieval-augmented generation) with tool calling and runs on Claude Sonnet 4 by default.

 You can monitor user interactions and export query data from your dashboard to gain insights into user needs and identify content gaps.

@@ -22,7 +22,7 @@

 Users can access the assistant in two ways:

 - **Keyboard shortcut**: <kbd>Command</kbd> + <kbd>I</kbd> (<kbd>Ctrl</kbd> + <kbd>I</kbd> on Windows)
 - **Assistant button** next to the search bar
  <img
    src="/images/assistant/assistant-button-light.png"
@@ -45,7 +45,7 @@

 Both methods open a chat panel on the right side of your docs. Users can ask any question and the assistant will search your documentation for an answer. If no relevant information is found, the assistant will respond that it cannot answer the question.

 ## Making content AI ingestible

 Structure your documentation to help the assistant provide accurate, relevant answers. Clear organization and comprehensive context benefit both human readers and AI understanding.

@@ -54,7 +54,7 @@
  - Write descriptive headings for sections.
  - Create a logical information hierarchy.
  - Use consistent formatting across your docs.
  - Include comprehensive metadata in page frontmatter.
  - Break up long blocks of text into shorter paragraphs.
 </Card>


diff --git a/guides/auth0.mdx b/guides/auth0.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Using Auth0 with the OAuth Handshake"
+title: "Using Auth0 with the OAuth handshake"
 description: "If Auth0 is the source of truth for your user data, you can set up Mintlify as an OAuth client app to authenticate your users."
 ---
 

diff --git a/image-embeds.mdx b/image-embeds.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Images and Embeds'
+title: 'Images and embeds'
 description: 'Add image, video, and other HTML elements'
 icon: 'image'
 ---
@@ -131,7 +131,7 @@

 <Warning>
 Since Mintlify needs to adhere to the JSX syntax, double word attributes will need to 
 be written in camelCase such as `autoPlay` and `playsInline`.
 </Warning>

 ## iFrames

diff --git a/integrations/analytics/overview.mdx b/integrations/analytics/overview.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Analytics Integrations"
+title: "Analytics integrations"
 description: "Integrate with an analytics platform to track events"
 ---
 

diff --git a/integrations/privacy/overview.mdx b/integrations/privacy/overview.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Privacy Integrations"
+title: "Privacy integrations"
 description: "Integrate with a data privacy platform"
 ---
 

diff --git a/integrations/support/overview.mdx b/integrations/support/overview.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Support Integrations"
+title: "Support integrations"
 description: "Integrate with a support widget"
 ---
 

diff --git a/list-table.mdx b/list-table.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Lists and Tables"
+title: "Lists and tables"
 description: "Display information in lists and tables"
 icon: "list"
 ---

diff --git a/reusable-snippets.mdx b/reusable-snippets.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Reusable Snippets'
+title: 'Reusable snippets'
 description: 'Reusable, custom snippets to keep content in sync'
 icon: 'recycle'
 ---

diff --git a/settings.mdx b/settings.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Global Settings"
+title: "Global settings"
 description: "Configure site-wide settings with the `docs.json` file"
 icon: "settings-2"
 keywords: ["docs.json", "settings", "customization", "configuration"]
@@ -13,7 +13,7 @@

 To get started, you only need to specify `theme`, `name`, `colors.primary`, and `navigation`. Other fields are optional and you can add them as your documentation needs grow.

 For the best editing experience, include the schema reference at the top of your `docs.json` file. This enables autocomplete, validation, and helpful tooltips in most code editors:

 ```json
 {
@@ -143,7 +143,7 @@

  <Expandable title="Fonts">
    <ResponseField name="family" type="string" required>
      Font family, such as "Open Sans", "Playfair Display".
    </ResponseField>
    <ResponseField name="weight" type="number">
      Font weight, such as 400 or 700. Variable fonts support precise weights  such as 550.
@@ -248,12 +248,12 @@

 ### Structure

 <ResponseField name="navbar" type="object">
  Navigation bar items.

  <Expandable title="Navbar">
    <ResponseField name="links" type="array of object">
      Links to display in the navbar

      <Expandable title="Links">
        <ResponseField name="label" type="string" required>
@@ -291,14 +291,14 @@

  <Expandable title="Navigation">
    <ResponseField name="global" type="object">
      Global navigation elements that appear accross all pages and sections.

      <Expandable title="Global">
        <ResponseField name="languages" type="array of object">
          Language switcher configuration for multi-language sites.

          <Expandable title="Languages">
            <ResponseField name="language" type="&quot;en&quot; | &quot;cn&quot; | &quot;zh&quot; | &quot;zh-Hans&quot; | &quot;zh-Hant&quot; | &quot;es&quot; | &quot;fr&quot; | &quot;ja&quot; | &quot;jp&quot; | &quot;pt&quot; | &quot;pt-BR&quot; | &quot;de&quot; | &quot;ko&quot; | &quot;it&quot; | &quot;ru&quot; | &quot;id&quot; | &quot;ar&quot; | &quot;tr&quot;" required>
              Language code in ISO 639-1 format
            </ResponseField>
            <ResponseField name="default" type="boolean">
@@ -525,7 +525,7 @@
  Contextual menu for AI-optimized content and integrations. 

  <Expandable title="Contextual">
    <ResponseField name="options" type="array of &quot;copy&quot; | &quot;view&quot; | &quot;chatgpt&quot; | &quot;claude&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.
@@ -543,7 +543,7 @@

 ### API Configurations

 <ResponseField name="api" type="object">
  API documentation and interactive playground settings.

  <Expandable title="Api">
@@ -962,7 +962,7 @@
      "footer": {
        "socials": {
          "x": "https://x.com/example",
          "linkedin": "https://www.linkedin.com/company/example",
          "github": "https://github.com/example",
          "slack": "https://example.com/community"
        },
@@ -1005,7 +1005,7 @@
      },
      "integrations": {
        "ga4": {
          "measurementId": "G-XXXXXXXXXX"
        },
        "koala": {
          "publicApiKey": "pk_example_key_123"
@@ -1014,8 +1014,8 @@
          "enabled": true
        },
        "cookies": {
          "key": "example_cookie_key",
          "value": "example_cookie_value"
        }
      },
      "contextual": {
@@ -1136,7 +1136,7 @@
      "footer": {
        "socials": {
          "x": "https://x.com/example",
          "linkedin": "https://www.linkedin.com/company/example",
          "github": "https://github.com/example",
          "slack": "https://example.com/community"
        },
@@ -1179,7 +1179,7 @@
      },
      "integrations": {
        "ga4": {
          "measurementId": "G-XXXXXXXXXX"
        },
        "koala": {
          "publicApiKey": "pk_example_key_123"
@@ -1188,8 +1188,8 @@
          "enabled": true
        },
        "cookies": {
          "key": "example_cookie_key",
          "value": "example_cookie_value"
        }
      },
      "contextual": {
@@ -1304,7 +1304,7 @@
      "footer": {
        "socials": {
          "x": "https://x.com/example",
          "linkedin": "https://www.linkedin.com/company/example",
          "github": "https://github.com/example",
          "slack": "https://example.com/community"
        },
@@ -1347,7 +1347,7 @@
      },
      "integrations": {
        "ga4": {
          "measurementId": "G-XXXXXXXXXX"
        },
        "koala": {
          "publicApiKey": "pk_example_key_123"
@@ -1356,8 +1356,8 @@
          "enabled": true
        },
        "cookies": {
          "key": "example_cookie_key",
          "value": "example_cookie_value"
        }
      },
      "contextual": {

diff --git a/settings/broken-links.mdx b/settings/broken-links.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Redirects and Broken Links"
+title: "Redirects and broken links"
 description: "Tools to help prevent invalid links"
 icon: 'link-2'
 ---

diff --git a/settings/ci.mdx b/settings/ci.mdx
@@ -1,5 +1,5 @@
 ---
-title: "CI Checks"
+title: "CI checks"
 description: "Add checks for broken links, linting, and grammar to the updating process"
 icon: "circle-check"
 ---

diff --git a/settings/custom-domain.mdx b/settings/custom-domain.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Custom Domain"
+title: "Custom domain"
 description: "Host your documentation at your website's custom domain"
 icon: "globe"
 ---
@@ -31,9 +31,9 @@
  />
 </Frame>

 ## Verification with Vercel

 If Vercel happens to be your domain provider, you will have to add a verification `TXT` record. This information will show on your dashboard after submitting your custom domain, as well as be emailed to you.

 ## Configuring your DNS


diff --git a/settings/custom-scripts.mdx b/settings/custom-scripts.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Custom Scripts'
+title: 'Custom scripts'
 description: 'Fully customize your documentation with custom CSS and JS'
 icon: "code"
 ---
@@ -12,7 +12,7 @@

 ### Adding `style.css`

 For example, you can add the following `style.css` file to customize the styling of the navbar and footer.

 ```css
 #navbar {
@@ -50,7 +50,7 @@
  - Header: `header`
  - NavBarTransition: `navbar-transition`
  - NavigationItems: `navigation-items`
  - Navbar: `navbar`
  - PageContextMenu: `page-context-menu`
  - PageContextMenuButton: `page-context-menu-button`
  - PageTitle: `page-title`
@@ -76,11 +76,11 @@
  - AlmondNavBottomSectionDivider: `almond-nav-bottom-section-divider`
  - Anchor: `nav-anchor`
  - Anchors: `nav-anchors`
  - APISection: `api-section`
  - APISectionHeading: `api-section-heading`
  - APISectionHeadingSubtitle: `api-section-heading-subtitle`
  - APISectionHeadingTitle: `api-section-heading-title`
  - Callout: `callout`
  - Card: `card`
  - CardGroup: `card-group`
  - ChatAssistantSheet: `chat-assistant-sheet`
@@ -130,7 +130,7 @@
  - TabsBarItem: `nav-tabs-item`
  - TableOfContents: `toc`
  - TableOfContentsItem: `toc-item`
  - Tooltip: `tooltip`
  - TopbarRightContainer: `topbar-right-container`
  - TryitButton: `tryit-button`
  - Update: `update`

diff --git a/settings/preview-deployments.mdx b/settings/preview-deployments.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Preview Deployments"
+title: "Preview deployments"
 description: "Preview changes to your docs in a live deployment"
 icon: "scan-eye"
 ---

diff --git a/text.mdx b/text.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Headers and Text"
+title: "Headers and text"
 description: "Text, title, and styling in standard markdown"
 icon: 'heading'
 ---
@@ -91,7 +91,7 @@

 ### Line Breaks

 Markdown syntax also recognizes a double enter in your MDX as a linebreak.

 ```html
 <br />