Merge pull request #9645 from tmorriso-rh/PR8990followup

Add edits to PR 8990

Author: Traci Morrison

dev_guide/expanding_persistent_volumes.adoc

@@ -20,7 +20,7 @@ cases.
 
 [NOTE]
 ====
-For more information on Red Hat Technology Preview features support scope,  see
+For more information on Red Hat Technology Preview features support scope, see
 https://access.redhat.com/support/offerings/techpreview/. 
 ====
 
@@ -66,10 +66,9 @@ kubernetesMasterConfig:
 [[expanding_glusterfs_pvc]]
 == Expanding GlusterFS-Based Persistent Volume Claims
 
-Expanding GlusterFS volumes is easiest. Once the  {product-title} administrator
-has created a StorageClass with `allowVolumeExpansion` set to `true`, you can
-create a PVC from that class, and afterwards, whenever needed, you can edit the
-PVC and request a new size. 
+Once the {product-title} administrator has created a StorageClass with
+`allowVolumeExpansion` set to `true`, you can create a PVC from that class, and
+afterwards, whenever needed, you can edit the PVC and request a new size. 
 
 For example:
 
@@ -120,18 +119,15 @@ available and `FileSystemResizePending` condition is removed from the PVC.
 [[recover_from_resize_failure]]
 == Recovering from Failure when Expanding Volumes
 
-If expanding underlying storage fails either on master or node,
-{product-title} admin can manually recover the PVC state and cancel the resize requests that are
-continuously retried by the controller without administrator intervention.
+If expanding underlying storage fails either on master or node, the
+{product-title} administrator can manually recover the PVC state and cancel the resize
+requests that are continuously retried by the controller without administrator
+intervention.
 
 Currently, this can be done manually by completing the following steps:
 
-1. Mark the PV that is bound to the claim (PVC) with the `Retain` reclaim policy.
-   This can be done by editing the PV and changing persistentVolumeReclaimPolicy to `Retain`.
-2. Delete the PVC, so as we can re-create it later.
-3. To ensure that newly created PVC can bind to PV marked `Retain`, we will have to manually edit the PV
-   and delete `claimRef` entry from PV specs. This will mark the PV as `Available`. For more information
-   about prebinding PVCs please see xref:./persistent_volumes.adoc#persistent-volumes-volumes-and-claim-prebinding[Volume and claim prebinding].
-4. Re-create the PVC in a smaller size or a size that can be allocated by the underlying storage provider.
-   Also set `volumeName` field of PVC to name of PV, so as PVC can only bind to already provisioned PV.
-5. Restore the reclaim policy on the PV.
+. Mark the PV that is bound to the claim (PVC) with the `Retain` reclaim policy. This can be done by editing the PV and changing `persistentVolumeReclaimPolicy` to `Retain`.
+. Delete the PVC (it will be recreated later).
+. To ensure that the newly created PVC can bind to the PV marked `Retain`, manually edit the PV and delete the `claimRef` entry from the PV specs. This marks the PV as `Available`. For more information about prebinding PVCs, see xref:./persistent_volumes.adoc#persistent-volumes-volumes-and-claim-prebinding[volume and claim prebinding].
+. Re-create the PVC in a smaller size or a size that can be allocated by the underlying storage provider. Also, set the `volumeName` field of the PVC to the name of the PV. This binds the PVC to the provisioned PV only.
+. Restore the reclaim policy on the PV.