Skip to content

Fix Typos in Documentation and Comments #142307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from

Conversation

leopardracer
Copy link

Description:
This pull request corrects several typographical errors in documentation and comments across the codebase. Specifically, it fixes the spelling of "vulnerabilities," "inherited," and "because" in the relevant files. These changes improve the clarity and professionalism of the code documentation without affecting any functionality.

@rustbot
Copy link
Collaborator

rustbot commented Jun 10, 2025

r? @joboet

rustbot has assigned @joboet.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Jun 10, 2025
@leopardracer
Copy link
Author

@joboet

@tgross35
Copy link
Contributor

We don't accept small typo fixes as they tend to be a popular way to farm identities or otherwise encourage spam. A more substantive rewording is welcome, but please do not make typo-only pull requests.

See also #58619.

@tgross35 tgross35 closed this Jun 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants