4 trivial edits to Concepts/Storage

1 update to ephemeral-volumes.md

1 update to projected-volumes.md

2 updates to persistent-volumes.md

Reverted 1 update to projected-volumes.md

Author: ClimberJ

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

@@ -224,7 +224,7 @@ volume.
 ### PersistentVolumeClaim naming
 
 Naming of the automatically created PVCs is deterministic: the name is
-a combination of Pod name and volume name, with a hyphen (`-`) in the
+a combination of the Pod name and volume name, with a hyphen (`-`) in the
 middle. In the example above, the PVC name will be
 `my-app-scratch-volume`.  This deterministic naming makes it easier to
 interact with the PVC because one does not have to search for it once

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

@@ -637,7 +637,7 @@ The access modes are:
  `ReadWriteOncePod`
 : {{< feature-state for_k8s_version="v1.27" state="beta" >}}
   the volume can be mounted as read-write by a single Pod. Use ReadWriteOncePod
-  access mode if you want to ensure that only one pod across whole cluster can
+  access mode if you want to ensure that only one pod across the whole cluster can
   read that PVC or write to it. This is only supported for CSI volumes and
   Kubernetes version 1.22+.
 
@@ -1130,7 +1130,7 @@ Kubernetes supports cross namespace volume data sources.
 To use cross namespace volume data sources, you must enable the `AnyVolumeDataSource`
 and `CrossNamespaceVolumeDataSource`
 [feature gates](/docs/reference/command-line-tools-reference/feature-gates/) for
-the kube-apiserver, kube-controller-manager.
+the kube-apiserver and kube-controller-manager.
 Also, you must enable the `CrossNamespaceVolumeDataSource` feature gate for the csi-provisioner.
 
 Enabling the `CrossNamespaceVolumeDataSource` feature gate allows you to specify