docs: Use “×” for dimensions #5502
Merged
Conversation
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
Much like `'' !== false` and `null !== undefined`, the typographical equivalent is `"x" !== "×"`. ☻
Contributor
Author
|
ping |
Contributor
Author
|
@lmccart ping 🙂 |
Member
|
Looks good. Thanks! |
Contributor
Author
|
🙏🏽 |
This was referenced Feb 3, 2022
Open
This was referenced Mar 7, 2022
1 task
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.
Typographically,
"x" !== "×". ☻Changes:
In comments, when referencing pixel dimensions or matrices, use “×” instead of “x”.
This does not include methods like
p5.Matrix.prototype.invert3x3, where “x” is part of the API and cannot change. It’s only for “prose”.PR Checklist
npm run lintpasses