anchor.diff:  
   == Overview
   
  -This guide will cover the how to attach a GlusterFS persistent volume to the Docker Registry.
  -It is assumed that the docker registry service has already been started and the gluster volume has been created.
  +This topic reviews how to attach a GlusterFS persistent volume to the Docker
  +Registry.
   
  -  
  +It is assumed that the Docker registry service has already been started and the
  +Gluster volume has been created.
  +
  +[[backing-docker-registry-with-glusterfs-storage-prerequisites]]
   === Prerequisites
  -* The link:../install/docker_registry.html#deploy-registry[docker-registry] has been deployed *without*
  +
  +* The link:../install/docker_registry.html#deploy-registry[docker-registry] was deployed *without*
   configuring storage.
  -* A gluster volume exists and *glusterfs-fuse* is installed on schedulable nodes.
  +* A Gluster volume exists and *glusterfs-fuse* is installed on schedulable nodes.
   * Definitions written for GlusterFS link:../persistent_storage/persistent_storage_glusterfs.html#creating-gluster-endpoints[endpoints and service],
  -link:../persistent_storage/persistent_storage_glusterfs.html#gfs-creating-persistent-volume[persistent volume (*pv*)],
  +link:../persistent_storage/persistent_storage_glusterfs.html#gfs-creating-persistent-volume[persistent volume (PV)],
   and
  -link:../../architecture/additional_concepts/storage.html#persistent-volume-claims[persistent volume claim (*pvc*)].
  +link:../../architecture/additional_concepts/storage.html#persistent-volume-claims[persistent volume claim (PVC)].
   ** For this guide, these will be:
  -*** `gluster-endpoints-service.yaml`
  -*** `gluster-endpoints.yaml`
  -*** `gluster-pv.yaml`
  -*** `gluster-pvc.yaml`
  +*** *_gluster-endpoints-service.yaml_*
  +*** *_gluster-endpoints.yaml_*
  +*** *_gluster-pv.yaml_*
  +*** *_gluster-pvc.yaml_*
   * A user with the
   link:../../admin_guide/manage_authorization_policy.html#managing-role-bindings[*cluster-admin*] role binding.
  -** For this guide, that user is `admin`
  +** For this guide, that user is *admin*.
   
  -NOTE:  All `$ oc` commands are executed on the master node as the `admin` user
  -
  +[NOTE]
  +====
  +All `oc` commands are executed on the master node as the *admin* user.
  +====
   
   [[create-gfs-pvc]]
   === Create the Gluster Persistent Volume
  
positive.code: ----
  ====
  
  When pods are created, they receive a copy of */etc/resolve.conf*, which typically contains
  only the master DNS server so they can resolve external DNS requests.  To enable internal
  DNS resolution, insert the dnsmasq server to the beginning.  This way, dnsmasq will attempt to resolve
  requests internally first.
  
  In */etc/resolve.conf* all scheduled nodes,
  ====
  ----
  nameserver 192.168.1.100  <1>
  nameserver 192.168.1.1    <2>
  ----
  <1> Add the internal DNS server
  <2> Pre-existing External DNS server
  ====
  
  Once the configurations have been changed, restart the OpenShift Master and dnsmasq services.
  
  ifdef::openshift-enterprise[]
  ----
  
negative.code: gluster-claim   <none>    Bound     gluster-pv   1Gi        RWX           24s
  ----
  
  [NOTE]
  ====
  If either the PVC or PV failed to create or the PVC failed to bind, refer back
  to the link:../persistent_storage/persistent_storage_glusterfs.html[GlusterFS
  Persistent Storage] guide. *Do not* proceed until they initialize and the PVC
  status is *Bound*.
  ====
  
  [[attach-pvc-to-reg]]
  === Attach the PVC to the Docker Registry
  
  Before moving forward, ensure that the *docker-registry* service is running.
  
  ----
  $ oc get svc
  