Add some tidy up changes for retriggering the CI

Author: tengqm

content/en/docs/concepts/storage/storage-classes.md

@@ -98,7 +98,7 @@ vendors provide their own external provisioner.
 ### Reclaim Policy
 
 PersistentVolumes that are dynamically created by a StorageClass will have the
-[reclaim policy](/docs/concepts/storage/persistent-volumes/#Reclaiming)
+[reclaim policy](/docs/concepts/storage/persistent-volumes/#reclaiming)
 specified in the `reclaimPolicy` field of the class, which can be
 either `Delete` or `Retain`. If no `reclaimPolicy` is specified when a
 StorageClass object is created, it will default to `Delete`.
@@ -108,8 +108,6 @@ whatever reclaim policy they were assigned at creation.
 
 ### Allow Volume Expansion
 
-{{< feature-state for_k8s_version="v1.11" state="beta" >}}
-
 PersistentVolumes can be configured to be expandable. This feature when set to `true`,
 allows the users to resize the volume by editing the corresponding PVC object.
 
@@ -147,8 +145,9 @@ the class or PV. If a mount option is invalid, the PV mount fails.
 
 ### Volume Binding Mode
 
-The `volumeBindingMode` field controls when [volume binding and dynamic
-provisioning](/docs/concepts/storage/persistent-volumes/#provisioning) should occur. When unset, "Immediate" mode is used by default.
+The `volumeBindingMode` field controls when
+[volume binding and dynamic provisioning](/docs/concepts/storage/persistent-volumes/#provisioning)
+should occur. When unset, "Immediate" mode is used by default.
 
 The `Immediate` mode indicates that volume binding and dynamic
 provisioning occurs once the PersistentVolumeClaim is created. For storage
@@ -177,14 +176,14 @@ The following plugins support `WaitForFirstConsumer` with pre-created Persistent
 - All of the above
 - [Local](#local)
 
-{{< feature-state state="stable" for_k8s_version="v1.17" >}}
 [CSI volumes](/docs/concepts/storage/volumes/#csi) are also supported with dynamic provisioning
 and pre-created PVs, but you'll need to look at the documentation for a specific CSI driver
 to see its supported topology keys and examples.
 
 {{< note >}}
 If you choose to use `WaitForFirstConsumer`, do not use `nodeName` in the Pod spec
-to specify node affinity. If `nodeName` is used in this case, the scheduler will be bypassed and PVC will remain in `pending` state.
+to specify node affinity.
+If `nodeName` is used in this case, the scheduler will be bypassed and PVC will remain in `pending` state.
 
 Instead, you can use node selector for hostname in this case as shown below.
 {{< /note >}}
@@ -354,7 +353,8 @@ parameters:
 - `path`: Path that is exported by the NFS server.
 - `readOnly`: A flag indicating whether the storage will be mounted as read only (default false).
 
-Kubernetes doesn't include an internal NFS provisioner. You need to use an external provisioner to create a StorageClass for NFS.
+Kubernetes doesn't include an internal NFS provisioner.
+You need to use an external provisioner to create a StorageClass for NFS.
 Here are some examples:
 
 - [NFS Ganesha server and external provisioner](https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner)
@@ -377,7 +377,8 @@ parameters:
 
 {{< note >}}
 {{< feature-state state="deprecated" for_k8s_version="v1.11" >}}
-This internal provisioner of OpenStack is deprecated. Please use [the external cloud provider for OpenStack](https://github.com/kubernetes/cloud-provider-openstack).
+This internal provisioner of OpenStack is deprecated. Please use
+[the external cloud provider for OpenStack](https://github.com/kubernetes/cloud-provider-openstack).
 {{< /note >}}
 
 ### vSphere
@@ -387,11 +388,15 @@ There are two types of provisioners for vSphere storage classes:
 - [CSI provisioner](#vsphere-provisioner-csi): `csi.vsphere.vmware.com`
 - [vCP provisioner](#vcp-provisioner): `kubernetes.io/vsphere-volume`
 
-In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi). For more information on the CSI provisioner, see [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#vsphere-csi-migration).
+In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi).
+For more information on the CSI provisioner, see
+[Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and
+[vSphereVolume CSI migration](/docs/concepts/storage/volumes/#vsphere-csi-migration).
 
 #### CSI Provisioner {#vsphere-provisioner-csi}
 
-The vSphere CSI StorageClass provisioner works with Tanzu Kubernetes clusters. For an example, refer to the [vSphere CSI repository](https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/example/vanilla-k8s-RWM-filesystem-volumes/example-sc.yaml).
+The vSphere CSI StorageClass provisioner works with Tanzu Kubernetes clusters.
+For an example, refer to the [vSphere CSI repository](https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/example/vanilla-k8s-RWM-filesystem-volumes/example-sc.yaml).
 
 #### vCP Provisioner
 
@@ -643,8 +648,6 @@ parameters:
 
 ### Local
 
-{{< feature-state for_k8s_version="v1.14" state="stable" >}}
-
 ```yaml
 apiVersion: storage.k8s.io/v1
 kind: StorageClass