chore(site): tweak wording

[NathanFlurry]

No description provided.

[vercel]

Deployment failed with the following error:

Too many requests - try again in 3 minutes (more than 120, code: "api-deployments-flood-pro").

Learn More: https://vercel.com/docs/limits#rate-limits

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(rivetkit): add ability to destroy actors #3458 : 2 dependent PRs (#3459 , #3462 )
• feat(rivet-engine): udb key parser #3457
• fix(rivetkit): fix zod not validating body if content-type header not provided #3456
• fix(rivetkit): fix onError handler not working #3455
• chore(site): tweak wording #3454 👈 (View in Graphite)
• chore(site): fix generating examples #3453
• chore: create branch for v3 website changes on v2 #3304
• chore(website): flatten actors docs structure #3280
• chore(rivetkit): switch dynamic node imports to use require #3461
• chore(rivetkit-typescript): remove dependency on node modules #3460
• feat(site): add typedoc docs #3446
• chore(rivetkit): remove deprecated packages #3447
• chore(rivetkit): add support for conn params on onRequest and onWebSocket #3445
• feat(rivetkit): add asyncapi spec #3442
• chore(rivetkit): add actor router to the openapi spec #3441
• fix(rivetkit): skip sending RivetKit messages to conns that do not support it #3440
• fix(rivetkit): fix race condition with websocket open events #3439
• fix(rivetkit): standardize error metadata return type #3438
• fix(rivetkit): remove incorrect getEndpoint call in metadata handler #3433 : 1 other dependent PR (#3451 )
• feat(rivetkit): add json protocol support #3432
• chore(rivetkit): add required zod validation for json encoding #3431
• chore(rivetkit): add listing actors by only name to manager api #3430
• refactor(rivetkit): extract WebSocket protocol parsing to shared utility #3429
• refactor(rivetkit): restructure connection lifecycle contexts #3428
• chore(rivetkit): add WebSocketContext and RequestContext #3427
• chore(rivetkit): add conn type #3426
• chore(rivetkit): add connection for raw http #3425
• chore(rivetkit): rename onFetch to onRequest #3424
• refactor(rivetkit): add state manager for conn with symbol-based access #3423
• fix(rivetkit): use loggerWithoutContext for websocket error when actor undefined #3412
• feat(rivetkit): add GET /actors/names #3411
• feat(api-public): expose actor kv api #3410
• chore(rivetkit): auto-generate inspector token for engine driver #3409
• chore(rivetkit): close websockets on out of sequence messages #3404
• fix(rivetkit): properly apply clientEndpoint from metadata lookup #3402
• fix(rivetkit): properly handle msgIndex for hibernatable websocket reconnection #3401
• chore(rivetkit): rename onstart/onstop to onwake/onsleep #3422
• chore(rivetkit): split ActorInstance logic in to multiple classes #3421
• chore(rivetkit): move conns to separate persisted kv keys #3420
• chore(rivetkit): remove deprecated conn tokens & sse support #3419
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review: Website Wording Tweaks

This PR makes small but effective improvements to website copy across the marketing pages. Overall, the changes are positive and improve clarity.

What Works Well

1. Consistency in terminology: The change from real-time to realtime (one word) throughout the site creates better consistency and follows common industry convention for this compound adjective.

2. Improved link targets: Changing CTAs from /docs/quickstart/ to /docs is likely better for user experience, as it gives users the docs landing page rather than jumping directly to quickstart.

3. Better copy precision:

   • server-authoritative state is more precise than authoritative state (website/src/data/use-cases.ts:102)
   • flexible state management is more accurate than automatic state management for workflows (website/src/data/use-cases.ts:42)
   • Adding Open-source and self-hostable to hero description provides important context upfront (HeroSection.tsx:23)

4. Reordering use cases: Moving Multiplayer Apps ahead of Workflows in the display order (UseCases.tsx:145) may better highlight a key use case.

Minor Observations

1. Checkmark wording change (UseCases.tsx:77): The new wording is more concise. Cloud or on-prem is clearer, Supports your agent SDK is more user-focused, but Realtime might be too terse.

2. Consistency check: The term realtime is now used consistently, which is good. Verify this aligns with documentation and technical materials.

3. MCP description change (use-cases.ts:95): The new version is slightly more technical (stateful MCP) - ensure this terminology is accurate to how MCP is used in the product.

Suggestions for Future Consideration

1. Hero copy length: The hero description is now quite long with the addition of Open-source and self-hostable. Consider if this might be better as a separate line or callout.

2. Link consistency: Ensure the docs landing page provides clear next steps for new users who expect a quickstart path.

3. A/B testing opportunity: The use case reordering might be worth tracking.

Security and Performance

• No security concerns (text-only changes)
• No performance impact
• No broken links introduced (all changed paths are internal routes)

Code Quality

• Changes follow existing code patterns
• Proper TypeScript/TSX syntax maintained
• No formatting issues
• Consistent with Next.js/React conventions

Final Verdict

Approved - This is a solid set of website copy improvements. The changes enhance clarity, consistency, and positioning. The modifications are low-risk and align with marketing best practices.

Recommendation: Merge after confirming that:

1. The /docs landing page is well-suited for users clicking Get Started CTAs
2. The term realtime (one word) is consistently used in docs and technical materials
3. The stateful Model Context Protocol terminology accurately reflects the product capabilities

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-site	Error			Nov 13, 2025 3:24am
rivetkit-serverless	Error			Nov 13, 2025 3:24am

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-cloud	Ignored			Nov 13, 2025 3:24am
rivet-inspector	Ignored	Preview		Nov 13, 2025 3:24am

[claude]

Pull Request Review

Thank you for this PR! I've reviewed the changes and they look good overall. This is a straightforward copy/UX improvement for the marketing website.

Positive Points

1. Consistent Terminology: The change from "Real-Time" to "Realtime" (single word) is consistent and aligns with modern tech industry convention.

2. Improved Marketing Copy: Adding "Open-source and self-hostable" to the hero description highlights key differentiators. "Cloud or on-prem" is clearer than "Cloud & on-prem". "Supports your agent SDK" is more inclusive than "Works with AI SDK".

3. Better Use Case Ordering: Promoting "Agent Orchestration & MCP" to the top position makes sense given current market trends toward AI applications.

4. More Accurate Descriptions: "flexible state management" is more accurate than "automatic state management" for workflows. "server-authoritative state" is more technically precise.

Observations

1. Link Changes: All "Get Started" buttons now point to /docs instead of /docs/quickstart/. Verify that the /docs landing page guides users appropriately - if users land there without clear next steps, it could impact conversion.

2. Consistency Check: Recommend doing a full audit to ensure "realtime" terminology is consistent across all marketing pages, documentation, and code comments.

3. Use Case Reordering: Swapping "Workflows" and "Multiplayer Apps" positions changes the visual hierarchy. Ensure this aligns with your product strategy.

Overall Assessment

Status: Approved with minor recommendations

This is a clean, well-scoped PR that improves marketing copy clarity. No code quality, security, or performance concerns since these are static content changes.

• Test Coverage: N/A (marketing content only)
• Performance Impact: None
• Security Impact: None

[claude]

PR Review: chore(site): tweak wording

Summary

This PR updates marketing copy across the Rivet website homepage, focusing on terminology consistency and improving link destinations. The changes are primarily cosmetic and don't affect functionality.

Code Quality ✅

Positive aspects:

• Clean, focused changes with clear intent
• Consistent terminology improvements throughout
• No functional code changes, reducing risk
• Follows the repository's conventional commit format

Changes Analysis

1. Terminology Standardization

• ✅ "Real-Time" → "Realtime": Good consistency improvement. Modern convention favors "realtime" as a single word in technical contexts
• ✅ "Open-source and self-hostable": Important addition to the hero section that clearly communicates key value propositions

2. Link Improvements

• ✅ /docs/quickstart/ → /docs: Simplifies navigation entry point (3 occurrences)
• ⚠️ Recommendation: Verify that /docs provides a good landing experience for new users

3. Content Refinements

• ✅ "automatic state management" → "flexible state management": More accurate description
• ✅ "authoritative state" → "server-authoritative state": Clearer technical terminology
• ✅ "Cloud & on-prem" → "Cloud or on-prem": Better grammar
• ✅ "Works with AI SDK" → "Supports your agent SDK": More inclusive and accurate

4. Use Case Reordering

• ✅ Agent Orchestration moved to top: Smart prioritization that aligns with current market trends

Potential Issues 🔍

No critical issues identified, but some minor considerations:

1. Link Change: Ensure /docs route provides appropriate landing content
2. Copy Length: Verify hero description doesn't cause layout issues on mobile
3. Consistency: Check if other pages still use "real-time" (hyphenated)

Testing Recommendations 📋

• Visual regression testing on multiple viewport sizes
• Verify all updated links work correctly
• Check text doesn't overflow containers on mobile

Final Verdict: APPROVED ✅

This is a clean, low-risk PR that improves marketing copy consistency and accuracy.

Minor suggestions for follow-up:

1. Document the "realtime" style choice
2. Verify the /docs landing experience is optimal
3. Check for consistency across all site pages