summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdam Pyle <admpyle@gmail.com>2016-04-25 09:18:26 +1000
committerAdam Pyle <admpyle@gmail.com>2016-04-25 09:18:26 +1000
commitb6ae1471393a155d2a8a2a382bd8f9976aa4a617 (patch)
tree9f8260109ff2a9e486b103d26dab9a609485019e
parent5080d0e7ac23f2c87947c68f916dbed4f9256299 (diff)
Incorrect attribute - docs - pod-security-context
Pod definition had incorrect spelling on attribute `securityContext` Also fixed the flow of Motivation intro paragraph.
-rw-r--r--pod-security-context.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod-security-context.md b/pod-security-context.md
index 420a006e..2899515c 100644
--- a/pod-security-context.md
+++ b/pod-security-context.md
@@ -40,7 +40,7 @@ order to correctly model pod- and container-level security concerns.
## Motivation
Currently, containers have a `SecurityContext` attribute which contains information about the
-security settings the container uses. In practice many of these attributes are uniform across all
+security settings the container uses. In practice, many of these attributes are uniform across all
containers in a pod. Simultaneously, there is also a need to apply the security context pattern
at the pod level to correctly model security attributes that apply only at a pod level.
@@ -277,7 +277,7 @@ to implement, explain, and support. Instead, we will approach backward compatib
securityContext:
runAsUser: 1001
- name: b
- securityContest:
+ securityContext:
runAsUser: 1002
```