Fix nits

Tidying that I spotted whilst reordering the storage concepts section.

content/en/docs/concepts/storage/persistent-volumes.md

@@ -10,14 +10,13 @@ feature:
   title: Storage orchestration
   description: >
     Automatically mount the storage system of your choice, whether from local storage, a public cloud provider such as <a href="https://cloud.google.com/storage/">GCP</a> or <a href="https://aws.amazon.com/products/storage/">AWS</a>, or a network storage system such as NFS, iSCSI, Gluster, Ceph, Cinder, or Flocker.
-
 content_type: concept
 weight: 20
 ---
 
 <!-- overview -->
 
-This document describes the current state of _persistent volumes_ in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested.
+This document describes _persistent volumes_ in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested.
 
 <!-- body -->
 

content/en/docs/concepts/storage/projected-volumes.md

@@ -1,6 +1,5 @@
 ---
 reviewers:
-- sftim
 - marosset
 - jsturtevant
 - zshihang
@@ -11,7 +10,7 @@ weight: 21 # just after persistent volumes
 
 <!-- overview -->
 
-This document describes the current state of _projected volumes_ in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested.
+This document describes _projected volumes_ in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested.
 
 <!-- body -->
 

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

@@ -16,7 +16,6 @@ Storage capacity is limited and may vary depending on the node on
 which a pod runs: network-attached storage might not be accessible by
 all nodes, or storage is local to a node to begin with.
 
-{{< feature-state for_k8s_version="v1.19" state="alpha" >}}
 {{< feature-state for_k8s_version="v1.21" state="beta" >}}
 
 This page describes how Kubernetes keeps track of storage capacity and