mirror of https://github.com/kubernetes/kops.git
One space after a period. Periods after sentences.
This commit is contained in:
parent
28363f5d01
commit
c147517c40
12
README.md
12
README.md
|
@ -92,10 +92,10 @@ What this means:
|
|||
__Issues__
|
||||
* Help read and triage issues, assist when possible.
|
||||
* Point out issues that are duplicates, out of date, etc.
|
||||
- Even if you don't have tagging permissions, make a note and tag maintainers. (`/close`,`/dupe #127`)
|
||||
- Even if you don't have tagging permissions, make a note and tag maintainers (`/close`,`/dupe #127`).
|
||||
|
||||
__Pull Requests__
|
||||
* Read and review the code. Leave comments, questions, and critiques (`/lgtm` )
|
||||
* Read and review the code. Leave comments, questions, and critiques (`/lgtm` ).
|
||||
* Download, compile, and run the code and make sure the tests pass (make test).
|
||||
- Also verify that the new feature seems sane, follows best architectural patterns, and includes tests.
|
||||
|
||||
|
@ -147,17 +147,17 @@ If you think you have found a bug please follow the instructions below.
|
|||
|
||||
- Please spend a small amount of time giving due diligence to the issue tracker. Your issue might be a duplicate.
|
||||
- Set `-v 10` command line option and save the log output. Please paste this into your issue.
|
||||
- Note the version of kops you are running (from `kops version`), and the command line options you are using
|
||||
- Open a [new issue](https://github.com/kubernetes/kops/issues/new)
|
||||
- Note the version of kops you are running (from `kops version`), and the command line options you are using.
|
||||
- Open a [new issue](https://github.com/kubernetes/kops/issues/new).
|
||||
- Remember users might be searching for your issue in the future, so please give it a meaningful title to helps others.
|
||||
- Feel free to reach out to the kops community on [kubernetes slack](https://github.com/kubernetes/community/blob/master/communication.md#social-media)
|
||||
- Feel free to reach out to the kops community on [kubernetes slack](https://github.com/kubernetes/community/blob/master/communication.md#social-media).
|
||||
|
||||
|
||||
### Features
|
||||
|
||||
We also use the issue tracker to track features. If you have an idea for a feature, or think you can help kops become even more awesome follow the steps below.
|
||||
|
||||
- Open a [new issue](https://github.com/kubernetes/kops/issues/new)
|
||||
- Open a [new issue](https://github.com/kubernetes/kops/issues/new).
|
||||
- Remember users might be searching for your issue in the future, so please give it a meaningful title to helps others.
|
||||
- Clearly define the use case, using concrete examples. EG: I type `this` and kops does `that`.
|
||||
- Some of our larger features will require some design. If you would like to include a technical design for your feature please include it in the issue.
|
||||
|
|
|
@ -329,7 +329,7 @@ spec:
|
|||
|
||||
Full documentation is accessible via [godocs](https://godoc.org/k8s.io/kops/pkg/apis/kops#InstanceGroupSpec).
|
||||
|
||||
Instance Groups map to auto scale groups in AWS, and Instance Groups in GCE. They are an API level description of a group of compute instances used as Masters or Nodes.
|
||||
Instance Groups map to Auto Scaling Groups in AWS, and Instance Groups in GCE. They are an API level description of a group of compute instances used as Masters or Nodes.
|
||||
|
||||
More documentation is available in the [Instance Group](instance_groups.md) document.
|
||||
|
||||
|
|
Loading…
Reference in New Issue