anchor.diff:  
   .Prerequisites
   
  -* The controlling StorageClass must have `allowVolumeExpansion` set 
  +* The controlling StorageClass must have `allowVolumeExpansion` set
   to `true`.
   
   .Procedure
   
  -. Edit the PVC and request a new size by editing `spec.resources.requests`. 
  -For example, the following expands the `ebs` PVC to 8 Gi. 
  +. Edit the PVC and request a new size by editing `spec.resources.requests`.
  +For example, the following expands the `ebs` PVC to 8 Gi.
   +
   [source,yaml]
   ----
  
positive.code: the PVC.
  
  . Once the cloud provider object has finished resizing, the PVC is set to
  `FileSystemResizePending`. The following command is used to check 
  the condition:
  +
  ----
  $ oc describe pvc <pvc_name>
  ----
  
  . When the cloud provider object has finished resizing, the 
  persistent volume object reflects the newly requested size in 
  `PersistentVolume.Spec.Capacity`. At this point, you can create or 
  re-create a new pod from the PVC to finish the file system resizing. 
  Once the pod is running, the newly requested size is available and the
  `FileSystemResizePending` condition is removed from the PVC.
  
negative.code: = Expanding Persistent Volume Claims (PVC) with a file system
  
  Expanding PVCs based on volume types that need file system resizing,
  such as GCE PD, EBS, and Cinder, is a two-step process.
  This process involves expanding volume objects in the cloud provider, and
  then expanding the file system on the actual node.
  
  