From f477fd8d376fa1928ce4b009e2cb43b1e252a2a2 Mon Sep 17 00:00:00 2001 From: Fabio Alessandro Locati Date: Sat, 18 Apr 2020 14:45:57 +0200 Subject: [PATCH] control plane should not be capitalized --- content/en/docs/concepts/overview/components.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/overview/components.md b/content/en/docs/concepts/overview/components.md index e5d61cf9e4..d1d4a1e7fb 100644 --- a/content/en/docs/concepts/overview/components.md +++ b/content/en/docs/concepts/overview/components.md @@ -25,10 +25,10 @@ Here's the diagram of a Kubernetes cluster with all the components tied together {{% capture body %}} ## Control Plane Components -The Control Plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's `replicas` field is unsatisfied). +The control plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's `replicas` field is unsatisfied). -Control Plane components can be run on any machine in the cluster. However, -for simplicity, set up scripts typically start all Control Plane components on +Control plane components can be run on any machine in the cluster. However, +for simplicity, set up scripts typically start all control plane components on the same machine, and do not run user containers on this machine. See [Building High-Availability Clusters](/docs/admin/high-availability/) for an example multi-master-VM setup.