-
Notifications
You must be signed in to change notification settings - Fork 604
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
Correct some typos across the codebase #6280
Conversation
Hello. You may have forgotten to update the changelog!
|
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.
Since the individual changes are so small, optional suggestion to add a changelog entry under the "Documentation" section, but otherwise LGTM!
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6280 +/- ##
=======================================
Coverage 99.70% 99.70%
=======================================
Files 444 444
Lines 42133 42133
=======================================
Hits 42008 42008
Misses 125 125 ☔ View full report in Codecov by Sentry. |
Thanks @dwierichs! I suggested one more change in this PR (I noticed it this morning) |
Just one more suggestion for this PR
**Context:** As title says. **Description of the Change:** **Benefits:** Fewer typos. A unified way to write the word "parametrize", which coincides with the naming of classes like `ParametrizedEvolution` or pytest's function `mark.parametrize`. **Possible Drawbacks:** **Related GitHub Issues:** --------- Co-authored-by: Pietropaolo Frisoni <pietropaolo.frisoni@xanadu.ai>
Context:
As title says.
Description of the Change:
Benefits:
Fewer typos.
A unified way to write the word "parametrize", which coincides with the naming of classes like
ParametrizedEvolution
or pytest's functionmark.parametrize
.Possible Drawbacks:
Related GitHub Issues: