diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-02-10 21:42:49 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-10 21:42:49 -0800 |
| commit | b5b05104699d190a190418c64e4dfdb46383fb02 (patch) | |
| tree | e9938d6f5c92f653cff9b95194d0bce7651aec6d | |
| parent | e2a648ecf0dbe826de6b6f2e27e02d5599867725 (diff) | |
| parent | 6a8aa54ea69b48e327236cdedd41a9b4a4a2c063 (diff) | |
Merge pull request #1786 from JaredTan95/master
typo: fix some duplication problems in keps.
| -rw-r--r-- | keps/0000-kep-template.md | 2 | ||||
| -rw-r--r-- | keps/sig-cluster-lifecycle/0004-bootstrap-checkpointing.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/keps/0000-kep-template.md b/keps/0000-kep-template.md index 105d3f6a..1b2dbd6d 100644 --- a/keps/0000-kep-template.md +++ b/keps/0000-kep-template.md @@ -128,7 +128,7 @@ This might be a good place to talk about core concepts and how they releate. What are the risks of this proposal and how do we mitigate. Think broadly. -For example, consider both security security and how this will impact the larger kubernetes ecosystem. +For example, consider both security and how this will impact the larger kubernetes ecosystem. ## Graduation Criteria diff --git a/keps/sig-cluster-lifecycle/0004-bootstrap-checkpointing.md b/keps/sig-cluster-lifecycle/0004-bootstrap-checkpointing.md index 88b5bdc3..7538f159 100644 --- a/keps/sig-cluster-lifecycle/0004-bootstrap-checkpointing.md +++ b/keps/sig-cluster-lifecycle/0004-bootstrap-checkpointing.md @@ -119,7 +119,7 @@ Graduating this feature is a responsibility of sig-cluster-lifecycle and sig-node to determine over the course of the 1.10 and 1.11 releases. History has taught us that initial implementations often have a tendency overlook use cases and require refinement. It is the goal of this proposal to have an -initial alpha implementation of of bootstrap checkpoining in the 1.9 cycle, +initial alpha implementation of bootstrap checkpoining in the 1.9 cycle, and further refinement will occur after we have validated it across several deployments. |