diff --git a/docs/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring.md b/docs/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring.md
index 7fd67e9743ee..ffc4217c3391 100644
--- a/docs/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring.md
+++ b/docs/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring.md
@@ -197,7 +197,7 @@ The relationship between the default roles deployed by Rancher (i.e. cluster-own
| project-owner | admin | monitoring-admin | RoleBinding within Project namespace |
| project-member | edit | monitoring-edit | RoleBinding within Project namespace |
-In addition to these default roles, the following additional Rancher project roles can be applied to members of your cluster to provide additional access to monitoring. These rancher roles will be tied to ClusterRoles deployed by the monitoring chart:
+In addition to these default roles, the following additional Rancher project roles can be applied to members of your cluster to provide additional access to monitoring. These Rancher roles will be tied to ClusterRoles deployed by the monitoring chart:
Non-default Rancher Permissions and Corresponding Kubernetes ClusterRoles
@@ -205,7 +205,7 @@ In addition to these default roles, the following additional Rancher project rol
|--------------------------|-------------------------------|-------|------|
| View Monitoring* | [monitoring-ui-view](#monitoring-ui-view) | 2.4.8+ | 9.4.204+ |
-\* A user bound to the **View Monitoring** Rancher Role and read-only permissions won't have access to Grafana links etc. in the monitoring UI. They can still access external Monitoring UIs if provided links to those UIs. In order to access the Monitoring Pane to get those links, the user must be a project member of at least one Project.
+\* A User bound to the **View Monitoring** Rancher role only has permissions to access external Monitoring UIs if provided links to those UIs. In order to access the Monitoring Pane to get those links, the User must be a Project Member of at least one Project.
### Differences in 2.5.x
diff --git a/versioned_docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring.md b/versioned_docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring.md
index 7993c1040c6d..7cc1ef99d028 100644
--- a/versioned_docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring.md
+++ b/versioned_docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring.md
@@ -197,7 +197,7 @@ The relationship between the default roles deployed by Rancher (i.e. cluster-own
| project-owner | admin | monitoring-admin | RoleBinding within Project namespace |
| project-member | edit | monitoring-edit | RoleBinding within Project namespace |
-In addition to these default Roles, the following additional Rancher project roles can be applied to members of your Cluster to provide additional access to Monitoring. These Rancher Roles will be tied to ClusterRoles deployed by the Monitoring chart:
+In addition to these default roles, the following additional Rancher project roles can be applied to members of your cluster to provide additional access to monitoring. These Rancher roles will be tied to ClusterRoles deployed by the monitoring chart:
Non-default Rancher Permissions and Corresponding Kubernetes ClusterRoles
@@ -205,7 +205,7 @@ In addition to these default Roles, the following additional Rancher project rol
|--------------------------|-------------------------------|-------|------|
| View Monitoring* | [monitoring-ui-view](#monitoring-ui-view) | 2.4.8+ | 9.4.204+ |
-\* A User bound to the **View Monitoring** Rancher Role only has permissions to access external Monitoring UIs if provided links to those UIs. In order to access the Monitoring Pane to get those links, the User must be a Project Member of at least one Project.
+\* A user bound to the **View Monitoring** Rancher role with read-only permissions won't have access to Grafana links in the monitoring UI. They can still access external Monitoring UIs if provided links to those UIs. In order to access the Monitoring Pane to get those links, the user must be a project member of at least one Project.
### Differences in 2.5.x