diff --git a/docs/concepts/index.md b/docs/concepts/index.md
index a14a889e55..dd241d15a6 100644
--- a/docs/concepts/index.md
+++ b/docs/concepts/index.md
@@ -10,10 +10,10 @@ To work with Kubernetes, you use *Kubernetes API objects* to describe your clust
 
 Once you've set your desired state, the *Kubernetes Control Plane* works to make the cluster's current state match the desired state. To do so, Kubernetes performs a variety of tasks automatically--such as starting or restarting containers, scaling the number of replicas of a given application, and more. The Kubernetes Control Plane consists of a collection of processes running on your cluster: 
 
-* The **Kubernetes Master** is a collection of three processes that run on a single node in your cluster, which is designated as the master node. Those processes are: kube-apiserver, kube-controller-manager and kube-scheduler.
+* The **Kubernetes Master** is a collection of three processes that run on a single node in your cluster, which is designated as the master node. Those processes are: [kube-apiserver](/docs/admin/kube-apiserver/), [kube-controller-manager](/docs/admin/kube-controller-manager/) and [kube-scheduler](/docs/admin/kube-scheduler/).
 * Each individual non-master node in your cluster runs two processes:
-  * **kubelet**, which communicates with the Kubernetes Master.
-  * **kube-proxy**, a network proxy which reflects Kubernetes networking services on each node.
+  * **[kubelet](/docs/admin/kubelet/)**, which communicates with the Kubernetes Master.
+  * **[kube-proxy](/docs/admin/kube-proxy/)**, a network proxy which reflects Kubernetes networking services on each node.
 
 ## Kubernetes Objects