From 519f8ec5bcb477f38ef3fbd908a8cc03772561e5 Mon Sep 17 00:00:00 2001
From: Matthew Grotheer <34672297+mdgrotheer@users.noreply.github.com>
Date: Fri, 16 Oct 2020 09:20:23 -0700
Subject: [PATCH] Update authentication.md

Small grammatical corrections
---
 content/en/docs/reference/access-authn-authz/authentication.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/reference/access-authn-authz/authentication.md b/content/en/docs/reference/access-authn-authz/authentication.md
index a97dca823f..e2e2d5c437 100644
--- a/content/en/docs/reference/access-authn-authz/authentication.md
+++ b/content/en/docs/reference/access-authn-authz/authentication.md
@@ -29,7 +29,7 @@ It is assumed that a cluster-independent service manages normal users in the fol
 In this regard, _Kubernetes does not have objects which represent normal user
 accounts._ Normal users cannot be added to a cluster through an API call.
 
-Even though normal user cannot be added via an API call, but any user that
+Even though a normal user cannot be added via an API call, any user that
 presents a valid certificate signed by the cluster's certificate authority
 (CA) is considered authenticated. In this configuration, Kubernetes determines
 the username from the common name field in the 'subject' of the cert (e.g.,