diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2016-10-15 08:50:02 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-10-15 08:50:02 -0700 |
| commit | a4d315e334d71e1cf501b83b692b879fd65847b9 (patch) | |
| tree | e693c77132bf9479587776120dd6f09adc588cc7 | |
| parent | c81fec4437f75c4235ae2bfd4dafc484abca43d5 (diff) | |
| parent | 07619709a9cebb66e374866272ff714dfe9ae6ac (diff) | |
Merge pull request #33076 from YuPengZTE/devIE
Automatic merge from submit-queue
ie. should be i.e.
| -rw-r--r-- | security_context.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/security_context.md b/security_context.md index 1bc654f8..db0d4390 100644 --- a/security_context.md +++ b/security_context.md @@ -86,7 +86,7 @@ shared disks. constraints to isolate containers from their host. Different use cases need different settings. * The concept of a security context should not be tied to a particular security -mechanism or platform (ie. SELinux, AppArmor) +mechanism or platform (i.e. SELinux, AppArmor) * Applying a different security context to a scope (namespace or pod) requires a solution such as the one proposed for [service accounts](service_accounts.md). |