diff --git a/.mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx b/.mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx index ea0246620b..0e3044b5d5 100644 --- a/.mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx +++ b/.mintlify/assistant/skills/custom-domain-rate-limit/skill.mdx @@ -1,6 +1,6 @@ --- name: "custom-domain-rate-limit" -description: "Use this skill when a user is setting up a custom domain and the _acme-challenge TXT record value never appears in the Mintlify dashboard — the dashboard shows a loading spinner, a blank field, or the value keeps changing on each attempt. This is caused by a Let's Encrypt certificate issuance rate limit from repeated failed validation attempts." +description: "Use this skill when a user is setting up a custom domain and the _acme-challenge TXT record value never appears in the Mintlify dashboard. The dashboard shows a loading spinner, a blank field, or the value keeps changing on each attempt. This is caused by a Let's Encrypt certificate issuance rate limit from repeated failed validation attempts." --- # Custom domain _acme-challenge value not appearing diff --git a/.mintlify/assistant/skills/editor-reset/skill.mdx b/.mintlify/assistant/skills/editor-reset/skill.mdx index de44f1cbf0..5d564b0242 100644 --- a/.mintlify/assistant/skills/editor-reset/skill.mdx +++ b/.mintlify/assistant/skills/editor-reset/skill.mdx @@ -5,7 +5,7 @@ description: "Use this skill when a user reports that the Mintlify web editor is # Reset the editor -A force reset usually fixes a web editor that is broken, showing stale content, or failing to load the file tree — especially after a Git sync. Resetting clears local editor state without affecting published docs or Git history. +A force reset usually fixes a web editor that is broken, showing stale content, or failing to load the file tree, especially after a Git sync. Resetting clears local editor state without affecting published docs or Git history. Walk the user through these steps: @@ -16,4 +16,4 @@ Walk the user through these steps: The editor reloads and re-syncs from the Git repository. -If the issue persists after resetting, it may indicate a deeper sync conflict — escalate to the support team. +If the issue persists after resetting, it may indicate a deeper sync conflict. Escalate to the support team. diff --git a/.mintlify/assistant/skills/git-revalidation/skill.mdx b/.mintlify/assistant/skills/git-revalidation/skill.mdx index b79efa07b8..62d2bdc722 100644 --- a/.mintlify/assistant/skills/git-revalidation/skill.mdx +++ b/.mintlify/assistant/skills/git-revalidation/skill.mdx @@ -1,11 +1,11 @@ --- name: "git-revalidation" -description: "Use this skill when a user reports that GitHub-dependent features have stopped working after they changed their repository from private to public or vice versa — Suggest Edits isn't showing on their docs, PR previews aren't generating, or branch options appear stale. Also applies when the Git connection appears stale or broken." +description: "Use this skill when a user reports that GitHub-dependent features have stopped working after they changed their repository from private to public or vice versa: Suggest Edits isn't showing on their docs, PR previews aren't generating, or branch options appear stale. Also applies when the Git connection appears stale or broken." --- # Revalidate the Git connection -When a repository's visibility changes (private to public or public to private), Mintlify's cached understanding of the repo's permissions becomes outdated. Features that depend on the GitHub connection — Suggest Edits, PR previews, branch syncing — can appear broken until the cache catches up to the new visibility state. +When a repository's visibility changes (private to public or public to private), Mintlify's cached understanding of the repo's permissions becomes outdated. Features that depend on the GitHub connection, such as Suggest Edits, PR previews, and branch syncing, can appear broken until the cache catches up to the new visibility state. Before recommending revalidation, check which direction the visibility changed: diff --git a/ai/model-context-protocol.mdx b/ai/model-context-protocol.mdx index 6452fca0ea..cba4216de8 100644 --- a/ai/model-context-protocol.mdx +++ b/ai/model-context-protocol.mdx @@ -201,7 +201,7 @@ MCP clients can use these annotations to surface tool safety information to user ### Enable authenticated MCP -If your site requires authentication, your search MCP server requires users to authenticate before connecting. When a user adds your MCP server URL to their AI tool, they must log in with their existing credentials. After authentication, a redirect sends them back to their tool. The MCP server returns only the content each user has permission to access based on their [user groups](/deploy/authentication-setup). +If your site requires authentication, your search MCP server requires users to authenticate before connecting. When a user adds your MCP server URL to their AI tool, they must sign in with their existing credentials. After authentication, a redirect sends them back to their tool. The MCP server returns only the content each user has permission to access based on their [user groups](/deploy/authentication-setup). If your site has partial authentication with both public and protected pages, you have two search MCP server endpoints: diff --git a/api-playground/troubleshooting.mdx b/api-playground/troubleshooting.mdx index 0a4d71a539..8c375c3962 100644 --- a/api-playground/troubleshooting.mdx +++ b/api-playground/troubleshooting.mdx @@ -79,7 +79,7 @@ If your API pages aren't displaying correctly, check these common configuration For a full diagnostic walkthrough, including intermittent failures caused by CI publishing the spec after triggering the build, see [Build fails with "Failed to fetch OpenAPI file for anchor or tab"](/help-center/openapi-url-fetch-fails-during-build). - + If you use a custom domain, your reverse proxy might cause this issue. By default, the API Playground starts requests with a `POST` request to the `/_mintlify/api/request` path on the docs site. If your reverse proxy allows only `GET` requests, all of these requests fail. Configure your diff --git a/assistant/use.mdx b/assistant/use.mdx index 1a98cebbaa..271a695fa8 100644 --- a/assistant/use.mdx +++ b/assistant/use.mdx @@ -8,7 +8,7 @@ You have multiple ways to start a conversation with the assistant. Each method o ## Use the assistant in local preview -The assistant is available in your local preview when you log in with the CLI. This lets you test assistant behavior, custom instructions in `Assistant.md`, and responses while developing documentation locally. +The assistant is available in your local preview when you sign in with the CLI. This lets you test assistant behavior, custom instructions in `Assistant.md`, and responses while developing documentation locally. 1. If you haven't already, install the CLI with `npm i -g mint`. 2. Run `mint login` to authenticate. diff --git a/changelog.mdx b/changelog.mdx index 42d8adc3ed..2b91e1a875 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -750,7 +750,7 @@ noindex: true ## Editor improvements - - **Drafts and publishing flow:** Make changes in a draft, request review, and publish — all from the [web editor](/editor). Drafts autocommit as you work, and renaming or updating a draft updates the underlying pull request. + - **Drafts and publishing flow:** Make changes in a draft, request review, and publish, all from the [web editor](/editor). Drafts autocommit as you work, and renaming or updating a draft updates the underlying pull request. - **Create non-`.mdx` files:** Add JSON, YAML, and other supported file types directly from the editor file tree. - **Topbar redesign:** A cleaner editor topbar with reorganized controls. - **Faster initial load:** The editor's first file and navigation load is significantly faster, with prefetching for visible nav tree pages. @@ -920,7 +920,7 @@ noindex: true The [editor](https://www.mintlify.com/docs/editor) has been redesigned for live collaboration, parsing, and stability. Additional improvements include: - - **Agent panel**: Chat with the editor agent inline — attach files, view per-session diffs, leave feedback, and jump to the page the agent edited. + - **Agent panel**: Chat with the editor agent inline. Attach files, view per-session diffs, leave feedback, and jump to the page the agent edited. - **Add to Assistant**: Send highlighted content straight to the [Assistant](https://www.mintlify.com/docs/assistant) from the editor toolbar. - **File tree**: Create folders, create unlisted pages, and rename items in the file tree. Add unlisted Markdown into the navigation tree, and open unlisted Markdown and media files directly from the tree. @@ -1128,10 +1128,10 @@ noindex: true Use subcommands to explore specific data: - - `mint analytics stats` — views, visitors, searches, feedback, and assistant usage for a date range - - `mint analytics search` — search queries with hit counts and click-through rates - - `mint analytics feedback` — page and code snippet feedback submitted by users - - `mint analytics conversation list` — recent assistant conversations + - `mint analytics stats`: views, visitors, searches, feedback, and assistant usage for a date range + - `mint analytics search`: search queries with hit counts and click-through rates + - `mint analytics feedback`: page and code snippet feedback submitted by users + - `mint analytics conversation list`: recent assistant conversations All subcommands support `--from`, `--to`, and `--format` flags. Output formats include `plain` (default), `table`, `json`, and `graph`. @@ -2764,7 +2764,7 @@ noindex: true ## More - - **Troubleshooting for API pages**: API pages could be complicated so we listed common issues to help you sort them out quickly — [Read the docs](/api-playground/troubleshooting) + - **Troubleshooting for API pages**: API pages could be complicated so we listed common issues to help you sort them out quickly. [Read the docs](/api-playground/troubleshooting) diff --git a/cli/commands.mdx b/cli/commands.mdx index 8a12a990a6..a53a417e27 100644 --- a/cli/commands.mdx +++ b/cli/commands.mdx @@ -157,7 +157,7 @@ mint login Opens a browser window to complete authentication. If the browser does not open, the CLI displays a URL to open manually and a prompt to paste the authorization code. Credentials save in `~/.config/mintlify/config.json`. -If you have more than one project, the CLI prompts you to select a default after you log in. You can change the default project later with `mint config set subdomain `. +If you have more than one project, the CLI prompts you to select a default after you sign in. You can change the default project later with `mint config set subdomain `. --- @@ -656,7 +656,7 @@ These commands are available to run but are not yet functional. Running them rec ## Telemetry -The CLI collects usage telemetry to help improve Mintlify. Telemetry data includes the command name, CLI version, operating system, and architecture. If you are logged in, telemetry events also include your account email address. Logged-out usage stays anonymous, and logging out removes your stored email. Mintlify does **not** collect project content or file paths. +The CLI collects usage telemetry to help improve Mintlify. Telemetry data includes the command name, CLI version, operating system, and architecture. If you are signed in, telemetry events also include your account email address. Signed-out usage stays anonymous, and signing out removes your stored email. Mintlify does **not** collect project content or file paths. By default, the CLI collects telemetry data. You can opt out at any time using the `--telemetry` flag: diff --git a/cli/preview.mdx b/cli/preview.mdx index b2ec8fc732..20c11e1413 100644 --- a/cli/preview.mdx +++ b/cli/preview.mdx @@ -43,9 +43,9 @@ You must authenticate the CLI with your Mintlify account to enable search and th mint login ``` -After you authenticate with the `mint login` command, the CLI stores your credentials in `~/.config/mintlify/config.json` so you stay logged in across sessions. The CLI also prompts you to select a default project. +After you authenticate with the `mint login` command, the CLI stores your credentials in `~/.config/mintlify/config.json` so you stay signed in across sessions. The CLI also prompts you to select a default project. -Once logged in, run `mint dev` to start the local preview with search and the assistant enabled. The assistant uses the same indexed content as your deployed documentation site. +Once signed in, run `mint dev` to start the local preview with search and the assistant enabled. The assistant uses the same indexed content as your deployed documentation site. To check your authentication status, run: diff --git a/components/fields.mdx b/components/fields.mdx index 4598f9c233..726f04fa4d 100644 --- a/components/fields.mdx +++ b/components/fields.mdx @@ -9,7 +9,7 @@ Use fields to document API parameters and responses. There are two types of fiel ## Parameter field -Use the `` component to define parameters for your APIs or SDKs. Adding a `ParamField` automatically adds an [API Playground](/api-playground/overview). +Use the `` component to define parameters for your APIs or SDKs. Adding a `ParamField` automatically adds an [API playground](/api-playground/overview). An example of a parameter field diff --git a/create/personalization.mdx b/create/personalization.mdx index 18ce18bdd2..26777924e5 100644 --- a/create/personalization.mdx +++ b/create/personalization.mdx @@ -25,7 +25,7 @@ Enable personalization on the [General](https://app.mintlify.com/settings/projec ### Shared session -Shared session reuses a visitor's existing application session, so they don't need to log in again on your Mintlify site. +Shared session reuses a visitor's existing application session, so they don't need to sign in again on your Mintlify site. 1. Select **Shared session** in the **Personalization** settings. 2. Enter an **Info API URL** that returns the current visitor's [user data](#user-data-format). @@ -127,7 +127,7 @@ For conditional rendering based on user data, use the `user` variable in JSX com ``` - The `user` variable is an empty object for logged-out users. Use optional chaining on all `user` fields to prevent errors. For example, `{user.org?.plan}` instead of `{user.org.plan}`. + The `user` variable is an empty object for signed-out users. Use optional chaining on all `user` fields to prevent errors. For example, `{user.org?.plan}` instead of `{user.org.plan}`. To read the same user object from a [custom JavaScript file](/customize/custom-scripts#access-personalized-user-data), use `window.mintlify.user` and listen for the `mintlify:user` event. diff --git a/deploy/authentication-setup.mdx b/deploy/authentication-setup.mdx index 7e02816bef..153b5f917a 100644 --- a/deploy/authentication-setup.mdx +++ b/deploy/authentication-setup.mdx @@ -12,7 +12,7 @@ keywords: ['authentication', 'auth', 'OAuth', 'JWT', 'password', 'private'] OAuth and JWT authentication require an [Enterprise plan](https://mintlify.com/pricing?ref=authentication). -Authentication requires users to log in before accessing your content. +Authentication requires users to sign in before accessing your content. You can configure full authentication for all pages or partial authentication where some pages are public and others require authentication. @@ -80,7 +80,7 @@ You host your documentation at `docs.foo.com` and you need basic access control 3. Set **Method** to **Authenticated**. 4. Click **Save**. - After you save, your site redeploys. When it finishes deploying, anyone who visits your site must log in to your Mintlify organization to access your content. + After you save, your site redeploys. When it finishes deploying, anyone who visits your site must sign in to your Mintlify organization to access your content. 1. In your dashboard, go to [Members](https://app.mintlify.com/settings/organization/members). @@ -122,7 +122,7 @@ You host your documentation at `docs.foo.com` and your entire team has access to * **Logout URL** (optional): The native logout URL for your OAuth provider. When users log out, Mintlify validates the logout redirect against this configured URL for security. The redirect only succeeds if it exactly matches the configured `logoutUrl`. If you do not configure a logout URL, users redirect to `/login`. Mintlify redirects users with a `GET` request and does not append query parameters. Include any parameters (for example, `returnTo`) directly in the URL. 6. Click **Save**. - After you configure your OAuth settings, your site redeploys. When it finishes deploying, anyone who visits your site must log in to your OAuth provider to access your content. + After you configure your OAuth settings, your site redeploys. When it finishes deploying, anyone who visits your site must sign in to your OAuth provider to access your content. 1. Copy the **Redirect URL** from your [Access settings](https://app.mintlify.com/settings/project/authentication). @@ -215,7 +215,7 @@ You host your documentation at `docs.foo.com` and you have an existing OAuth ser 8. Click **Generate new key**. 9. Store your key securely where your backend can access it. - After you generate a private key, your site redeploys. When it finishes deploying, anyone who visits your site must log in to your JWT authentication system to access your content. + After you generate a private key, your site redeploys. When it finishes deploying, anyone who visits your site must sign in to your JWT authentication system to access your content. Modify your existing login flow to include these steps after user authentication: diff --git a/deploy/preview-deployments.mdx b/deploy/preview-deployments.mdx index 3a1d592898..9ab8494e9b 100644 --- a/deploy/preview-deployments.mdx +++ b/deploy/preview-deployments.mdx @@ -10,7 +10,7 @@ keywords: ["preview URLs", "pull request previews", "branch previews", "staging Preview deployments let you see how changes to your docs look before merging to production. Each preview creates a shareable URL that updates automatically as you push new changes. -Preview URLs are publicly viewable by default. Share a preview link with anyone who needs to review your changes. +Preview URLs are publicly viewable by default. Share the preview deployment URL with anyone who needs to review your changes. ## Create preview deployments diff --git a/enterprise-contracting.mdx b/enterprise-contracting.mdx index 1eb68d466e..d81a9d33b6 100644 --- a/enterprise-contracting.mdx +++ b/enterprise-contracting.mdx @@ -15,13 +15,13 @@ This page explains what those things are—and what's genuinely open for discuss All Mintlify Enterprise agreements go through legal review. Our goal is execution in under three business days. - + We review your redlines and assess each against our standard positions. - + We come back with responses on every open item. We bring solutions, not walls. - + Final document signed and deal closed. diff --git a/guides/geo.mdx b/guides/geo.mdx index 41be147cd1..75c6a33706 100644 --- a/guides/geo.mdx +++ b/guides/geo.mdx @@ -156,14 +156,14 @@ Mintlify's auto-generated `robots.txt` allows all crawlers by default and includ A `robots.txt` that blocks all crawlers also blocks AI agents: -```txt Bad — blocks all AI agents +```txt Bad: blocks all AI agents User-agent: * Disallow: / ``` To block specific scrapers while allowing AI agents, target only the bots you want to restrict: -```txt Good — allows AI agents +```txt Good: allows AI agents User-agent: BadBot Disallow: / diff --git a/guides/help-center.mdx b/guides/help-center.mdx index bb8bb6583f..b9362319ba 100644 --- a/guides/help-center.mdx +++ b/guides/help-center.mdx @@ -142,7 +142,7 @@ Old cached data can cause login problems. Clear your browser cache and try again ## Check account status -If your account is suspended or deactivated, you'll see an error when logging in. +If your account is suspended or deactivated, you'll see an error when signing in. Contact support if you believe this is a mistake. ``` diff --git a/help-center/configure-oauth-with-auth0.mdx b/help-center/configure-oauth-with-auth0.mdx index 9a04531821..c37aa2d949 100644 --- a/help-center/configure-oauth-with-auth0.mdx +++ b/help-center/configure-oauth-with-auth0.mdx @@ -52,5 +52,5 @@ Then add a matching `groups` value to the frontmatter of each page you want to r ## Troubleshooting - **Callback URL mismatch.** Auth0 blocks the login and shows a callback error. Confirm the redirect URL in Auth0's **Allowed Callback URLs** exactly matches the one shown in your Mintlify authentication settings, including protocol and trailing path. -- **Users log in but see no restricted content.** Your groups claim is not reaching Mintlify. Confirm the Auth0 Action adds the claim, that `source` in Mintlify matches the token you set it on (`id_token` or `access_token`), and that `groupsClaim` matches the claim name. +- **Users sign in but see no restricted content.** Your groups claim is not reaching Mintlify. Confirm the Auth0 Action adds the claim, that `source` in Mintlify matches the token you set it on (`id_token` or `access_token`), and that `groupsClaim` matches the claim name. - **Logout does not redirect back.** Auth0 requires the `returnTo` URL in the logout link to be listed under **Allowed Logout URLs** on the application. diff --git a/migration-services/enterprise.mdx b/migration-services/enterprise.mdx index fd541c153e..8d7983df0a 100644 --- a/migration-services/enterprise.mdx +++ b/migration-services/enterprise.mdx @@ -15,7 +15,7 @@ We lead a kick-off call to gather your content and determine your information ar -We assemble your content into a Mintlify site, perform quality assurance on the content, and share a preview link so you can monitor progress in real time. +We assemble your content into a Mintlify site, perform quality assurance on the content, and share a preview deployment so you can monitor progress in real time. diff --git a/snippets/setup-agent-prompt.mdx b/snippets/setup-agent-prompt.mdx index 6f0ab77c77..8577d570e6 100644 --- a/snippets/setup-agent-prompt.mdx +++ b/snippets/setup-agent-prompt.mdx @@ -6,19 +6,19 @@ Get my documentation live on a published Mintlify site. You are successfully don 1. Ask for my existing content that will be used for my Mintlify site. This may be a local folder or a repo. Verify the source before building: echo back exactly what you're reading and list its top-level contents so I can confirm it's right. If you can't access something I named (private repos return 404, same as nonexistent), stop and ask. Never substitute a different source. 2. Check whether `mint` is installed with `mint --version`. If it's missing, install it with `npm i -g mint` (or `pnpm add -g mint`). If it's already installed, run `mint update` instead of reinstalling. 3. Run `mint status`. If it already shows an organization, skip to step 7. -4. Needs me: If `mint status` shows I'm not logged in, ask me directly whether I already have a Mintlify account. Don't guess. +4. Needs me: If `mint status` shows I'm not signed in, ask me directly whether I already have a Mintlify account. Don't guess. - If I have one: run `mint login`. You need me for browser steps and to approve access. - If I don't: ask me for my first name, last name, company, and email if I haven't given them already—never invent these. Run `mint signup --firstName [firstName] --lastName [lastName] --company [company] --email [email]` as a background task since it blocks until I click a verification link that can take several minutes. -5. Needs me: I'll check my email and click the verification link. That opens a browser tab that automatically finishes the rest of account creation/logging in. I must approve the CLI, then connect a GitHub repository or let Mintlify host one. Tell me clearly this step is mine, then wait for it before continuing. -6. Run `mint status` again to confirm an organization and subdomain now exist. The subdomain isn't provisioned until I select or connect a repository during the step 5 browser flow — so if `mint status` shows my organization but no subdomain yet, that almost always means I haven't finished the repo step, not that anything is broken. Don't treat it as an error or poll blindly: wait until I confirm I've completed onboarding, then re-run `mint status`. Provisioning can still lag a few seconds after that, so retry a few times before concluding something is wrong. -7. Needs me: ask for the URL of the repository connected to my Mintlify project — `mint status` doesn't expose it, so you can't look it up yourself. Clone it once I give it to you. -8. Check what's in that repo. If I connected my own existing docs repo, my content is already there — don't overwrite it. If Mintlify created the repo, it contains starter template content — replace that with my actual docs content from step 1. Only use `mint new [directory]` if I want a different theme or template than what's in the repo — scaffold it locally, then use its output in place of the seeded content. +5. Needs me: I'll check my email and click the verification link. That opens a browser tab that automatically finishes the rest of account creation and sign-in. I must approve the CLI, then connect a GitHub repository or let Mintlify host one. Tell me clearly this step is mine, then wait for it before continuing. +6. Run `mint status` again to confirm an organization and subdomain now exist. The subdomain isn't provisioned until I select or connect a repository during the step 5 browser flow. If `mint status` shows my organization but no subdomain yet, that almost always means I haven't finished the repo step, not that anything is broken. Don't treat it as an error or poll blindly: wait until I confirm I've completed onboarding, then re-run `mint status`. Provisioning can still lag a few seconds after that, so retry a few times before concluding something is wrong. +7. Needs me: ask for the URL of the repository connected to my Mintlify project. `mint status` doesn't expose it, so you can't look it up yourself. Clone it once I give it to you. +8. Check what's in that repo. If I connected my own existing docs repo, my content is already there, so don't overwrite it. If Mintlify created the repo, it contains starter template content. Replace that with my actual docs content from step 1. Only use `mint new [directory]` if I want a different theme or template than what's in the repo. Scaffold it locally, then use its output in place of the seeded content. 9. Preview with `mint dev`, which generally starts on `http://localhost:3000` unless that port is in use. It blocks until stopped, so run it as a background task. Verify the preview loads, then stop it before continuing. 10. Commit and push your changes. Mintlify deploys automatically on push. 11. Needs me: If I want a custom domain, run `mint add-domain `. It prints the DNS records I need to add with my domain provider. Tell me the DNS records, since only I can configure them at my registrar. Make it clear that this is a step I must complete. 12. Confirm my site is live: fetch `https://.mintlify.site` (find the subdomain via `mint status`) and confirm it loads. If I added a custom domain in step 11, also fetch that domain and confirm it loads before calling this step done—DNS propagation can lag, so retry a few times before treating a failed fetch as an error. 13. Set yourself up to keep working here: install the [Mintlify skill](https://mintlify.com/docs/ai/skillmd.md) with `npx skills add https://mintlify.com/docs`, then register the [admin MCP server](https://mintlify.com/docs/ai/model-context-protocol.md) at `https://mcp.mintlify.com` for your specific tool. For example, `claude mcp add --transport http mintlify https://mcp.mintlify.com` for Claude Code or fetch https://mintlify.com/docs/ai/mintlify-mcp.md for instructions for Claude, Cursor, Codex, or ChatGPT. Do this step yourself—don't ask me to run these commands. -14. Needs me: the first admin MCP tool call opens a browser window for OAuth login. Approve it there. Most tools don't load newly added MCP servers mid-session — if the Mintlify tools don't show up, tell me to restart you and we'll pick up from here. +14. Needs me: the first admin MCP tool call opens a browser window for OAuth login. Approve it there. Most tools don't load newly added MCP servers mid-session. If the Mintlify tools don't show up, tell me to restart you and we'll pick up from here. 15. If any command fails in a way not covered above, stop and tell me the exact error rather than guessing or retrying blindly. If it looks like something's wrong on Mintlify's end rather than in what you're doing, check https://status.mintlify.com or point me to https://mintlify.com/docs/contact-support.