diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md
index d7d60d5ded343..361c8c17f553c 100644
--- a/content/en/docs/concepts/workloads/controllers/statefulset.md
+++ b/content/en/docs/concepts/workloads/controllers/statefulset.md
@@ -45,7 +45,7 @@ that provides a set of stateless replicas.
 
 * The storage for a given Pod must either be provisioned by a
   [PersistentVolume Provisioner](/docs/concepts/storage/dynamic-provisioning/) ([examples here](https://github.com/kubernetes/examples/tree/master/staging/persistent-volume-provisioning/README.md))
-  based on the requested `storage class`, or pre-provisioned by an admin.
+  based on the requested _storage class_, or pre-provisioned by an admin.
 * Deleting and/or scaling a StatefulSet down will *not* delete the volumes associated with the
   StatefulSet. This is done to ensure data safety, which is generally more valuable than an
   automatic purge of all related StatefulSet resources.
@@ -144,9 +144,10 @@ validation error during StatefulSet creation.
 You can set the `.spec.volumeClaimTemplates` field to create a
 [PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/). 
 This will provide stable storage to the StatefulSet if either
-* The specified `storage class` is set up to use [dynamic
+
+* The StorageClass specified for the volume claim is set up to use [dynamic
   provisioning](/docs/concepts/storage/dynamic-provisioning/), or
-* The cluster already contains a PersistentVolume with the correct `storage class`
+* The cluster already contains a PersistentVolume with the correct StorageClass
   and sufficient available storage space.
 
 ### Minimum ready seconds