Apply brand tone and writing style fixes#6701
Merged
Merged
Conversation
ethanpalm
approved these changes
Jul 22, 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
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
Minor style fixes for consistency across the files touched by "Decouple search and assistant endpoints" (#6700).
Changes
api/introduction.mdx: replace double hyphen (--) with em dash (—) to match the repo convention.api/assistant/get-page-content.mdx: add a blank line after the## Rate limitsheading to match the siblingsearch.mdxformatting.Context
The rest of the in-scope pages already follow the house style: second person, active voice, sentence-case headings, consistent terminology.
Note
Low Risk
Copy and whitespace-only MDX changes with no runtime or API behavior impact.
Overview
Small house-style tweaks on API docs tied to the search/assistant endpoint work.
In
api/introduction.mdx, the authentication sentence now uses an em dash (—) instead of a double hyphen (--) when describing org-scoped API keys.In
api/assistant/get-page-content.mdx, a blank line was added under## Rate limitsso it matchessearch.mdxand the other assistant pages.Reviewed by Cursor Bugbot for commit c94f225. Bugbot is set up for automated code reviews on this repo. Configure here.