From 147687dddb1d2057f5dc7a3ce791a6ea9a6ca3bc Mon Sep 17 00:00:00 2001 From: Himanshu Pandey Date: Wed, 3 Jul 2019 06:56:35 -0700 Subject: [PATCH] Added the hyperlink for pod in the page (#15113) * add the hyperlink for pod in the page * Changed Pod href to tooltip --- 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 4d31a2e190..fe869b1cd1 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 they detect and respond to cluster events (for example, starting up a new pod when a replication controller's `replicas` field is unsatisfied). +cluster (for example, scheduling), and they detect and respond to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment'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