diff --git a/content/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/_index.md b/content/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/_index.md
index 4a19f2249dc..144a0e904b4 100644
--- a/content/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/_index.md
+++ b/content/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/_index.md
@@ -46,7 +46,7 @@ The following table lists each built-in custom cluster role available in Rancher
 > **Notes:** 
 >
 >- Each cluster role listed above, including `Owner` and `Member`, is comprised of multiple rules granting access to various resources. You can view the roles and their rules on the Global > Security > Roles page.   
->- In Rancher v2.1.1 and earlier, default resources denoted with `(Custom)` are a UI bug. These resources are two or more Rancher API resources that Rancher flags as `(Custom)` due to an escape issue. This issue is resolved as of v2.1.2.
+>- In Rancher v2.1.1 and earlier, default resources denoted with `(Custom)` are two Kubernetes API resources that Rancher flags as `(Custom)` due to an escape issue. This issue is resolved as of v2.1.2.
 
 ### Project Roles
 
diff --git a/content/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/_index.md b/content/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/_index.md
index 7cf7294dc8e..05ca64f61fa 100644
--- a/content/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/_index.md
+++ b/content/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/_index.md
@@ -62,7 +62,7 @@ While Rancher comes out-of-the-box with a set of default user roles, you can als
 
 6.	Use the **Grant Resources** options to assign individual [Kubernetes API endpoints](https://kubernetes.io/docs/reference/) to the role.
 
-    >**Note:** In Rancher v2.1.1 and earlier, default resources denoted with `(Custom)` are a UI bug. These resources are two or more Rancher API resources that Rancher flags as `(Custom)` due to an escape issue. This issue is resolved as of v2.1.2.
+    >**Note:** - In Rancher v2.1.1 and earlier, default resources denoted with `(Custom)` are two Kubernetes API resources that Rancher flags as `(Custom)` due to an escape issue. This issue is resolved as of v2.1.2.
 
 	You can also choose the individual cURL methods (`Create`, `Delete`, `Get`, etc.) available for use with each endpoint you assign.
 
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 b7932cee0d6..deedff7772f 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
@@ -54,7 +54,7 @@ The following table lists each custom global permission available and whether it
 > **Note:** 
 >
 >- Each permission listed above is comprised of multiple individual permissions not listed in the Rancher UI. For a full list of these permissions and the rules they are comprised of, access through the API at `/v3/globalRoles`.
->- In Rancher v2.1.1 and earlier, default resources denoted with `(Custom)` are a UI bug. These resources are two or more Rancher API resources that Rancher flags as `(Custom)` due to an escape issue. This issue is resolved as of v2.1.2.
+>- In Rancher v2.1.1 and earlier, default resources denoted with `(Custom)` are two Kubernetes API resources that Rancher flags as `(Custom)` due to an escape issue. This issue is resolved as of v2.1.2.
 
 
 When a user from an [external authentication source]({{< baseurl >}}/rancher/v2.x/en/admin-settings/authentication/) signs into Rancher for the first time, they're automatically assigned a set of global permissions (hereafter, permissions). By default, new users are assigned the [user](#user) permissions. However, in some organizations, these permissions may extend too much access. In this use case, you can change the default permissions to something more restrictive, such as a set of individual permissions.