docs: plainer tone across the documentation site - #129
Merged
Conversation
Drop signpost prefixes and inflated phrasing, sentence-case the headings, replace em dashes, and remove mechanical bold. No code, command, link, or technical claim changed.
Extends the same tone pass to the rest of the docs tree: drop signpost headings and preambles, thin the repeated antithesis phrasing, remove mechanical bold lead-ins and emphatic italics, and replace em dashes. Cross-linked headings are left verbatim so anchors keep resolving. No code block, command, link, number, or technical claim changed.
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.
A copyedit pass over the documentation for tone and readability, covering the guides and the rest of the user-facing tree (concepts, guides, reference).
Tone only:
Nothing technical changed. Verified over every edited file: fenced code blocks byte-identical, link targets unchanged, inline-code identifiers preserved, and every intra-doc anchor still resolves (cross-linked headings kept verbatim). The site builds.