-
-
Notifications
You must be signed in to change notification settings - Fork 512
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
chore: fix typos #2940
chore: fix typos #2940
Conversation
✅ Deploy Preview for testcontainers-go ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this, just a few comments to get this in
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for this 🙇
I'm changing the PR title to chore: fix typos
as it's not changing the existing behaviour, but fixing typos both in code and the docs. Therefore the PR will land in the Housekeeping
section in the release notes.
BTW @NathanBaulch did you use an automated tool to find the typos? If so, I'd like to use it as part of the lint phase. |
I used a combination of https://github.com/crate-ci/typos (automated) and the built-in IntelliJ language tools (manual). |
I retriggered Netlify's build and created the deployment, although it did not update the GH checks. LGTM anyway |
What does this PR do?
Fixes a bunch of typos.
Why is it important?
Improves readability and professionalism.
The top typos are: