Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[fix] Fix typos #1692

Closed
wants to merge 4 commits into from
Closed

Conversation

not-my-profile
Copy link
Collaborator

@not-my-profile not-my-profile commented Aug 8, 2023

This is the followup PR for #1691 (the first commit here actually belongs to that other PR, this PR will be rebased once that other PR has been merged).

The typos were found with the typos spell checker.
The 1st fix commit was created manually, the fixes in the 2nd fix commit were done by typos -w (but all manually reviewed), the fixes in the 3rd fix commit were again done manually.

I'm planning on introducing the typos spell checker into the CI in a followup PR to prevent the accidental introduction of known typos in the future.

While fixing all the typos in this repository, I discovered that these
comments don't actually make sense to me.

If we already touch these comments to fix the typos,
we should make sure they actually make sense.
Fix this typo first manually because otherwise `typos -w`
would correct it to "processes" ... we however want the singular.
While the typos spell checker could report these typos
it couldn't automatically fix them since there are multiple possible
corrections, e.g. `agains` could be `again` or `against`.
So this commit fixes these typos manually.
@andychu
Copy link
Contributor

andychu commented Aug 9, 2023

OK wow, we actually have a spell checker for the doc/ tree and the blog

But not one for the code

This change is good as long as it passes the CI -- I sent you an invite so you have permissions to run through the CI

@not-my-profile
Copy link
Collaborator Author

not-my-profile commented Aug 9, 2023

Ah is #1038 the relevant issue? I accepted the invite but the CI is still failing in the other PR after a force push because "$TOIL_KEY not set" and manually rerunning all jobs also didn't do the trick. What do I have to do to make it work?

@not-my-profile not-my-profile mentioned this pull request Aug 10, 2023
@not-my-profile
Copy link
Collaborator Author

Closing in favor of #1693 (since GitHub doesn't let you update the source branch of a PR).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants