From 70eba58d3b6b177ca3f7cfaec485cc1caadd2778 Mon Sep 17 00:00:00 2001
From: Tej-Singh-Rana <58101587+Tej-Singh-Rana@users.noreply.github.com>
Date: Sat, 19 Sep 2020 16:48:42 +0530
Subject: [PATCH] Contex to Context

---
 content/en/docs/concepts/security/pod-security-standards.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/security/pod-security-standards.md b/content/en/docs/concepts/security/pod-security-standards.md
index 2dddc711a9..18c1b7e862 100644
--- a/content/en/docs/concepts/security/pod-security-standards.md
+++ b/content/en/docs/concepts/security/pod-security-standards.md
@@ -292,7 +292,7 @@ Containers at runtime. Security contexts are defined as part of the Pod and cont
 in the Pod manifest, and represent parameters to the container runtime.
 
 Security policies are control plane mechanisms to enforce specific settings in the Security Context,
-as well as other parameters outside the Security Contex. As of February 2020, the current native
+as well as other parameters outside the Security Context. As of February 2020, the current native
 solution for enforcing these security policies is [Pod Security
 Policy](/docs/concepts/policy/pod-security-policy/) - a mechanism for centrally enforcing security
 policy on Pods across a cluster. Other alternatives for enforcing security policy are being