Apply brand tone and writing style fixes - #7130
Merged
Merged
Conversation
ethanpalm
approved these changes
Aug 26, 2026
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 Workflows to automatically generate PRs for you. |
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 on the preview deployment pages touched by the fork-support clarification (#7078).
Changes
api/preview/trigger.mdxfrontmatter and trailing whitespace indeploy/preview-deployments.mdx.No technical content, code samples, or API references were changed.
Note
Low Risk
Copy and formatting edits only; no product logic, APIs, or build configuration.
Overview
Documentation-only style pass on preview deployment pages (follow-up to fork-support clarification), with no API or behavioral changes.
The fork-branch help article opening is rewritten into shorter sentences in English, Spanish, and French so fork PRs and failed Trigger preview deployment API calls are explained separately instead of one long compound sentence.
In the Preview lifetime section, “PR” is spelled out as “pull request” (and locale equivalents in
es,fr, andzh) for terminology consistency. Minor cleanup: trailing whitespace indeploy/preview-deployments.mdxand an extra blank line inapi/preview/trigger.mdxfrontmatter.Reviewed by Cursor Bugbot for commit 56bdd61. Bugbot is set up for automated code reviews on this repo. Configure here.