This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
Spelling #15603
Merged
Spelling #15603
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description of the Change
Spelling fixes
Alternate Designs
None of the misspellings appeared particularly intentional.
Why Should This Be In Core?
Misspellings hurt project health.
Benefits
It's easier to use healthier projects, and there are fewer errors when people try to write code with the expected spelling (which doesn't match the used misspelling).
Possible Drawbacks
It's possible that a misspelling is intentional, or that it's an APIand thus is hard to change (JavaScript and stylesheet are the only likely candidates in this series).