summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZhiqinYang <yangzhiqin@ghostcloud.cn>2017-10-22 18:05:18 +0800
committerGitHub <noreply@github.com>2017-10-22 18:05:18 +0800
commit22e056a4344d5dd90276ed8fc48753bfd234100a (patch)
tree1e1f6a84936f4b7668293f823cd9ee089148d310
parent2f5b6321b924c8e14fc026c63bc4d21f837621c4 (diff)
Update controller-ref.md
-rw-r--r--contributors/design-proposals/api-machinery/controller-ref.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/api-machinery/controller-ref.md b/contributors/design-proposals/api-machinery/controller-ref.md
index c5514345..ec2db536 100644
--- a/contributors/design-proposals/api-machinery/controller-ref.md
+++ b/contributors/design-proposals/api-machinery/controller-ref.md
@@ -237,7 +237,7 @@ This section lists considerations specific to a given controller.
* **ReplicaSet/ReplicationController**
- * These controllers currenly only enable ControllerRef behavior when the
+ * These controllers currently only enable ControllerRef behavior when the
Garbage Collector is enabled. When ControllerRef was first added to these
controllers, the main purpose was to enable server-side cascading deletion
via the Garbage Collector, so it made sense to gate it behind the same flag.