diff --git a/content/rancher/v2.x/en/concepts/volumes-and-storage/_index.md b/content/rancher/v2.x/en/concepts/volumes-and-storage/_index.md
index 0efca368988..757fd1bdd19 100644
--- a/content/rancher/v2.x/en/concepts/volumes-and-storage/_index.md
+++ b/content/rancher/v2.x/en/concepts/volumes-and-storage/_index.md
@@ -6,7 +6,7 @@ There are two ways to create volumes on Kubernetes: Persistent Volumes (PVs) and
 
 ## Persistent Volumes
 
-_Persistent Volumes_ are pre-provisioned storage volumes that you can bind to specific pods later. For example, in Amazon EC2, you might want to create a number of Elastic Block Store (EBS) volumes before you start running your application. Each pre-provisioned EBS volume corresponds to a Kubernetes persistent volume. When the application starts, it creates Persistent Volume Claims (PVCs) that bind to persistent volumes. A PVC corresponds to a Docker volume. Each PVC binds to one PV that includes the minimimum resources that the PVC requires. The following figure illustrates the relationship between pods, PVCs, PVs, and the underlying cloud storage.
+_Persistent Volumes_ are pre-provisioned storage volumes that you can bind to specific pods later. For example, in Amazon EC2, you might want to create a number of Elastic Block Store (EBS) volumes before you start running your application. Each pre-provisioned EBS volume corresponds to a Kubernetes persistent volume. When the application starts, it creates Persistent Volume Claims (PVCs) that bind to persistent volumes. A PVC corresponds to a Docker volume. Each PVC binds to one PV that includes the minimum resources that the PVC requires. The following figure illustrates the relationship between pods, PVCs, PVs, and the underlying cloud storage.
 
 ![Persistent Volumes]({{< baseurl >}}/img/rancher/persistent-volume.png)
 
@@ -14,8 +14,10 @@ Rancher allows you to create PVs at cluster level and bind them to PVCs later. V
 
 ## Storage Classes
 
-Storage classes allow you to create PVCs dynamically without having to create PVs first. For example, an EBS Storage Class will dynamically create EBS volumes and bind them to PVCs. A storage class is similar to the notion of a “storage driver.” The following figure illustrates how a PVC creation triggers the dynamic provisioning of an underlying EBS volume.
+Storage classes allow you to create PVCs dynamically without having to create PVs first. For example, an Amazon EBS Storage class will dynamically create EBS volumes and bind them to PVCs. A storage class is similar to the notion of a _storage driver_. The following figure illustrates how a PVC creation triggers the dynamic provisioning of an underlying EBS volume.
 
 ![Storage Classes]({{< baseurl >}}/img/rancher/storage-classes.png)
 
-<!-- Storage and Cloud Providers -->
+### Storage and Cloud Providers
+
+Kubernetes (and therefore, Rancher) supports a wide variety of storage volume plugins, both on premise and in the cloud.
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 a18b0cf0183..a24f5ce869e 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
@@ -14,7 +14,7 @@ In This Document:
 
 <!-- /TOC -->
 
->**Prerequisite:** Completion of all tasks on this page require the `Manage Volumes` [role](../../../concepts/global-configuration/users-permissions-roles/#project-role-reference):
+>**Prerequisite:** Completion of all tasks on this page require the `Manage Volumes` [role](../../../concepts/global-configuration/users-permissions-roles/#project-role-reference).
 
 ## Adding a Persistent Volume
 
@@ -41,7 +41,7 @@ Persistent volumes can either be a disk or file system that you host on premise,
 
 1. Enter the **Capacity** of your volume in gigabytes.
 
-1. Complete the **Plugin Configuration** form. Each plugin type requires information specific to the vendor of disk type. For more information about each plugin's form, refer to the reference table below.
+1. Complete the **Plugin Configuration** form. Each plugin type requires information specific to the vendor of disk type. For help regarding each plugin's form and the information that's required, refer to the plug-in's vendor documentation.
 
 1. **Optional:** Complete the **Customize** form. This form features:
 
@@ -65,30 +65,6 @@ Persistent volumes can either be a disk or file system that you host on premise,
 
 For example, this volume is a _hostPath_ volume in Kubernetes:
 
-```
-> kubectl get pv
-
-NAME      CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM     STORAGECLASS   REASON    AGE
-test      10Gi       RWO            Retain           Available                                      23m
-
-> kubectl get pv/test -o yaml
-apiVersion: v1
-kind: PersistentVolume
-metadata:
-  ...
-spec:
-  accessModes:
-  - ReadWriteOnce
-  capacity:
-    storage: 10Gi
-  hostPath:
-    path: /tmp/test
-    type: ""
-  persistentVolumeReclaimPolicy: Retain
-status:
-  phase: Available
-```
-
 ## Adding Storage Classes
 
 _Storage Classes_ allow you to dynamically provision persistent volumes on demand. Think of storage classes as storage profiles that are created automatically upon a request (which is known as a _persistent volume claim_).