From 7a6a8e1915f76bd6911e54e13f1112fe008ac837 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E7=8E=8B=28Wang=29?= Date: Tue, 30 Apr 2019 22:33:37 +0900 Subject: [PATCH] fix an offense against the style guide (#14102) > Use code style for object field names --- content/en/docs/concepts/overview/components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/overview/components.md b/content/en/docs/concepts/overview/components.md index 4373482ffc..80943546d2 100644 --- a/content/en/docs/concepts/overview/components.md +++ b/content/en/docs/concepts/overview/components.md @@ -18,7 +18,7 @@ deliver a functioning Kubernetes cluster. ## Master Components Master components provide the cluster's control plane. Master components make global decisions about the -cluster (for example, scheduling), and detecting and responding to cluster events (starting up a new pod when a replication controller's 'replicas' field is unsatisfied). +cluster (for example, scheduling), and detecting and responding to cluster events (starting up a new pod when a replication controller's `replicas` field is unsatisfied). Master components can be run on any machine in the cluster. However, for simplicity, set up scripts typically start all master components on