-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 misspelling in some docs files #4551
Conversation
Signed-off-by: chymy <[email protected]>
Hi @chymy. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/ok-to-test
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
This merged while I was reviewing, left a couple of comment as I don't quite agree with all the changes here, WDYT @chymy
@@ -238,7 +238,7 @@ libraries so the issue of support should be solved with this contract. | |||
a single yaml file. These artifacts will need to be “grouped” together to | |||
support current retrieval mechanisms. Currently, `clusterctl config cluster` | |||
retrieves templates from multiple sources such as ConfigMaps within a | |||
cluster, URL, Github Repository, Local Repository and even the overrides | |||
cluster, URL, Github Repository, Local Repository and even the overrides' |
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.
Not sure this apostrophe is required here, what's the motivation on this one? I think overrides directory
forms one noun here rather than overrides
owning the directory 🤔
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 your reviews @JoelSpeed , you are right, I will revise it.
@@ -109,7 +109,7 @@ lifecycle hook. | |||
- Create a mechanism to signal what lifecycle point a machine is at currently. | |||
- Dictate implementation of controllers that respond to the hooks. | |||
- Implement ordering in the machine-controller. | |||
- Require anyone use these hooks for normal machine operations, these are | |||
- Require anyone uses these hooks for normal machine operations, these are |
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.
I think in this context and format, use
is preferred over uses
. It think these bullets are imperative so that would make me lean towards use
over uses
anyway
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.
I think we should be Require anyone to use ...
, this is require...to do something
grammar
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.
Require anyone to use
seems ok to me
What this PR does / why we need it:
Fix misspelling in some docs files
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #