docs: extend writing-rules sweep to remaining docs tree#501
Merged
Conversation
Replace every em and en dash across the concepts docs, the nine evidence-profile docs, the dev.atrib/attribution extension spec, the payments profile, and the PyPI runsheet with colons, commas, semicolons, or parentheses as each sentence needed; en-dash section and step ranges become plain hyphens. Rewrite the one banned phrase in the extension spec around the forwarding obligation it claimed, matching the wording already merged in the p049 draft. Tier bullets in the profile docs move from dash separators to colons. Editorial only: no profile facts, tier values, normative MUSTs, or links change, so no profile_version or extension version bump. The chain-tail charter needed nothing; it already complies. Two scanner hits stay as-is: "robustness" in payments-profile describes the technical cross-attestation property the rule permits, and "facilitator" in concepts/08 is the x402 protocol role name.
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.
Follow-up to #496, which swept the twelve 2026-07-06 redesign docs. This extends the same writing rules to the 18 remaining
docs/files that still carried em/en dashes: six concepts docs, the nine evidence-profile docs, thedev.atrib/attributionextension spec,payments-profile.md, and the PyPI runsheet.What changed
- \declared` — description), which become colons uniformly. Prose dashes became commas, semicolons, colons, or parentheses per sentence; en-dash ranges (§2.1–§2.5,Rules 1–5,Steps 2–3`) become plain hyphens._metaforwarding sentence) rewritten to match the wording already merged for the same sentence in the p049 draft, so the two documents agree again.docs/chain-tail-corpus-scoped-charter.mdneeded nothing: it was authored under the rules and already complies. Verified for dashes, banned vocabulary, curly quotes, and exclamation marks.Reviewer notes
#62-receipt-blockis externally linked; the changed slugs have zero references.payments-profile.md§Note (describes the technical cross-attestation property, which the rule permits) and "facilitator" inconcepts/08(the x402 protocol role name, not the banned verb).payments-profile.mdwas relocated verbatim per D147; the only edits here are five en-dash ranges in its mapping tables, nothing in normative prose.Verification
pnpm doc-sync: 13/13 checks passing.grep -rE '—|–|load[- ]bearing' docs/returns nothing.