-
-
Notifications
You must be signed in to change notification settings - Fork 591
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 across the project #1306
Conversation
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
Please don't change the change logs. These are auto generated and from the commits |
5c57adf
to
dd81722
Compare
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.
@ematipico Done 💯
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.
@snitin315 Thanks for submitting this PR!
Have you used any tool to get these errors ( Referring to the screenshot in the corresponding issue ) ?
It would be better to automate detecting these grammatical changes by integrating it to CI.
@snitin315 Also the files under |
@ematipico @rishabh3112 I used misspell to find and correct typos. |
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!
What kind of change does this PR introduce?
Fixes #1305
Did you add tests for your changes?
NA
If relevant, did you update the documentation?
NA
Summary
Fixed all typos.
Does this PR introduce a breaking change?
NO
Other information
NA