Skip to content

Apply brand tone and writing style fixes#6286

Merged
ethanpalm merged 1 commit into
mainfrom
mintlify/5af3e6de
Jun 25, 2026
Merged

Apply brand tone and writing style fixes#6286
ethanpalm merged 1 commit into
mainfrom
mintlify/5af3e6de

Conversation

@mintlify

@mintlify mintlify Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Remove first-person plural ("We use", "We support") from technical reference docs in favor of "Mintlify" as the subject, aligning with the writing standards (second person for instructions, third person for system behavior).

Changes

  • create/text.mdx: "We support most Markdown formatting…" → "Mintlify supports…"
  • create/text.mdx: "We support LaTeX…" → "Mintlify supports LaTeX…"
  • create/code.mdx: "We use Shiki…" → "Mintlify uses Shiki…"
  • deploy/vercel.mdx: "We use the rewrites configuration…" → "Mintlify uses the rewrites configuration…"

First-person voice in customer-facing pages (enterprise-contracting.mdx, advanced-support.mdx, contact-support.mdx) was left intact since those pages intentionally speak from Mintlify's perspective.


Note

Low Risk
Copy-only wording updates in documentation with no runtime, config, or security impact.

Overview
Aligns technical reference copy with Mintlify writing standards by naming Mintlify as the subject when describing platform behavior instead of first-person plural (We).

In create/text.mdx, Markdown formatting and LaTeX support sentences now say Mintlify supports…. In create/code.mdx, the Shiki syntax-highlighting line becomes Mintlify uses… and supports…. In deploy/vercel.mdx, the vercel.json rewrites explanation now says Mintlify uses the rewrites configuration. Customer-facing pages that intentionally use Mintlify’s voice are unchanged.

Reviewed by Cursor Bugbot for commit a0140cf. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify mintlify Bot requested a review from ethanpalm June 25, 2026 21:14
@mintlify

mintlify Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
mintlify 🟢 Ready View Preview Jun 25, 2026, 9:23 PM

@mintlify

mintlify Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
smartac 🟢 Ready View Preview Jun 25, 2026, 9:26 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
testsignup415 🟢 Ready View Preview Jun 25, 2026, 9:31 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
adminroletesting 🟢 Ready View Preview Jun 25, 2026, 9:36 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@ethanpalm ethanpalm merged commit 946977a into main Jun 25, 2026
6 checks passed
@ethanpalm ethanpalm deleted the mintlify/5af3e6de branch June 25, 2026 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants