summaryrefslogtreecommitdiff
path: root/pod-security-context.md
diff options
context:
space:
mode:
authorChristian Koep <christiankoep@gmail.com>2016-10-18 10:12:26 +0200
committerChristian Koep <christiankoep@gmail.com>2016-10-31 18:31:08 +0100
commit6cd1f8b4d2ff594d9e7faf2c47cb3cdc14d5ffab (patch)
tree391d49837be7a3b11a2b2a7ce3d53072f9e3a5a8 /pod-security-context.md
parent544bddb652b98ad9bb7678004a6e8b99df58995a (diff)
Fix typos and linted_packages sorting
Diffstat (limited to 'pod-security-context.md')
-rw-r--r--pod-security-context.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod-security-context.md b/pod-security-context.md
index eb7b7141..bfaffa59 100644
--- a/pod-security-context.md
+++ b/pod-security-context.md
@@ -56,7 +56,7 @@ attributes.
Some use cases require the containers in a pod to run with different security settings. As an
example, a user may want to have a pod with two containers, one of which runs as root with the
privileged setting, and one that runs as a non-root UID. To support use cases like this, it should
-be possible to override appropriate (ie, not intrinsically pod-level) security settings for
+be possible to override appropriate (i.e., not intrinsically pod-level) security settings for
individual containers.
## Proposed Design