From 1a6df75cf534cb344a88ba27cb97504bbbcc1b0c Mon Sep 17 00:00:00 2001 From: Jared Date: Tue, 6 Dec 2016 17:30:17 -0800 Subject: [PATCH] Update authentication.md --- docs/admin/authentication.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/admin/authentication.md b/docs/admin/authentication.md index 82a23e10c0..ce6aaf9f45 100644 --- a/docs/admin/authentication.md +++ b/docs/admin/authentication.md @@ -36,8 +36,8 @@ or be treated as an anonymous user. ## Authentication strategies Kubernetes uses client certificates, bearer tokens, an authenticating proxy, or HTTP basic auth to -authenticate API requests through authentication plugins. As HTTP request are -made to the API server plugins attempts to associate the following attributes +authenticate API requests through authentication plugins. As HTTP requests are +made to the API server, plugins attempt to associate the following attributes with the request: * Username: a string which identifies the end user. Common values might be `kube-admin` or `jane@example.com`.