summaryrefslogtreecommitdiff
path: root/keps
diff options
context:
space:
mode:
authorhalfcrazy <hackzhuyan@gmail.com>2018-02-04 22:41:56 +0800
committerhalfcrazy <hackzhuyan@gmail.com>2018-02-04 22:41:56 +0800
commitec3d22e7c5d6041aeca949f9a8f01a4596a5ab1f (patch)
tree5f105d97c45df3746d9aa546e66916e0cfed892b /keps
parentf2ad4746f799f4dafc2f04d68331f845c2866828 (diff)
doc: fix some typo
Diffstat (limited to 'keps')
-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 db2fe9fb..c0d113da 100644
--- a/keps/0001-kubernetes-enhancement-proposal-process.md
+++ b/keps/0001-kubernetes-enhancement-proposal-process.md
@@ -172,7 +172,7 @@ Metadata items:
* **owning-sig** Required
* The SIG that is most closely associated with this KEP. If there is code or
other artifacts that will result from this KEP, then it is expected that
- this SIG will take responsiblity for the bulk of those artifacts.
+ this SIG will take responsibility for the bulk of those artifacts.
* Sigs are listed as `sig-abc-def` where the name matches up with the
directory in the `kubernetes/community` repo.
* **participating-sigs** Optional
@@ -359,4 +359,4 @@ and durable storage.
- How reviewers and approvers are assigned to a KEP
- Example schedule, deadline, and time frame for each stage of a KEP
- Communication/notification mechanisms
-- Review meetings and escalation procedure \ No newline at end of file
+- Review meetings and escalation procedure