docs(readme): refine, proofread, drop em-dashes#130
Merged
Conversation
…sing - Replace em-dashes (—) throughout with commas, colons, semicolons, or parens as appropriate for the local syntactic role; numeric en-dashes (e.g. 25–30M, RFC-0002–RFC-0010, Phase 0–1) are preserved. - Tighten the 'Why GenoLeWM' opener (drop 'powerful' adjective and the 'signal is strong' framing) and the Phase 1 status line (drop 'shipping today'). - Refocus the cypherpunk table row on RFC content (on-device, verifiable inference) rather than positioning. - Drop the aspirational lead-in to 'Engineering discipline' and let the gate table speak for itself. - Reflow acknowledgments to use 'by ... for ...' instead of paired em-dashes around the author list.
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
2 participants
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
A proofreading and refinement pass over
README.md:—(em-dash) is replaced with thebest fit for its local syntactic role: commas for parentheticals,
colons for explanatory follow-ons, semicolons for stronger clause
breaks, parens where the aside is clearly bounded. Numeric en-dashes
(e.g.
25–30M,RFC-0002–RFC-0010,Phase 0–1) are preservedbecause they are not em-dashes.
calls Carbon "powerful" and no longer uses "the signal is strong"
framing; it just states the mechanic (
logP(alt) − logP(ref)) andgoes to the structural limits. The Phase 1 status line drops
"shipping today". The "cypherpunk angle" table row is refocused on
the RFC content (on-device, verifiable inference) rather than
positioning against "other bio models". The aspirational lead-in to
Engineering disciplineis removed; the gate table speaks foritself.
rewritten as
by ... for ...constructions, which is closer tostandard academic acknowledgment phrasing.
No structural changes; all headings, badges, code blocks, tables, and
links are preserved.
Test plan
mkdocs build --strict) passes—(U+2014 em-dash) remains inREADME.mdGenerated by Claude Code