From a3064b1a368afad930e18cec7afefd6c554eb6ad Mon Sep 17 00:00:00 2001 From: Stanislav Kardashov Date: Fri, 19 Aug 2022 16:37:47 +0300 Subject: [PATCH] [en] typo fix "privilge -> privilege" --- content/en/docs/concepts/security/rbac-good-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/security/rbac-good-practices.md b/content/en/docs/concepts/security/rbac-good-practices.md index fe858bba72..933dbdb9bb 100644 --- a/content/en/docs/concepts/security/rbac-good-practices.md +++ b/content/en/docs/concepts/security/rbac-good-practices.md @@ -12,7 +12,7 @@ weight: 60 Kubernetes {{< glossary_tooltip text="RBAC" term_id="rbac" >}} is a key security control to ensure that cluster users and workloads have only the access to resources required to execute their roles. It is important to ensure that, when designing permissions for cluster -users, the cluster administrator understands the areas where privilge escalation could occur, +users, the cluster administrator understands the areas where privilege escalation could occur, to reduce the risk of excessive access leading to security incidents. The good practices laid out here should be read in conjunction with the general