docs: Don't use "lame" in documentation #14833
Closed
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.
I noticed that the docs for the new
class
features usecool/lame
as an example. The usage of the word "lame" feels a bit unnecessary in this case and some people (including me) consider it ableist. For example, Merriam-Webster say:(via https://www.merriam-webster.com/dictionary/lame)
My suggestion is to replace the wanted contrast with
cool/boring
and be done with it. I also quickly checked for other ableist words in examples but couldn't find any. (There were two "dumb"s in code comments, and I changed them as well, but they are not user-facing.)Before submitting the PR, please make sure you do the following
feat:
,fix:
,chore:
, ordocs:
.Ideally, include a test that fails without this PR but passes with it.If this PR changes code withinpackages/svelte/src
, add a changeset (npx changeset
).Tests and linting
pnpm test
and lint the project withpnpm lint