mintlify · mintlify · Jul 11, 2025 · Jul 11, 2025 · Jul 11, 2025 · Jul 11, 2025
diff --git a/advanced/subpath/route53-cloudfront.mdx b/advanced/subpath/route53-cloudfront.mdx
@@ -1,34 +1,34 @@
 ---
-title: "AWS Route 53 and Cloudfront"
+title: "AWS Route 53 and CloudFront"
 sidebarTitle: "AWS"
 description: "Host documentation at a /docs subdirectory using AWS services"
 ---
 
 import Propagating from "/snippets/custom-subpath-propagating.mdx";
 
-## Create Cloudfront Distribution
+## Create CloudFront Distribution
 
-Navigate to [Cloudfront](https://aws.amazon.com/cloudfront) inside the AWS console and click on `Create distribution`
+Navigate to [CloudFront](https://aws.amazon.com/cloudfront) inside the AWS console and click on `Create distribution`
 
 <Frame>
-  ![Cloudfront Create Distribution](/images/cloudfront/create-distribution.png)
+  ![CloudFront Create Distribution](/images/cloudfront/create-distribution.png)
 </Frame>
 
 For the Origin domain, input `[SUBDOMAIN].mintlify.dev` where `[SUBDOMAIN]` is the project's unique subdomain. Click on `Use: [SUBDOMAIN].mintlify.dev`
 
-<Frame>![Cloudfront Origin name](/images/cloudfront/origin-name.png)</Frame>
+<Frame>![CloudFront Origin name](/images/cloudfront/origin-name.png)</Frame>
 
 For **Cache key and origin requests**, select `Caching Optimized`.
 
 <Frame>
-  ![Cloudfront Caching policy](/images/cloudfront/caching-policy.png)
+  ![CloudFront Caching policy](/images/cloudfront/caching-policy.png)
 </Frame>
 
 And for **Web Application Firewall (WAF)**, enable security protections
 
 <Frame>
-  ![Cloudfront Caching
-  policy](/images/cloudfront/enable-security-protections.png)
+  ![CloudFront Security
+  protections](/images/cloudfront/enable-security-protections.png)
 </Frame>
 
 The remaining settings should be default. Click `Create distribution`.
@@ -37,15 +37,15 @@
 
 After creating the distribution, navigate to the `Origins` tab.
 
-<Frame>![Cloudfront Origins](/images/cloudfront/origins.png)</Frame>
+<Frame>![CloudFront Origins](/images/cloudfront/origins.png)</Frame>
 
-We want to find a staging URL that mirrors where the main domain (example.com). This is highly variant depending on how your landing page is hosted.
+We want to find a staging URL that mirrors the main domain (example.com). This is highly variant depending on how your landing page is hosted.
 
 <Info>
-For instance, if your landing page is hosted on Webflow, you can use the
+For instance, if your landing page is hosted on Webflow, you can use
 Webflow's staging URL. It would look like `.webflow.io`.
 
 If you use Vercel, you use the `.vercel.app` domain available for every project.

 </Info>
 <Note>
@@ -58,46 +58,46 @@
 Once you have the staging URL, ours for instance is [mintlify-landing-page.vercel.app](https://mintlify-landing-page.vercel.app), create a new Origin and add it as the **Origin domain**.
 
 <Frame>
-  ![Cloudfront Default Origins](/images/cloudfront/default-origin.png)
+  ![CloudFront Default Origins](/images/cloudfront/default-origin.png)
 </Frame>
 
-By this point, you should have two Origins - one with `[SUBDOMAIN].mintlify.app` and another with with staging URL.
+By this point, you should have two Origins - one with `[SUBDOMAIN].mintlify.dev` and another with the staging URL.
 
 ## Set Behaviors
 
-Behaviors in Cloudfront enables control over the subpath logic. At a high level, we're looking to create the following logic.
+Behaviors in CloudFront enable control over the subpath logic. At a high level, we're looking to create the following logic.
 
 - **If a user lands on /docs**, go to `[SUBDOMAIN].mintlify.dev`
-- **If a user lands on any other page**, go the current landing page
+- **If a user lands on any other page**, go to the current landing page
 
 We're going to create three behaviors by clicking on the `Create behavior` button.
 
 ### `/docs/*`
 
 The first behavior should have a **Path pattern** of `/docs/*` with **Origin and origin groups** pointing to the `.mintlify.dev` URL (in our case `acme.mintlify.dev`)
 
-<Frame>![Cloudfront Behavior 1](/images/cloudfront/behavior-1.png)</Frame>
+<Frame>![CloudFront Behavior 1](/images/cloudfront/behavior-1.png)</Frame>
 
 For **Cache policy**, select `CachingOptimized` and create behavior.
 
 ### `/docs`
 
 The second behavior should be the same as the first one but with a **Path pattern** of `/docs` and **Origin and origin groups** pointing to the same `.mintlify.dev` URL.
 
-<Frame>![Cloudfront Behavior 2](/images/cloudfront/behavior-2.png)</Frame>
+<Frame>![CloudFront Behavior 2](/images/cloudfront/behavior-2.png)</Frame>
 
 ### `Default (*)`
 
 Lastly, we're going to edit the `Default (*)` behavior.
 
 <Frame>
-  ![Cloudfront Behavior Default 1](/images/cloudfront/default-behavior-1.png)
+  ![CloudFront Behavior Default 1](/images/cloudfront/default-behavior-1.png)
 </Frame>
 
 We're going to change the default behavior's **Origin and origin groups** to the staging URL (in our case `mintlify-landing-page.vercel.app`).
 
 <Frame>
-  ![Cloudfront Behavior Default 2](/images/cloudfront/default-behavior-2.png)
+  ![CloudFront Behavior Default 2](/images/cloudfront/default-behavior-2.png)
 </Frame>
 
 Click on `Save changes`.
@@ -107,23 +107,23 @@
 You can now test if your distribution is set up properly by going to the `General` tab and visiting the **Distribution domain name** URL.
 
 <Frame>
-  ![Cloudfront Preview
+  ![CloudFront Preview
   distribution](/images/cloudfront/preview-distribution.png)
 </Frame>
 
 All pages should be directing to your main landing page, but if you append `/docs` to the URL, you should see it going to the Mintlify documentation instance.
 
-## Connecting it with Route53
+## Connecting it with Route 53
 
-Now, we're going to bring the functionality of the Cloudfront distribution into your primary domain.
+Now, we're going to bring the functionality of the CloudFront distribution into your primary domain.
 
 <Note>
   For this section, you can also refer to AWS's official guide on [Configuring
   Amazon Route 53 to route traffic to a CloudFront
   distribution](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-cloudfront-distribution.html#routing-to-cloudfront-distribution-config)
 </Note>
 
-Navigate to [Route53](https://aws.amazon.com/route53) inside the AWS console, and click into the `Hosted zone` for your primary domain. Click on `Create record`
+Navigate to [Route 53](https://aws.amazon.com/route53) inside the AWS console, and click into the `Hosted zone` for your primary domain. Click on `Create record`
 
 <Frame>
   ![Route 53 create record](/images/cloudfront/route53-create-record.png)

diff --git a/advanced/subpath/vercel.mdx b/advanced/subpath/vercel.mdx
@@ -1,11 +1,11 @@
 ---
 title: "Vercel"
 description: "Host documentation at a /docs subpath using Vercel"
 ---

 ## vercel.json Configuration

 To host your documentation at a custom subpath using Vercel, you need to add the
 following configuration to your `vercel.json` file.

 ```json
@@ -24,7 +24,7 @@
 ```
 
 <Note>
-  For more information, you can also refer to Vercel's offical guide on
+  For more information, you can also refer to Vercel's official guide on
   rewrites: [Project Configuration:
   Rewrites](https://vercel.com/docs/projects/project-configuration#rewrites)
 </Note>
diff --git a/ai-ingestion.mdx b/ai-ingestion.mdx
@@ -1,6 +1,6 @@
 ---
 title: "AI ingestion"
 description: "Prepare your documentation for LLMs and AI tools"
 icon: "bot-message-square"
 ---

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

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

 ## Contextual menu

@@ -42,8 +42,8 @@
   "options": [
     "copy",
     "view",
     "chatgpt",
     "claude",
     "perplexity"
   ]
 }
@@ -143,6 +143,6 @@
 
 <PreviewButton href="https://mintlify.com/docs/quickstart.md">Open quickstart.md</PreviewButton>
 
-### Command \+ C shortcut
+### Command + C shortcut
 
-Select Command \+ C (Ctrl \+ C on Windows) to copy any page as Markdown.
+Select Command + C (Ctrl + C on Windows) to copy any page as Markdown.
diff --git a/analytics/analytics-api-reference.mdx b/analytics/analytics-api-reference.mdx
diff --git a/analytics/analytics-api.mdx b/analytics/analytics-api.mdx
diff --git a/analytics/analytics.mdx b/analytics/analytics.mdx
diff --git a/analytics/event-tracking.mdx b/analytics/event-tracking.mdx
diff --git a/api-playground/asyncapi/playground.mdx b/api-playground/asyncapi/playground.mdx
@@ -1,5 +1,5 @@
 ---
 title: "Playground"
-description: "Enable users to interact with your websockets"
+description: "Enable users to interact with your WebSockets"
 asyncapi: "/asyncapi.yaml channelOne"
 ---
diff --git a/api-playground/customization.mdx b/api-playground/customization.mdx
diff --git a/api-playground/customization/complex-data-types.mdx b/api-playground/customization/complex-data-types.mdx
@@ -56,7 +56,7 @@

 ### Providing options with `oneOf` and `anyOf`

 When you use `oneOf` or `anyOf`, the options are displayed in a tabbed container. Specify a `title` field in each subschema to give your options names. For example, here's how you might display two different types of delivery addresses:

 ```yaml
 delivery_address:
@@ -82,7 +82,7 @@
     <Tabs>
       <Tab title="StreetAddress">
         <ParamField body="address_line_1" type="string">
-          The street address of the residence
+          The street address of the recipient
         </ParamField>
       </Tab>
       <Tab title="POBox">

diff --git a/api-playground/openapi-setup.mdx b/api-playground/openapi-setup.mdx
@@ -8,7 +8,7 @@
 
 ## Add an OpenAPI specification file
 
-To document your endpoints with OpenAPI, you need a valid OpenAPI document in either JSON or YAML format that follows the [OpenAPI specification 3.0\+](https://swagger.io/specification/).
+To document your endpoints with OpenAPI, you need a valid OpenAPI document in either JSON or YAML format that follows the [OpenAPI specification 3.0+](https://swagger.io/specification/).
 
 ### Describing your API
 
@@ -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/api-playground/playground-api.mdx b/api-playground/playground-api.mdx
diff --git a/api-playground/set-up.mdx b/api-playground/set-up.mdx
diff --git a/api-playground/troubleshooting.mdx b/api-playground/troubleshooting.mdx
@@ -18,7 +18,7 @@ If your API pages aren't displaying correctly, check these common configuration
     1. Visit [this validator](https://editor.swagger.io/)
     2. Switch to the "Validate text" tab
     3. Paste in your OpenAPI document
-    4. Click "Validate it\!"
+    4. Click "Validate it!"
 
     If the text box that appears below has a green border, your document has passed validation.
     This is the exact validation package Mintlify uses to validate OpenAPI documents, so if your document

diff --git a/api-reference/generation.mdx b/api-reference/generation.mdx
diff --git a/api-reference/languages.mdx b/api-reference/languages.mdx
diff --git a/api-reference/openapi.mdx b/api-reference/openapi.mdx
diff --git a/api-reference/parameters.mdx b/api-reference/parameters.mdx
diff --git a/api-reference/settings.mdx b/api-reference/settings.mdx
diff --git a/changelog.mdx b/changelog.mdx
@@ -4,17 +4,17 @@
 rss: true
 ---

 <Update label="June 2025" rss={{ title: "June Product Updates", description: "AI assistant updates and subscribable changelogs" }}>
  ## AI assistant updates

  - Improved accuracy through agentic RAG with tool calling
  - Provides navigable links to referenced pages so that users can go directly to the source of answers
  - Copy shortcut for code examples generated by assistant
  - "Ask AI" shortcut on code blocks in documentation to generate explanations from the assistant

  Learn more in the [assistant docs](/guides/assistant).

  ## Subscribable changelogs
  - Automatically generate an RSS feed from changelog pages
  - Integrate RSS-enabled updates with Slack, email, and other tools

@@ -33,7 +33,7 @@
   Learn more at [API playground docs.](/api-playground/)
 
   ## `mint update`
-  Can now use `mint update` to update your CLI.
+  You can now use `mint update` to update your CLI.
 </Update>
 
 <Update label="April 2025">
@@ -101,7 +101,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">
@@ -132,9 +132,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

@@ -216,7 +216,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

@@ -288,7 +288,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.
@@ -302,7 +302,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.
@@ -335,7 +335,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

@@ -369,7 +369,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.

@@ -402,7 +402,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)
@@ -437,7 +437,7 @@
 <Update label="May 2024">
  ## Okta SSO

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

  ## Mintlify REST API

@@ -460,7 +460,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">
@@ -469,7 +469,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/code.mdx b/code.mdx
@@ -57,7 +57,7 @@

 Enable syntax highlighting by specifying the programming language after the opening backticks of a code block.

 We use [Shiki](https://shiki.style/) for syntax highlighting and support all available languages. See the full list of [languages](https://shiki.style/languages) in Shiki's documentation.

 ```java
 class HelloWorld {
@@ -109,7 +109,7 @@
 
 Highlight specific lines in your code blocks using `highlight` with the line numbers or ranges you want to highlight.
 
-```javascript Line Highlighting Example highlight= {1-2,5}
+```javascript Line Highlighting Example highlight={1-2,5}
 const greeting = "Hello, World!";
 function sayHello() {
   console.log(greeting);
@@ -131,7 +131,7 @@
 
 Focus on specific lines in your code blocks using `focus` with line numbers or ranges.
 
-```javascript Line Focus Example focus= {2,4-5}
+```javascript Line Focus Example focus={2,4-5}
 const greeting = "Hello, World!";
 function sayHello() {
   console.log(greeting);

diff --git a/components/accordion.mdx b/components/accordion.mdx
diff --git a/components/callouts.mdx b/components/callouts.mdx
@@ -1,10 +1,10 @@
 ---
 title: 'Callouts'
 description: 'Use callouts to add eye-catching context to your content'
 icon: 'info'
 ---

 Callouts can be styled as a Note, Warning, Info, Tip, or Check:

 <Note>This adds a note in the content</Note>

@@ -30,10 +30,10 @@
 <Tip>This suggests a helpful tip</Tip>
 ```
 
-<Check>This brings us a checked status</Check>
+<Check>This brings a checked status</Check>
 
 ```mdx
-<Check>This brings us a checked status</Check>
+<Check>This brings a checked status</Check>
 ```
 
 <Danger>This is a danger callout</Danger>

diff --git a/components/card-group.mdx b/components/card-group.mdx
diff --git a/components/card.mdx b/components/card.mdx
diff --git a/components/code-group.mdx b/components/code-group.mdx
diff --git a/components/code.mdx b/components/code.mdx
diff --git a/components/examples.mdx b/components/examples.mdx
@@ -17,7 +17,7 @@ On mobile devices, `<RequestExample>` and `<ResponseExample>` components display
 
 ## RequestExample
 
-Use `<RequestExample>` to pins code examples in the right sidebar. This component works similarly to the [CodeGroup](/components/code-groups) component, but displays the code in the sidebar instead of inline.
+Use `<RequestExample>` to pin code examples in the right sidebar. This component works similarly to the [CodeGroup](/components/code-groups) component, but displays the code in the sidebar instead of inline.
 
 You can include multiple code blocks inside a single `<RequestExample>`. Each code block must have a title attribute.
 

diff --git a/components/frame.mdx b/components/frame.mdx
diff --git a/components/frames.mdx b/components/frames.mdx
@@ -14,8 +14,8 @@ Frames are very helpful if you want to center an image.
 
 You can add additional context to an image using the optional `caption` prop.
 
-<Frame caption="Yosemite National Park is visited by over 3.5 million people every year">
-  <img src="https://mintlify-assets.b-cdn.net/yosemite.jpg" />
+<Frame caption="Yellowstone National Park is visited by over 3.5 million people every year">
+  <img src="https://mintlify-assets.b-cdn.net/yellowstone.jpeg" />
 </Frame>
 
 ## Props

diff --git a/components/frequently-asked-questions.mdx b/components/frequently-asked-questions.mdx
diff --git a/components/images.mdx b/components/images.mdx
diff --git a/components/mint-components-list.mdx b/components/mint-components-list.mdx
diff --git a/components/snippets.mdx b/components/snippets.mdx
diff --git a/components/steps.mdx b/components/steps.mdx
@@ -4,7 +4,7 @@
 icon: 'list-todo'
 ---
 
-Steps are the best way to display a series of actions of events to your users. You can add as many steps as desired.
+Steps are the best way to display a series of actions or events to your users. You can add as many steps as desired.
 
 <Steps>
   <Step title="First Step">
@@ -53,7 +53,7 @@
 </ResponseField>

 <ResponseField name="icon" type="string or svg">
  A [Font Awesome icon](https://fontawesome.com/icons), [Lucide icon](https://lucide.dev/icons), or SVG code in `icon={}`
 </ResponseField>

 <ResponseField name="iconType" type="string">

diff --git a/components/tables.mdx b/components/tables.mdx
diff --git a/components/video.mdx b/components/video.mdx
diff --git a/content-management/hosting-videos.mdx b/content-management/hosting-videos.mdx
diff --git a/deployments/custom-domains.mdx b/deployments/custom-domains.mdx
diff --git a/deployments/git-sync.mdx b/deployments/git-sync.mdx
diff --git a/deployments/hosting.mdx b/deployments/hosting.mdx
diff --git a/development/astro.mdx b/development/astro.mdx
diff --git a/development/code-block-components.mdx b/development/code-block-components.mdx
diff --git a/development/custom-components.mdx b/development/custom-components.mdx
diff --git a/development/custom-css.mdx b/development/custom-css.mdx
diff --git a/development/introduction.mdx b/development/introduction.mdx
diff --git a/development/mdx-support.mdx b/development/mdx-support.mdx
diff --git a/development/nextjs.mdx b/development/nextjs.mdx
diff --git a/development/presentation-components.mdx b/development/presentation-components.mdx
diff --git a/development/tailwindcss.mdx b/development/tailwindcss.mdx
diff --git a/development/typescript.mdx b/development/typescript.mdx
diff --git a/development/ui-components.mdx b/development/ui-components.mdx
diff --git a/faqs.mdx b/faqs.mdx
diff --git a/get-started.mdx b/get-started.mdx
diff --git a/guides/assistant.mdx b/guides/assistant.mdx
@@ -12,7 +12,7 @@
 
 The assistant answers questions about your documentation through natural language queries. It is embedded directly in your documentation site, providing users with immediate access to contextual help.
 
-The assistant uses agentic RAG (retrieval-augmented generation) with tool calling powered by Claude Sonnet 4. When users ask questions, the assistant:
+The assistant uses agentic RAG (retrieval-augmented generation) with tool calling powered by Claude 3.5 Sonnet. When users ask questions, the assistant:
 
 * **Searches and retrieves** relevant content from your documentation to provide accurate answers.
 * **Cites sources** and provides navigable links to take users directly to referenced pages.
@@ -28,7 +28,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"
@@ -51,7 +51,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.

@@ -60,7 +60,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>

@@ -94,7 +94,7 @@
 
 ## Changing the model
 
-The assistant uses Claude Sonnet 4 by default. We have found that this model performs the best when searching and answering questions.
+The assistant uses Claude 3.5 Sonnet by default. We have found that this model performs the best when searching and answering questions.
 
 If you want to select another model:
 
@@ -126,7 +126,7 @@
     }
   />
   <Card
-    title="Claude 3.7 Sonnet"
+    title="Claude 3.5 Sonnet"
     horizontal
     icon={
       <svg
@@ -145,7 +145,7 @@
     }
   />
   <Card
-    title="GPT 4.1"
+    title="GPT-4o"
     horizontal
     icon={
       <svg

diff --git a/integrations/analytics/hotjar.mdx b/integrations/analytics/hotjar.mdx
@@ -1,8 +1,8 @@
 ---
-title: "HotJar"
+title: "Hotjar"
 ---
 
-Add the following to your `docs.json` file to send analytics to HotJar.
+Add the following to your `docs.json` file to send analytics to Hotjar.
 
 ```json Analytics options in docs.json
 "integrations": {

diff --git a/integrations/analytics/posthog.mdx b/integrations/analytics/posthog.mdx
@@ -35,4 +35,4 @@ You only need to include `apiHost` if you are self-hosting PostHog. We send even
 
 ## Session Recordings
 
-You need to add the URL for your docs website to Posthog's "Authorized domains for recordings" before you can receive session recordings. The option to add your URL is in Posthog's project settings.
+You need to add the URL for your docs website to PostHog's "Authorized domains for recordings" before you can receive session recordings. The option to add your URL is in PostHog's project settings.
diff --git a/integrations/privacy/osano.mdx b/integrations/privacy/osano.mdx
@@ -1,5 +1,5 @@
 ---
 title: "Osano"
 ---

 Add the following to your `docs.json` file to add the [Osano](https://www.osano.com/) cookie consent manager.
@@ -14,13 +14,13 @@
 
 ```json Example
 "integrations": {
-    "osano": "https://cmp.osano.com/2sUB2dqwqdkks/8dqwd-dwd86£-4a9b/osano.js"
+    "osano": "https://cmp.osano.com/2sUB2dqwqdkks/8dqwd-dwd86-4a9b/osano.js"
 }
 ```
 
 </CodeGroup>

 The `SOURCE` can be found as the `src` value in the code snippet generated by Osano. It always starts with `https://cmp.osano.com/`.

 ```html Code snippet from Osano
 <script src="https://cmp.osano.com/placeholder/placeholder/osano.js"/>

diff --git a/integrations/sdks/speakeasy.mdx b/integrations/sdks/speakeasy.mdx
@@ -3,11 +3,11 @@
 description: Automate your SDK usage snippets in the API playground
 ---

 You can integrate Speakeasy-generated code snippets from your SDKs directly into your Mintlify API reference documentation. SDK usage snippets are shown in the [interactive playground](https://mintlify.com/docs/api-playground/overview) of your Mintlify-powered documentation.

 ## Speakeasy SDK Repository Changes

 In your Speakeasy SDK repos, add the following to the `targets` section of your `.speakeasy/workflow.yaml` file to ensure code samples are automatically produced alongside SDK generations.

 ```yaml .speakeasy/workflow.yaml
 targets:
@@ -45,7 +45,7 @@
 
 ![](/images/speakeasy-3.webp)
 
-Finally, Add your `SPEAKEASY_API_KEY` as a repository secret to your Minlify repo under `Settings > Secrets & Variables > Actions`. Find the Speakeasy API key in the Speakeasy dashboard under the **API Keys** tab.
+Finally, add your `SPEAKEASY_API_KEY` as a repository secret to your Mintlify repo under `Settings > Secrets & Variables > Actions`. Find the Speakeasy API key in the Speakeasy dashboard under the **API Keys** tab.
 
 ## Manual Set Up
 
@@ -66,7 +66,7 @@
 targets: {}
 ```
 
-```yaml .speakeasy/workflows/sdk_generation.yaml
+```yaml .github/workflows/sdk_generation.yaml
 name: Generate
 permissions:
   checks: write
@@ -94,4 +94,4 @@
       speakeasy_api_key: ${{ secrets.SPEAKEASY_API_KEY }}
 ```
 
-Finally, make sure you add your `SPEAKEASY_API_KEY` as a repository secret to your Minlify repo under `Settings > Secrets & Variables > Actions`. Find the Speakeasy API key in the Speakeasy dashboard under the **API Keys** tab.
+Finally, make sure you add your `SPEAKEASY_API_KEY` as a repository secret to your Mintlify repo under `Settings > Secrets & Variables > Actions`. Find the Speakeasy API key in the Speakeasy dashboard under the **API Keys** tab.
diff --git a/introduction.mdx b/introduction.mdx
diff --git a/localizations/i18n.mdx b/localizations/i18n.mdx
diff --git a/navigation/anchors.mdx b/navigation/anchors.mdx
diff --git a/navigation/folders.mdx b/navigation/folders.mdx
diff --git a/navigation/global.mdx b/navigation/global.mdx
diff --git a/navigation/mdx-page.mdx b/navigation/mdx-page.mdx
diff --git a/navigation/multiple-versions.mdx b/navigation/multiple-versions.mdx
diff --git a/navigation/navigation.mdx b/navigation/navigation.mdx
diff --git a/navigation/page-titles.mdx b/navigation/page-titles.mdx
diff --git a/navigation/redirects.mdx b/navigation/redirects.mdx
diff --git a/navigation/setting-up-search.mdx b/navigation/setting-up-search.mdx
diff --git a/navigation/versioning.mdx b/navigation/versioning.mdx
diff --git a/reusable-snippets.mdx b/reusable-snippets.mdx
@@ -40,7 +40,7 @@ import MySnippet from '/snippets/path/to/my-snippet.mdx';
 
 ## Header
 
-Lorem impsum dolor sit amet.
+Lorem ipsum dolor sit amet.
 
 <MySnippet/>
 
@@ -67,7 +67,7 @@ import MySnippet from '/snippets/path/to/my-snippet.mdx';
 
 ## Header
 
-Lorem impsum dolor sit amet.
+Lorem ipsum dolor sit amet.
 
 <MySnippet word="bananas" />
 

diff --git a/settings.mdx b/settings.mdx
@@ -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
 {
@@ -158,7 +158,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.
@@ -263,12 +263,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>
@@ -306,7 +306,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">
@@ -540,7 +540,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.
@@ -559,7 +559,7 @@

 ### API Configurations

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

  <Expandable title="Api">
@@ -978,7 +978,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"
        },
@@ -1021,7 +1021,7 @@
      },
      "integrations": {
        "ga4": {
          "measurementId": "G-XXXXXXXXXX"
        },
        "koala": {
          "publicApiKey": "pk_example_key_123"
@@ -1030,8 +1030,8 @@
          "enabled": true
        },
        "cookies": {
          "key": "example_cookie_key",
          "value": "example_cookie_value"
        }
      },
      "contextual": {
@@ -1152,7 +1152,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"
        },
@@ -1195,7 +1195,7 @@
      },
      "integrations": {
        "ga4": {
          "measurementId": "G-XXXXXXXXXX"
        },
        "koala": {
          "publicApiKey": "pk_example_key_123"
@@ -1204,8 +1204,8 @@
          "enabled": true
        },
        "cookies": {
          "key": "example_cookie_key",
          "value": "example_cookie_value"
        }
      },
      "contextual": {
@@ -1290,10 +1290,10 @@
              {
                "dropdown": "Documentación",
                "icon": "book",
                "description": "Cómo usar el producto de Example Co.",
                "pages": [
                  {
                    "group": "Comenzando",
                    "pages": ["es/index", "es/quickstart"]
                  },
                  {
@@ -1313,7 +1313,7 @@
              {
                "dropdown": "Changelog",
                "icon": "history",
                "description": "Actualizaciones y cambios",
                "pages": ["es/changelog"]
              }
            ]
@@ -1341,7 +1341,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"
        },
@@ -1384,7 +1384,7 @@
      },
      "integrations": {
        "ga4": {
          "measurementId": "G-XXXXXXXXXX"
        },
        "koala": {
          "publicApiKey": "pk_example_key_123"
@@ -1393,8 +1393,8 @@
          "enabled": true
        },
        "cookies": {
          "key": "example_cookie_key",
          "value": "example_cookie_value"
        }
      },
      "contextual": {

diff --git a/settings/api-reference.mdx b/settings/api-reference.mdx
diff --git a/settings/billing.mdx b/settings/billing.mdx
diff --git a/settings/ci.mdx b/settings/ci.mdx
@@ -51,7 +51,7 @@ To see the results of this check, you can visit GitHub's check results page for
 Mintlify supports automatically running Vale in a CI check, and displaying the results as a check status.
 
 #### Configuration
-If you have a `.vale.ini` file in the root the content directory for your deployment, we will automatically use that configuration file.
+If you have a `.vale.ini` file in the root of the content directory for your deployment, we will automatically use that configuration file.
 We will also automatically use any configuration files in your specified `stylesPath`.
 
 <Tip>Don't have a Vale config or not sure where to get started? Don't worry, Mintlify has a default configuration that will automatically be used if one is not provided.</Tip>

diff --git a/settings/code.mdx b/settings/code.mdx
diff --git a/settings/colors.mdx b/settings/colors.mdx
diff --git a/settings/custom-scripts.mdx b/settings/custom-scripts.mdx
@@ -28,11 +28,11 @@

 ### Adding `style.css`

 For example, you can add the following `style.css` file to customize the styling of the navbar and footer.
 
 ```css
 #navbar {
-  background: "#fffff2";
+  background: #fffff2;
   padding: 1rem;
 }
 
@@ -66,7 +66,7 @@
  - Header: `header`
  - NavBarTransition: `navbar-transition`
  - NavigationItems: `navigation-items`
  - Navbar: `navbar`
  - PageContextMenu: `page-context-menu`
  - PageContextMenuButton: `page-context-menu-button`
  - PageTitle: `page-title`
@@ -92,11 +92,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`
@@ -146,7 +146,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/development.mdx b/settings/development.mdx
diff --git a/settings/favicon.mdx b/settings/favicon.mdx
diff --git a/settings/fonts.mdx b/settings/fonts.mdx
diff --git a/settings/footer.mdx b/settings/footer.mdx
Original file line number	Diff line number	Diff line change
Expand Up		@@ -35,4 +35,4 @@ You only need to include `apiHost` if you are self-hosting PostHog. We send even

		## Session Recordings

		You need to add the URL for your docs website to Posthog's "Authorized domains for recordings" before you can receive session recordings. The option to add your URL is in Posthog's project settings.
		You need to add the URL for your docs website to PostHog's "Authorized domains for recordings" before you can receive session recordings. The option to add your URL is in PostHog's project settings.