diff --git a/rules/S6867/kubernetes/rule.adoc b/rules/S6867/kubernetes/rule.adoc
index 29e01de46fc..f18391bbb5c 100644
--- a/rules/S6867/kubernetes/rule.adoc
+++ b/rules/S6867/kubernetes/rule.adoc
@@ -3,7 +3,7 @@
 Using wildcards when defining Role-Based Access Control (RBAC) permissions in Kubernetes can lead to significant security issues. This is because it grants overly broad permissions, potentially allowing access to sensitive resources.
 
 
-RBAC is designed to limit the access rights of users within the system by assigning roles to them. These roles define what actions a user can perform and on which resources. When a wildcard is used, it means that the role has access to all resources/verbs, bypassing the principle of least privilege. This principle states that a user should have only the minimal permissions they need to perform their job function.
+RBAC is designed to limit the access rights of users within the system by assigning roles to them. These roles define what actions a user can perform and on which resources. When a wildcard is used, it means that the role has access to all resources/verbs, bypassing the principle of least privilege. This principle states that users should have only the minimal permissions they need to perform their job function.
 
 
 === What is the potential impact?