Apply brand tone and writing style fixes - #7305
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
ethanpalm
approved these changes
Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Style-consistency pass over the pages touched by the className/Tailwind documentation update (#7301), fixing minor deviations from the repo's voice and terminology conventions.
Changes
components/cards.mdx: "Clicking on this card" → "Clicking this card" (per Vale "click on" rule) in demo prose and mirrored code samplescomponents/responses.mdx,components/update.mdx,components/visibility.mdx: split dash-joined clauses into two sentencescomponents/accordions.mdx: sentence-case code block title (Accordion Group Example→Accordion group example)help-center/tailwind-classes-not-applying-in-editor-preview.mdx: passive → active voice ("it never generates the CSS")All other in-scope pages (custom-scripts, custom-layouts, image-embeds, callouts, remaining component references) already follow the predominant style. Validation and broken-link checks pass.
Note
Low Risk
Copy-only edits to docs and help content with no runtime, auth, or data impact.
Overview
Documentation-only voice and style pass across six MDX pages tied to recent Tailwind/className docs work. No product or API behavior changes.
Cards demo copy and mirrored samples now say “Clicking this card” instead of “Clicking on this card” (Vale click on rule). Accordions renames a fenced example title to sentence case (
Accordion group example).Several pages replace em-dash run-ons with two sentences:
responses.mdx(type prop description),update.mdx(RSS Markdown-only note), andvisibility.mdx(Markdown export behavior). The Tailwind live preview help article rephrases the build-vs-preview explanation so the live preview actively “never generates” Tailwind CSS instead of passive wording.Reviewed by Cursor Bugbot for commit c536017. Bugbot is set up for automated code reviews on this repo. Configure here.