polish(marketing): remove prose em/en-dashes site-wide (incl. homepage) - #235
Merged
Conversation
Final dash sweep across the whole marketing site, including the homepage components I'd previously left to the hero owner. Em-dashes (—) and en-dashes (–) in visible copy are replaced with commas (prose) or hyphens (numeric ranges); the homepage audit-trail / outcome / value-prop sections that still read "uploaded — by named owner" are now clean. Protected (left intact): the functional '—' UI sentinels — the comparison-table "not included" marker (PricingComparisonTable) and empty-value placeholders (VerifyClient, StatusPageClient) — which are correct UI dashes, not prose. Safe by construction: em/en-dashes only ever appear in strings, JSX text, or comments (never code logic outside those sentinels), so the blanket replace is non-breaking — tsc + eslint clean, all routes 200. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (62)
📝 WalkthroughWalkthroughThis PR systematically updates punctuation and typography across 70+ marketing and component files, replacing em-dashes with commas in copy and comments, en-dashes with hyphens in range notation, and refining text wording. No functional code logic or component behavior changes occur. ChangesPunctuation & Typography Standardization
Estimated Code Review Effort🎯 1 (Trivial) | ⏱️ ~8 minutes Possibly Related PRs
Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
♿ Accessibility Test Results✅ PASSED - No critical accessibility issues found Tests Performed:
Artifacts: Download the accessibility reports from the "Artifacts" section for detailed results. |
🔒 Compliance Testing ResultsTest Date: Thu Jun 4 09:23:22 UTC 2026 GDPR ComplianceSOC2 ComplianceCompliance Reports: Available in the artifacts section below |
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.
Final dash sweep across the whole marketing site, including the homepage components previously left to the hero owner.
'—'UI sentinels — the comparison-table "not-included" marker (PricingComparisonTable) and empty-value?? '—'placeholders (VerifyClient,StatusPageClient). Those are correct UI dashes, not prose.Safe by construction: em/en-dashes only ever appear in strings, JSX text, or comments (never code logic outside those sentinels), so the blanket replace is non-breaking. 62 files, symmetric 190/190.
tsc+ eslint clean; home + pricing/security/features/enterprise all 200; homepage audit-trail fix verified in-browser.🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation
Style
Chores