summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-11-14 10:25:03 -0800
committerGitHub <noreply@github.com>2018-11-14 10:25:03 -0800
commite26747773e35bd27a2d5abfb1f5ea70723a168f6 (patch)
tree21b19bfbb83c992367c3975f51ad7b48db2bd65d
parent6d16c3337481e10e5d2622b688f04a8c6655a385 (diff)
parente3ed83bc07e60a0461b75dd7a905cd25a4daf879 (diff)
Merge pull request #2936 from vboctor/patch-1
Fix typos in KEP-0001
-rw-r--r--keps/0001-kubernetes-enhancement-proposal-process.md4
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