summaryrefslogtreecommitdiff
path: root/security.md
diff options
context:
space:
mode:
authorEd Costello <epc@epcostello.com>2015-06-11 01:11:44 -0400
committerEd Costello <epc@epcostello.com>2015-06-12 18:47:28 -0400
commita407b64a3d2be8e3ddca9192609c72e92b64a6a9 (patch)
tree27c068b7d9dbb57f4abb866e739268f18c58e043 /security.md
parent867825849dbdd7105fd037239a64397bf2c8d969 (diff)
Copy edits for spelling errors and typos
Signed-off-by: Ed Costello <epc@epcostello.com>
Diffstat (limited to 'security.md')
-rw-r--r--security.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/security.md b/security.md
index 26d543c9..6ea611b7 100644
--- a/security.md
+++ b/security.md
@@ -22,13 +22,13 @@ While Kubernetes today is not primarily a multi-tenant system, the long term evo
We define "user" as a unique identity accessing the Kubernetes API server, which may be a human or an automated process. Human users fall into the following categories:
-1. k8s admin - administers a kubernetes cluster and has access to the undelying components of the system
+1. k8s admin - administers a kubernetes cluster and has access to the underlying components of the system
2. k8s project administrator - administrates the security of a small subset of the cluster
3. k8s developer - launches pods on a kubernetes cluster and consumes cluster resources
Automated process users fall into the following categories:
-1. k8s container user - a user that processes running inside a container (on the cluster) can use to access other cluster resources indepedent of the human users attached to a project
+1. k8s container user - a user that processes running inside a container (on the cluster) can use to access other cluster resources independent of the human users attached to a project
2. k8s infrastructure user - the user that kubernetes infrastructure components use to perform cluster functions with clearly defined roles