chore: remove em dashes from text and comments#15
Merged
Conversation
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.
Removes every em dash (U+2014) from tracked source across the repo, plus the few stray en dashes (U+2013) found in the same docs, per the owner's convention against both.
Scope
18 files:
.env.example,CONTRIBUTING.md, client CSS/components/pages, and docs. Each occurrence was rewritten in context (comma, colon, semicolon, parentheses, or split sentence) so grammar and meaning are preserved. No logic or behavior changed.Notable cases:
client/src/pages/AnalysisPage.tsx: the user-facing'—'fallback placeholder became'-'.0–10) became hyphens (0-10).term — descriptionpatterns becameterm: description.Verification
git grepfor U+2014 and U+2013 both return zero matches.pnpm -r buildclean.pnpm typecheckclean.