fix(copy): separate stream update cadence from Bitcoin settlement claims - #13
Merged
Conversation
Marketing feedback flagged that copy like 'settling on Bitcoin every few seconds' and 'once it lands, it is final' conflates the ~5s Stacks block cadence (how often streams update) with Bitcoin finality (inherited when Stacks state anchors to Bitcoin). Crypto audiences will nitpick that. Rework every fused claim across the landing page, FAQ, hero, features, site metadata, and the marketing docs to the accurate shape: streams update in seconds; settlement inherits Bitcoin finality. Add a durable settlement-language rule to MARKETING_PLAN_V2 and CONTENT_SCHEDULE so future copy cannot regress.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
Applies the marketing reviewer's point-4 fix across the live site and marketing docs: copy must never fuse the ~5s stream-update cadence with Bitcoin settlement, and must never imply instant finality ("once it lands, it is final").
The accurate shape, used throughout: streams update in seconds; settlement inherits Bitcoin finality.
Live site fixes
who-its-for.tsxfaq.tsxhero.tsxfeatures.tsxlayout.tsx(metadata)Marketing docs
MARKETING_PLAN_V2.md— corrected supporting fact [Security Review] StackStream v1.0.0-rc1 — Pre-Mainnet Community Review #1 (was: "Stacks blocks settle in about 5 seconds and are as final as Bitcoin once confirmed") and added a settlement language rule with approved/forbidden phrasings.CONTENT_SCHEDULE.md— fixed all 8 fused lines (Jun 16 ×4, Jun 19 ×2, Jun 22, Jun 24) in each channel's voice, and added the same rule to the voice-rules block so future copy can't regress.The brand line "real-time money, settled on Bitcoin" is intentionally kept — it's positioning, not a per-block claim.
Verify
npm run buildpasses (13 routes)