You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documentation only; no code or generated files change.
Checklist:
Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
The title of the PR states what changed and the related issues number (used for the release note).
My new feature complies with the feature status guidelines. (Not applicable: no feature.)
I have added a brief description of why this PR is necessary and/or what this PR solves.
Optional. My organization is added to USERS.md.
Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).
Prepared with help from Claude Code; I reviewed both changes.
Summary by CodeRabbit
Documentation
Corrected spelling errors in two proposal documents.
This documentation-only change fixes two typos in design proposals and has no runtime impact. It is safe to merge.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title "docs: fix typos in proposals (#30976)" matches the changeset. The PR corrects two spelling errors in design proposals under docs/proposals/: "againts" to "against" and "Depracating" to "Dep…
Description check
The description covers the required template items for a documentation-only fix. It links the issue with "Fixes #30976", lists both corrected spellings and their files, and explains why the change is …
Linked Issues check
Issue #30976 is the only directly linked issue. It requires two spelling fixes in docs/proposals/. The whole-PR diff (merge base e263590 to head 3240102) shows both fixes: line 90 of attach-debug-cont…
Out of Scope Changes check
The whole-PR diff changes exactly two lines in two files, both in docs/proposals/. Each change corrects a misspelling named in #30976. No code, generated files, or unrelated text change. Both hunks ar…
Full details: Title check
Explanation
The title "docs: fix typos in proposals (#30976)" matches the changeset. The PR corrects two spelling errors in design proposals under docs/proposals/: "againts" to "against" and "Depracating" to "Deprecating". The title names the type of change, the area, and the issue number. It does not name the specific words fixed, but that detail is not required.
Full details: Description check
Explanation
The description covers the required template items for a documentation-only fix. It links the issue with "Fixes #30976", lists both corrected spellings and their files, and explains why the change is needed. The checklist is complete, with the inapplicable items marked with reasons. The checklist boxes for the release-note and title conventions are checked, and the DCO sign-off is confirmed. Two template items remain unchecked, but the author explains they do not apply. The description therefore meets the template.
Full details: Linked Issues check
Explanation
Issue #30976 is the only directly linked issue. It requires two spelling fixes in docs/proposals/. The whole-PR diff (merge base e263590 to head 3240102) shows both fixes: line 90 of attach-debug-containers.md changes "againts" to "against", and line 198 of multiple-sources-for-applications.md changes "Depracating" to "Deprecating". No other text changes. The issue has no coding requirements beyond these edits. Its expected outcome, that both words are spelled correctly, is met. Automated tests do not apply to this documentation-only change.
Full details: Out of Scope Changes check
Explanation
The whole-PR diff changes exactly two lines in two files, both in docs/proposals/. Each change corrects a misspelling named in #30976. No code, generated files, or unrelated text change. Both hunks are within scope.
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.
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
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.
Fixes #30976
Fixes two spelling mistakes in design proposals under
docs/proposals/:attach-debug-containers.md: "againts" → "against"multiple-sources-for-applications.md: "Depracating" → "Deprecating"Documentation only; no code or generated files change.
Checklist:
Prepared with help from Claude Code; I reviewed both changes.
Summary by CodeRabbit