anchor.diff:  
   A claim with a *selector* stanza (see example below) attempts to match existing,
   unclaimed, and non-prebound PVs. The existence of a PVC selector ignores a PV's
  -capacity; however, *accessModes* are still considered in the matching criteria.
  +capacity. However, *accessModes* are still considered in the matching criteria.
   
   It is important to note that a claim must match *all* of the key-value pairs
  -included in its *selector* stanza. If no PV matches the claim then the PVC
  -will remain unbound (Pending). A PV can subsequently be created and the 
  +included in its *selector* stanza. If no PV matches the claim, then the PVC
  +will remain unbound (Pending). A PV can subsequently be created and the
   claim will automatically check for a label match.
   
   .glusterfs-pvc.yaml
  
positive.code: 
  [NOTE]
  ====
  PVCs are local to a project; whereas PVs are a cluster-wide, global resource. Developers
  and non-admin users may not have access to see all (or any) of the available PVs.
  ====
  
negative.code:   persistentVolumeReclaimPolicy: Retain
  ----
  <1> Use labels to identify common attributes or characteristics shared among
   volumes. In this case, we defined the Gluster volume to have a custom attribute
   (key) named *storage-tier* with a value of *gold* assigned. A claim will be
   able to select a PV with `*storage-tier=gold*` to match this PV.
  <2> Endpoints define the Gluster trusted pool and are discussed below.
  ====
  
  [[binding-pv-by-label-pvc-with-selectors]]
  