Fix weekly spelling check - #44962
Merged
Merged
Conversation
github-actions
Bot
added
Content:CSS
dipikabh
approved these changes
Aug 4, 2026
dipikabh
left a comment
dipikabh
left a comment
Contributor
There was a problem hiding this comment.
Looks good, thank you for the PR!
Contributor
|
Preview URLs (1 page) |
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
3 participants
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
Adds valid proper names, non-English words, technical terms, and example identifiers reported by the weekly cSpell check to the appropriate dictionaries. Also fixes the invalid
willchangeCSS declaration by changing it towill-change.Motivation
The weekly spelling check was failing because several valid words used in MDN documentation were missing from the project’s custom cSpell dictionaries. Adding these words prevents false-positive spelling errors, while correcting
willchangefixes an actual error in the CSS example.Additional details
The following validation completed successfully:
Related issues and pull requests
Fixes #44925