From 8c1c0ad5ea32e64784fd41f3ca2cf920c7c1c2cd Mon Sep 17 00:00:00 2001
From: Rajakavitha1 <37059749+Rajakavitha1@users.noreply.github.com>
Date: Wed, 4 Apr 2018 23:02:08 +0530
Subject: [PATCH] Update service.md (#7972)

Fixed a 404 listed in: https://github.com/kubernetes/website/issues/7924
---
 docs/concepts/services-networking/service.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/concepts/services-networking/service.md b/docs/concepts/services-networking/service.md
index 555c485ec9..b5be551217 100644
--- a/docs/concepts/services-networking/service.md
+++ b/docs/concepts/services-networking/service.md
@@ -7,7 +7,7 @@ title: Services
 Kubernetes [`Pods`](/docs/concepts/workloads/pods/pod/) are mortal. They are born and when they die, they
 are not resurrected.  [`ReplicationControllers`](/docs/concepts/workloads/controllers/replicationcontroller/) in
 particular create and destroy `Pods` dynamically (e.g. when scaling up or down
-or when doing [rolling updates](/docs/user-guide/kubectl/{{page.version}}/#rolling-update)).  While each `Pod` gets its own IP address, even
+or when doing [rolling updates](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#rolling-update)).  While each `Pod` gets its own IP address, even
 those IP addresses cannot be relied upon to be stable over time. This leads to
 a problem: if some set of `Pods` (let's call them backends) provides
 functionality to other `Pods` (let's call them frontends) inside the Kubernetes