From f3a000757ce10bb51465bd210406def41ddef3b2 Mon Sep 17 00:00:00 2001 From: YuPengZTE Date: Tue, 20 Sep 2016 16:21:14 +0800 Subject: [PATCH] ie. is should be i.e. Signed-off-by: YuPengZTE --- docs/design/security_context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design/security_context.md b/docs/design/security_context.md index 1bc654f88c3..db0d4390b61 100644 --- a/docs/design/security_context.md +++ b/docs/design/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).