[Docs] Correct integration tool lookup comment grammar - #3086
Draft
roomote-community[bot] wants to merge 1 commit into
Draft
roomote-community[bot] wants to merge 1 commit into
roomote-community[bot] wants to merge 1 commit into
Conversation
Contributor
Author
This branch has not been deployed
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 changed
Corrected the missing preposition in the shared integration-tool lookup comment so it reads, "Each runtime gathers its catalog in its own way."
Why this change was made
The original wording was a high-confidence grammar typo in a shipped developer-facing comment. The correction is independent of the existing open typo and documentation PRs and does not change any runtime contract.
Impact
The comment now accurately describes the two catalog-building paths without changing behavior. The package format check, TypeScript check, targeted oxlint, diff check, and repository pre-push suite passed; browser proof is not applicable to a source-comment-only change.