From 774832039cc4f05255bf239a3afc435076aa6ec5 Mon Sep 17 00:00:00 2001 From: Adam Eivy Date: Thu, 2 Jun 2016 15:37:21 -0700 Subject: [PATCH] "rather then" -> "rather than" --- docs/user-guide/replication-controller/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/replication-controller/index.md b/docs/user-guide/replication-controller/index.md index 9dbf4f3a93..44546a4ab0 100644 --- a/docs/user-guide/replication-controller/index.md +++ b/docs/user-guide/replication-controller/index.md @@ -15,7 +15,7 @@ replication controller are automatically replaced if they fail, get deleted, or For example, your pods get re-created on a node after disruptive maintenance such as a kernel upgrade. For this reason, we recommend that you use a replication controller even if your application requires only a single pod. You can think of a replication controller as something similar to a process supervisor, -but rather then individual processes on a single node, the replication controller supervises multiple pods +but rather than individual processes on a single node, the replication controller supervises multiple pods across multiple nodes. Replication Controller is often abbreviated to "rc" or "rcs" in discussion, and as a shortcut in