Skip to content

chore: strip em/en dashes from user-facing text - #1497

Merged
Flotapponnier merged 1 commit into
devfrom
chore/strip-em-en-dashes-user-text
Jul 26, 2026
Merged

chore: strip em/en dashes from user-facing text#1497
Flotapponnier merged 1 commit into
devfrom
chore/strip-em-en-dashes-user-text

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Removes em-dashes and en-dashes from every user-visible surface (markdown docs, hardcoded UI copy, meta titles, JSON-LD names, SVG aria-labels, provider registry descriptions). Comments + design-vocabulary glyphs untouched. See commit for full scope.

Removes em-dashes and en-dashes from every user-visible surface,
replacing with commas / periods / colons contextually. Never a hyphen.

Editorial preference documented in the user's global CLAUDE.md and
already enforced by the spec-schema validator on bench YAMLs; this
extends the same rule to markdown docs, hardcoded UI copy, meta
titles, JSON-LD names, SVG aria-labels, provider registry descriptions.

Scope:
- README.md, AGENTS.md, docs/architecture.md (all prose in these files)
- src/app/layout.tsx (RSS + JSON Feed titles)
- src/app/mcp, rpc, hyperliquid/[slug], benchmarks/[slug],
  compare/[slug]/page.tsx (page titles, headings, jsonld names)
- src/app/api/badge, api/sparkline (SVG titles + aria-labels)
- src/data/provider-registry.ts (ParaSwap, Ondo OUSG, Maple SyrupUSDC)

Skipped:
- JSX comments ({/* ... */}) and inline // block comments (internal
  code documentation, not user-visible)
- Design-vocabulary '—' glyphs used as 'no data' cell indicators
  (ledger-table, hl-cohort-leaderboard, etc.)
- src/lib/jsonld.ts em-dash logic (operates ON the dash, not text)
@Flotapponnier
Flotapponnier merged commit 23976db into dev Jul 26, 2026
1 check failed
Flotapponnier added a commit that referenced this pull request Jul 26, 2026
…1497) (#1498)

Removes em-dashes and en-dashes from every user-visible surface,
replacing with commas / periods / colons contextually. Never a hyphen.

Editorial preference documented in the user's global CLAUDE.md and
already enforced by the spec-schema validator on bench YAMLs; this
extends the same rule to markdown docs, hardcoded UI copy, meta
titles, JSON-LD names, SVG aria-labels, provider registry descriptions.

Scope:
- README.md, AGENTS.md, docs/architecture.md (all prose in these files)
- src/app/layout.tsx (RSS + JSON Feed titles)
- src/app/mcp, rpc, hyperliquid/[slug], benchmarks/[slug],
  compare/[slug]/page.tsx (page titles, headings, jsonld names)
- src/app/api/badge, api/sparkline (SVG titles + aria-labels)
- src/data/provider-registry.ts (ParaSwap, Ondo OUSG, Maple SyrupUSDC)

Skipped:
- JSX comments ({/* ... */}) and inline // block comments (internal
  code documentation, not user-visible)
- Design-vocabulary '—' glyphs used as 'no data' cell indicators
  (ledger-table, hl-cohort-leaderboard, etc.)
- src/lib/jsonld.ts em-dash logic (operates ON the dash, not text)

Co-authored-by: Florent Tapponnier <contact@mobula.io>
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