diff --git a/content/rancher/v2.x/en/concepts/global-configuration/users-permissions-roles/_index.md b/content/rancher/v2.x/en/concepts/global-configuration/users-permissions-roles/_index.md
index 22847e402a1..c8dafa4605d 100644
--- a/content/rancher/v2.x/en/concepts/global-configuration/users-permissions-roles/_index.md
+++ b/content/rancher/v2.x/en/concepts/global-configuration/users-permissions-roles/_index.md
@@ -2,6 +2,28 @@
 title: Users, Global Permissions, and Roles
 weight: 15
 ---
+In This Document:
+
+<!-- TOC -->
+
+- [Users and Roles](#users-and-roles)
+    - [Global Permissions](#global-permissions)
+        - [Global Permission Assignment](#global-permission-assignment)
+        - [Custom Global Permissions](#custom-global-permissions)
+        - [Global Permissions Reference](#global-permissions-reference)
+    - [Cluster and Project Roles](#cluster-and-project-roles)
+        - [Membership and Role Assignment](#membership-and-role-assignment)
+        - [Cluster Roles](#cluster-roles)
+            - [Custom Cluster Roles](#custom-cluster-roles)
+            - [Cluster Role Reference](#cluster-role-reference)
+        - [Project Roles](#project-roles)
+            - [Custom Project Roles](#custom-project-roles)
+            - [Project Role Reference](#project-role-reference)
+    - [Defining Custom Roles](#defining-custom-roles)
+        - [Locked Roles](#locked-roles)
+
+<!-- /TOC -->
+
 
 Within Rancher, each user authenticates as a _user_, which is a login that grants you access to Rancher. As mentioned in [Authentication]({{< baseurl >}}/rancher/v2.x/en/concepts/global-configuration/authentication), users can either be local or external.
 
diff --git a/content/rancher/v2.x/en/tasks/clusters/adding-storage/_index.md b/content/rancher/v2.x/en/tasks/clusters/adding-storage/_index.md
index c539e017cb4..a119c68f354 100644
--- a/content/rancher/v2.x/en/tasks/clusters/adding-storage/_index.md
+++ b/content/rancher/v2.x/en/tasks/clusters/adding-storage/_index.md
@@ -44,7 +44,6 @@ Persistent volumes can either be a disk or file system that you host on premise,
     - [Access Modes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes):
 
          This options sets how many nodes can access the volume, along with the node read/write permissions. The [Kubernetes Documentation](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) includes a table that lists which access modes are supported by the plugins available.
-
     - [Mount Options](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#mount-options):
 
          Each volume plugin allows you to specify additional command line options during the mounting process. You can enter these options in the **Mount Option** fields. Consult each plugin's vendor documentation for the mount options available.
@@ -52,7 +51,6 @@ Persistent volumes can either be a disk or file system that you host on premise,
     - **Assign to Storage Class:**
 
          If you later want to automatically provision persistent volumes identical to the volume that you've specified here, assign it a storage class. Later, when you create a workload, you can assign it a persistent volume claim that references the storage class, which will provision a persistent volume identical to the volume you've specified here.
-
          >**Note:** You must [add a storage class](#adding-storage-classes) before you can assign it to a persistent volume.
 
 1. Click **Save**.