From 47b0f2f0a4a5c64856063750fdab0936f179f57d Mon Sep 17 00:00:00 2001 From: "Sahdev P. Zala" Date: Thu, 13 Jul 2017 15:15:28 -0400 Subject: [PATCH] Fix unresolvable element The incorrect element pointer gives an error, cannot resolve element with id updating-a-replication-controller, with a broken link. Fix it. --- docs/concepts/workloads/controllers/replicationcontroller.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/workloads/controllers/replicationcontroller.md b/docs/concepts/workloads/controllers/replicationcontroller.md index 8c3b12cd72..f7c0b4f723 100644 --- a/docs/concepts/workloads/controllers/replicationcontroller.md +++ b/docs/concepts/workloads/controllers/replicationcontroller.md @@ -137,7 +137,7 @@ ReplicationController thinks that it created the other pods. Kubernetes does no from doing this. If you do end up with multiple controllers that have overlapping selectors, you -will have to manage the deletion yourself (see [below](#updating-a-replication-controller)). +will have to manage the deletion yourself (see [below](#working-with-replicationcontrollers)). ### Multiple Replicas