Manual spell check fixes#60
Merged
Merged
Conversation
rvedotrc
reviewed
May 7, 2025
| ### Age-ify (A future age calculator) | ||
|
|
||
| > You are talking to a friend who suddently looks at you and asks: "How old will you be in 2045?" Hmm you remember the year you were born and try to do some calculation: Born in 1987 + 3 that's 1990. 90 - 40 is 50 + 5 thats 58. I will be 58! Wow that was painful! Let's fix that by making some code that automatically does this! | ||
| > You are talking to a friend who suddenly looks at you and asks: "How old will you be in 2045?" Hmm you remember the year you were born and try to do some calculation: Born in 1987 + 3 that's 1990. 90 - 40 is 50 + 5 that's 58. I will be 58! Wow that was painful! Let's fix that by making some code that automatically does this! |
Contributor
There was a problem hiding this comment.
Born in 1987 + 3 that's 1990. 90 - 40 is 50 + 5 that's 58. I will be 58!
"50 + 5 that's 58"? Not a spelling issue, but this could do with rewording! 😅 Perhaps in another PR.
Contributor
Author
There was a problem hiding this comment.
Good idea. Maybe, follow up PRs with pasting .md in a setup where Grammarly could flag issues.
rvedotrc
reviewed
May 7, 2025
rvedotrc
reviewed
May 7, 2025
rvedotrc
reviewed
May 7, 2025
rvedotrc
reviewed
May 7, 2025
rvedotrc
reviewed
May 7, 2025
rvedotrc
reviewed
May 7, 2025
rvedotrc
reviewed
May 7, 2025
rvedotrc
reviewed
May 7, 2025
rvedotrc
approved these changes
May 7, 2025
rvedotrc
left a comment
rvedotrc
left a comment
Contributor
There was a problem hiding this comment.
Approving because this fixes far more than it breaks, but there are a couple of things in there that merit a closer look, a think.
Thanks!
adamblanchard
approved these changes
May 8, 2025
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.
Went through all files and corrected spelling mistakes by using Code Spell Checker.
Used
en-GBin the settings of the extension.Many of the changes are
camelCaserelated, but there is a vast amount of missing letters, flipped letters, or extra letters.Besides the names of people, I ignored the following words:
Ignored everything in
legacy/nodejs, knowing it's being worked on, but forgot to skiplegacy/react. Hopefully we don't have annoying merge conflicts due to that 😬