summaryrefslogtreecommitdiff
path: root/keps
diff options
context:
space:
mode:
authorBily Zhang <xcoder@tenxcloud.com>2018-11-06 01:42:13 +0800
committerk8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-11-05 09:42:13 -0800
commitd0d8d09f67693a1093fb61938f699b29d0bf4ebe (patch)
tree022852f012657535f2e91aadaeee476f7f417a9c /keps
parent79748734e6225769eb5186d0496adeb9f64789cf (diff)
Remove duplication (#2898)
* Remove depplication Signed-off-by: mooncake <xcoder@tenxcloud.com> * Remove duplciate words Signed-off-by: mooncake <xcoder@tenxcloud.com> * Fix issue Signed-off-by: mooncake <xcoder@tenxcloud.com>
Diffstat (limited to 'keps')
-rw-r--r--keps/sig-cli/0024-kubectl-plugins.md2
-rw-r--r--keps/sig-contributor-experience/0007-20180403-community-forum.md2
-rw-r--r--keps/sig-node/0030-20180906-quotas-for-ephemeral-storage.md2
3 files changed, 3 insertions, 3 deletions
diff --git a/keps/sig-cli/0024-kubectl-plugins.md b/keps/sig-cli/0024-kubectl-plugins.md
index 10db78ca..2d863d7e 100644
--- a/keps/sig-cli/0024-kubectl-plugins.md
+++ b/keps/sig-cli/0024-kubectl-plugins.md
@@ -138,7 +138,7 @@ or case-handling in `kubectl`.
In essence, a plugin binary must be able to run as a standalone process, completely independent of `kubectl`.
-* When `kubectl` is executed with a subcommand _foo_ that does not exist exist in the command tree, it will attempt to look
+* When `kubectl` is executed with a subcommand _foo_ that does not exist in the command tree, it will attempt to look
for a filename `kubectl-foo` (`kubectl-foo.exe` on Windows) in the user's `PATH` and execute it, relaying all arguments given
as well as all environment variables to the plugin child-process.
diff --git a/keps/sig-contributor-experience/0007-20180403-community-forum.md b/keps/sig-contributor-experience/0007-20180403-community-forum.md
index c187af69..04ceb38b 100644
--- a/keps/sig-contributor-experience/0007-20180403-community-forum.md
+++ b/keps/sig-contributor-experience/0007-20180403-community-forum.md
@@ -150,7 +150,7 @@ The site would be forum.k8s.io, and would be linked to from the homepage and maj
- [Discussion on the pros and cons of each](https://meta.discourse.org/t/discourse-vs-email-mailing-lists/54298)
- We have enough churn and new Working Groups that we could pilot a few, opt-in for SIGs that want to try it?
- A community forum is asynchronous, whereas chat is realtime.
- - This doesn't solve our Slack lock-in concerns, but can be a good first step in being more active in running our own community properties so that we can build out own own resources.
+ - This doesn't solve our Slack lock-in concerns, but can be a good first step in being more active in running our own community properties so that we can build out own resources.
- Ghost have [totally migrated to Discourse](https://twitter.com/johnonolan/status/980872508395188224?s=12) and shut down their Slack.
- We should keep an eye on this and see what data we can gleam from this. Engage with Ghost community folks to see what lessons they've learned.
- Not sure if getting rid of realtime chat entirely is a good idea either.
diff --git a/keps/sig-node/0030-20180906-quotas-for-ephemeral-storage.md b/keps/sig-node/0030-20180906-quotas-for-ephemeral-storage.md
index bf1ee5c9..a6c5aaba 100644
--- a/keps/sig-node/0030-20180906-quotas-for-ephemeral-storage.md
+++ b/keps/sig-node/0030-20180906-quotas-for-ephemeral-storage.md
@@ -519,7 +519,7 @@ appropriate end to end tests.
reasons for using quotas is indeed to improve performance. If this
is a problem in the field, merely turning off quotas (or selectively
disabling project quotas) on the filesystem in question will avoid
- the problem. Against the possibility that that cannot be done
+ the problem. Against the possibility that cannot be done
(because project quotas are needed for other purposes), we should
provide a way to disable use of quotas altogether via a feature
gate.