From e00cfd4ea1431ffe479e46a1b3af7d4f4ea86cda Mon Sep 17 00:00:00 2001
From: Brenda Rearden <brenda@rancher.com>
Date: Mon, 5 Oct 2020 17:00:28 -0700
Subject: [PATCH] Update rbac roles

---
 content/rancher/v2.x/en/istio/rbac/_index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/rancher/v2.x/en/istio/rbac/_index.md b/content/rancher/v2.x/en/istio/rbac/_index.md
index cdd75c9867a..91c56254a8c 100644
--- a/content/rancher/v2.x/en/istio/rbac/_index.md
+++ b/content/rancher/v2.x/en/istio/rbac/_index.md
@@ -32,8 +32,8 @@ Istio creates three `ClusterRoles` and adds Istio CRD access to the following de
 
 ClusterRole create by chart | Default K8s ClusterRole  | Rancher Role |
  ------------------------------:| ---------------------------:|---------:|
- `istio-admin` | admin| Project Owner, Project Member | 
- `istio-edit`| edit | Project Owner, Project Member | 
+ `istio-admin` | admin| Project Owner | 
+ `istio-edit`| edit | Project Member | 
  `istio-view` | view | Read-only | 
 
 Rancher will continue to use cluster-owner, cluster-member, project-owner, project-member, etc as role names, but will utilize default roles to determine access. For each default K8s `ClusterRole` there are different Istio CRD permissions and K8s actions (Create ( C ), Get ( G ), List ( L ), Update ( U ), Patch ( P ), Delete( D ), All ( * )) that can be performed.