anchor.diff:  
   ====
   ----
  -# oc get endpoints gluster-endpoints 
  +# oc get endpoints gluster-endpoints
   NAME                ENDPOINTS                           AGE
   gluster-endpoints   192.168.122.21:1,192.168.122.22:1   1m
   ----
   ====
   
  +[[complete-example-using-gusterfs-creating-the-persistent-volume]]
   == Creating the Persistent Volume
  -The persistent volume (PV) file is defined next before creating the PV object in
  -OpenShift:
  +Next, before creating the PV object, define the persistent volume in
  +{product-title}:
   
   .Persistent Volume Object Definition Using GlusterFS
   ====
  
positive.code: ----
  ====
  
  == Creating the Persistent Volume Claim
  A persistent volume claim (PVC) specifies the desired access mode and storage capacity.
  Currently, based on only these two attributes, a PVC is bound to a single PV. Once a PV is
  bound to a PVC that PV is essentially tied to the PVC's project and cannot be bound to by
  another PVC. There is a one-to-one mapping of PVs and PVCs. However, multiple pods in the same
  project can use the same PVC.
  
  .PVC Object Definition
  ====
  
negative.code: <1> The SCC used by the pod.
  <2> The project (namespace) name.
  <3> The UID of the busybox container.
  <4> The ⁠SELinux label for the container, and the default ⁠SELinux label for the
  entire pod, which happen to be the same here.
  <5> The supplemental group ID for the pod (all containers).
  <6> The PVC name used by the pod.
  ====
  