BlockVolume is no longer in alpha (#18167)

* BlockVolume is no longer alpha

Signed-off-by: dulltz <isrgnoe@gmail.com>

* Apply comment

https://github.com/kubernetes/website/pull/18167#discussion_r358304226

Co-Authored-By: Tim Bannister <tim@scalefactory.com>

* Apply comment

https://github.com/kubernetes/website/pull/18167#discussion_r358519588

* Apply comment

https://github.com/kubernetes/website/pull/18167#pullrequestreview-335535663
Signed-off-by: dulltz <isrgnoe@gmail.com>

Co-authored-by: Tim Bannister <tim@scalefactory.com>

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

@@ -657,7 +657,6 @@ metadata:
 spec:
   capacity:
     storage: 100Gi
-  # volumeMode field requires BlockVolume Alpha feature gate to be enabled.
   volumeMode: Filesystem
   accessModes:
   - ReadWriteOnce
@@ -679,9 +678,8 @@ PersistentVolume `nodeAffinity` is required when using local volumes. It enables
 the Kubernetes scheduler to correctly schedule Pods using local volumes to the
 correct node.
 
-PersistentVolume `volumeMode` can now be set to "Block" (instead of the default
-value "Filesystem") to expose the local volume as a raw block device. The
-`volumeMode` field requires `BlockVolume` Alpha feature gate to be enabled.
+PersistentVolume `volumeMode` can be set to "Block" (instead of the default
+value "Filesystem") to expose the local volume as a raw block device.
 
 When using local volumes, it is recommended to create a StorageClass with
 `volumeBindingMode` set to `WaitForFirstConsumer`. See the