Skip to content

docs: take the em-dashes out of the README - #58

Merged
upgradedev merged 1 commit into
mainfrom
docs/humanize-readme
Aug 3, 2026
Merged

docs: take the em-dashes out of the README#58
upgradedev merged 1 commit into
mainfrom
docs/humanize-readme

Conversation

@upgradedev

Copy link
Copy Markdown
Owner

The README had 62 em-dashes in 682 lines, in the file a judge opens before anything else. House style avoids them: they stack clauses into sentences that are hard to read aloud.

Not a blind find-and-replace

A mechanical swap to commas produces comma splices, so the pass distinguishes three cases:

Pattern Becomes Why
A — B — C (parenthetical pair) A, B, C that is what the pair was doing
before an independent clause . the sentence ends instead of growing
everything else , an appositive reads naturally as a comma

The title took a colon rather than a comma, because # Cinemory, your memories, made into film reads as a list.

Checked afterwards

Scanned for the artefacts this edit produces: zero double commas, stranded punctuation, or headings left ending mid-clause. The only line matching the heading check is a code comment inside a fenced block, not prose.

Docs only. No application code, no video, no demo asset.

Sixty-two of them, in a file a judge reads before anything else. The house
style avoids them because they stack clauses into sentences that are hard to
read aloud.

Substitution was not blind. A parenthetical pair becomes a pair of commas, an
em-dash introducing an independent clause becomes a full stop so the sentence
ends instead of growing, and the rest become commas where an appositive reads
naturally. The title takes a colon, since a comma made it read as a list.

Checked afterwards for the artefacts this kind of edit produces: no double
commas, no stranded punctuation, no heading left ending mid-clause.
@upgradedev
upgradedev merged commit 98c9533 into main Aug 3, 2026
12 checks passed
@upgradedev
upgradedev deleted the docs/humanize-readme branch August 3, 2026 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant