diff options
| author | Victor Boctor <vboctor@gmail.com> | 2018-11-13 17:37:10 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-11-13 17:37:10 -0800 |
| commit | e3ed83bc07e60a0461b75dd7a905cd25a4daf879 (patch) | |
| tree | ccf8e20dd95518c0fed27d580486148b1a4df783 | |
| parent | bf62d68498df66f88b27394f3125c58deb4432df (diff) | |
Fix typos
| -rw-r--r-- | keps/0001-kubernetes-enhancement-proposal-process.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/keps/0001-kubernetes-enhancement-proposal-process.md b/keps/0001-kubernetes-enhancement-proposal-process.md index 4594b716..9dc65553 100644 --- a/keps/0001-kubernetes-enhancement-proposal-process.md +++ b/keps/0001-kubernetes-enhancement-proposal-process.md @@ -274,7 +274,7 @@ failure of the KEP process are - distribution of time a KEP spends in each state - KEP rejection rate - PRs referencing a KEP merged per week -- number of issued open which reference a KEP +- number of issues open which reference a KEP - number of contributors who authored a KEP - number of contributors who authored a KEP for the first time - number of orphaned KEPs @@ -330,7 +330,7 @@ this proposal attempts to place these concerns within a general framework. [accepted design and a proposal]: https://github.com/kubernetes/community/issues/914 [the organization of design proposals]: https://github.com/kubernetes/community/issues/918 -### Github issues vs. KEPs +### GitHub issues vs. KEPs The use of GitHub issues when proposing changes does not provide SIGs good facilities for signaling approval or rejection of a proposed change to Kubernetes |