From 5104e99b7a0489e3d9beb26da2d6d3cd92551711 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 5 Oct 2020 17:59:21 -0700 Subject: [PATCH] Grammar edit --- .../v2.x/en/admin-settings/rbac/global-permissions/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.x/en/admin-settings/rbac/global-permissions/_index.md b/content/rancher/v2.x/en/admin-settings/rbac/global-permissions/_index.md index ba3f701f232..f5cfc8fd32f 100644 --- a/content/rancher/v2.x/en/admin-settings/rbac/global-permissions/_index.md +++ b/content/rancher/v2.x/en/admin-settings/rbac/global-permissions/_index.md @@ -52,8 +52,8 @@ The `restricted-admin` permissions are as follows: - Has full admin access to all downstream clusters managed by Rancher. - Has very limited access to the local Kubernetes cluster. Can access Rancher custom resource definitions, but has no access to any Kubernetes native types. - Can add other users and assign them to clusters outside of the local cluster. -- Can create other restricted admins -- Can not grant any permissions in the local cluster they don't currently have (This is how Kubernetes normally operates) +- Can create other restricted admins. +- Cannot grant any permissions in the local cluster they don't currently have. (This is how Kubernetes normally operates) ### Upgrading from Rancher with a Hidden Local Cluster