From b4eae4efd565b219333ca0894da442c9d759891f Mon Sep 17 00:00:00 2001
From: knight <1004815462@qq.com>
Date: Wed, 6 Feb 2019 10:20:50 +0800
Subject: replace proxy with kube-proxy

---
 contributors/design-proposals/auth/security.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/contributors/design-proposals/auth/security.md b/contributors/design-proposals/auth/security.md
index 846b2c39..d2c3e0e2 100644
--- a/contributors/design-proposals/auth/security.md
+++ b/contributors/design-proposals/auth/security.md
@@ -181,13 +181,13 @@ An administrator must be able to properly secure Kubernetes at a policy level,
 rather than at an implementation level, and schema changes over time should not
 risk unintended security leaks.
 
-Both the Kubelet and Kube Proxy need information related to their specific roles -
-for the Kubelet, the set of pods it should be running, and for the Proxy, the
-set of services and endpoints to load balance. The Kubelet also needs to provide
+Both the kubelet and kube-proxy need information related to their specific roles -
+for the kubelet, the set of pods it should be running, and for the kube-proxy, the
+set of services and endpoints to load balance. The kubelet also needs to provide
 information about running pods and historical termination data. The access
-pattern for both Kubelet and Proxy to load their configuration is an efficient
-"wait for changes" request over HTTP. It should be possible to limit the Kubelet
-and Proxy to only access the information they need to perform their roles and no
+pattern for both kubelet and kube-proxy to load their configuration is an efficient
+"wait for changes" request over HTTP. It should be possible to limit the kubelet
+and kube-proxy to only access the information they need to perform their roles and no
 more.
 
 The controller manager for Replication Controllers and other future controllers
-- 
cgit v1.2.3