Repository navigation
docs: tone down README marketing copy to sentence case - #223
Merged
Merged
Conversation
✅ Deploy Preview for dryoc-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
brndnmtthws
marked this pull request as ready for review
September 27, 2026 20:10
brndnmtthws
enabled auto-merge (squash)
September 27, 2026 20:10
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #223 +/- ##
=======================================
Coverage 68.32% 68.32%
=======================================
Files 115 115
Lines 10032 10032
=======================================
Hits 6854 6854
Misses 3178 3178 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Summary
Tones down the README marketing copy: all-caps lead-ins in "Why dryoc?" become sentence case, and hype words ("blazing", "high-performance", "exceptional", "state-of-the-art", "hand-optimized", "Pythonic") are replaced with plain descriptions. Post-Quantum and Platform lead-ins are also sentence-cased for consistency.
User Impact
README reads more neutral and professional; no functional, API, or feature-flag changes.
Root Cause
Marketing-style uppercase labels and superlatives in README prose.
Fix
README.md prose edits only (13 insertions, 13 deletions, no code changes).
Validation
Reviewed
git diff --cached; prose-only change, no tests affected.