docs: replace "Coordinator" with "Reactor Platform" in happy-oyster README - #259
Merged
Merged
Conversation
… README Two prose mentions named the backend service the SDK talks to before its WebRTC connection opens - an internal component name with no meaning outside Reactor's own architecture. The NEXT_PUBLIC_COORDINATOR_URL env var name itself is left unchanged, since renaming it would need matching changes across .env.example and the actual app code, not just this README. Signed-off-by: ggoldens <german.goldenstein@gmail.com>
Same internal-terminology cleanup as the previous commit, extended to the env var itself and the local COORDINATOR_URL const in ho-client.tsx (renamed to REACTOR_API_URL), plus two more "Coordinator" mentions in code comments this file had that the README-only pass didn't touch. Purely a rename - no behavior change, same fallback to https://api.reactor.inc in both examples. A deployment of either example with the old env var name already set falls back to that default silently after this change rather than erroring, until the new name is set there and it's redeployed (Next.js bakes NEXT_PUBLIC_* vars in at build time). Signed-off-by: ggoldens <german.goldenstein@gmail.com>
prettier re-aligns every column once one cell's width changes. Signed-off-by: ggoldens <german.goldenstein@gmail.com>
ggoldens
marked this pull request as ready for review
August 24, 2026 22:39
Bryceoz
approved these changes
Aug 24, 2026
Contributor
Author
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
2 participants
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.
Why
Tracked as REA-5597. Companion to REA-5594 — the same fix in
reactor-team/docs's SDK reference pages.examples/happy-oyster/README.mdhad two prose mentions of "Coordinator," the internal backend-service name, with no meaning outside Reactor's own architecture.What changed
Two prose sentences reworded to "Reactor Platform":
getJwtresolver."REACTOR_API_KEY, no JWT."Left unchanged: the
NEXT_PUBLIC_COORDINATOR_URLenv var name (used in real app code across.env.example,route.ts, and components in bothhappy-oysterandlingbot-world-2) — renaming it needs matching code changes across both examples, out of scope for a terminology-only pass.lingbot-world-2/README.mdonly ever used the term via that same env var name, so nothing else to fix there.Testing
Prose-only README change, no code touched.
🤖 Generated with Claude Code