docs: refine reader-facing contract language#49
Merged
Conversation
Merged
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
This change makes the documentation and API hints read as one account of the same runtime model.
The existing docs already lead readers toward a few stable questions: where was this relationship created, which scope still owns it, and does this API return a result now or a handle to observe later? This pass keeps the surrounding language closer to those questions, so readers can carry the same mental model from guide prose into topic pages, concept pages, Explorer copy, and editor hints without switching vocabulary along the way.
The emphasis is on continuity rather than new surface area. Values can still cross JavaScript boundaries, futures can still be observed after they are returned, and scope-owned work still converges at the boundary that owns it. The copy now keeps those ideas attached to the reader-facing contract instead of drifting into local phrasing that makes each page sound slightly separate from the rest.
Notes
This is a wording refinement over the existing model, not a runtime behavior change.