Fix typos in docs and source comments#43889
Conversation
|
👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:
You'll need to revert all of the files you changed that match that list using GitHub Desktop or The complete list of files we can't accept are:
We also can't accept contributions to files in the content directory with frontmatter |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
Những( vốn từ) khi suy nghĩ về sự việc làm cá nhân sợ hãi hay bị tự loading không kiểm soát, |
Repo: github/docs (⭐ 16000)
Type: docs
Files changed: 3
Lines: +3/-3
What
Fixes four spelling errors across the repo:
content/actions/reference/workflows-and-actions/contexts.md:enviroment→environmentandevironment→environmentin thegithub.action_pathdescription.src/rest/components/get-rest-code-samples.ts:seperate→separatein an inline comment.src/content-render/tests/octicon.ts:non-existant→non-existentin a test name.Why
These are user-visible (the contexts.md change appears on docs.github.com) or developer-visible typos. They are harmless to fix and improve docs polish without altering behavior.
Testing
No behavioral change. The test name string is only an identifier displayed in test output; no assertions reference the old spelling. Verified via
grepthat no other code references the old test name. Did not run the full Vitest suite (out of scope for budget).Risk
Low — comment and string literal edits only; no logic touched.