diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index 49f2dcfb39..a0ec08063a 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -722,12 +722,11 @@ and need persistent storage, it is recommended that you use the following patter
     `persistentVolumeClaim.storageClassName` field.
     This will cause the PVC to match the right storage
     class if the cluster has StorageClasses enabled by the admin.
-  - If the user does not provide a storage class name, leave the
-    `persistentVolumeClaim.storageClassName` field as nil.
-    - This will cause a PV to be automatically provisioned for the user with
-      the default StorageClass in the cluster. Many cluster environments have
-      a default StorageClass installed, or administrators can create their own
-      default StorageClass.
+  - If the user does not provide a storage class name, leave the 
+    `persistentVolumeClaim.storageClassName` field as nil. This will cause a 
+    PV to be automatically provisioned for the user with the default StorageClass 
+    in the cluster. Many cluster environments have a default StorageClass installed,
+    or administrators can create their own default StorageClass.
 - In your tooling, watch for PVCs that are not getting bound after some time
   and surface this to the user, as this may indicate that the cluster has no
   dynamic storage support (in which case the user should create a matching PV)