From efc3c488ea2577aee4b42158006e638f8dcd2364 Mon Sep 17 00:00:00 2001
From: Nate Reid <45366367+natereid72@users.noreply.github.com>
Date: Wed, 13 Jan 2021 17:04:26 -0500
Subject: [PATCH] Update service.md

---
 content/en/docs/concepts/services-networking/service.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md
index 58d9bb9a2d..d3747323d1 100644
--- a/content/en/docs/concepts/services-networking/service.md
+++ b/content/en/docs/concepts/services-networking/service.md
@@ -238,7 +238,7 @@ There are a few reasons for using proxying for Services:
 
 ### User space proxy mode {#proxy-mode-userspace}
 
-In this mode, kube-proxy watches the Kubernetes master for the addition and
+In this mode, kube-proxy watches the Kubernetes control plane for the addition and
 removal of Service and Endpoint objects. For each Service it opens a
 port (randomly chosen) on the local node.  Any connections to this "proxy port"
 are proxied to one of the Service's backend Pods (as reported via