diff --git a/install_config/aggregate_logging.adoc b/install_config/aggregate_logging.adoc
index 83816c6967b5..7d06c9c89e48 100644
--- a/install_config/aggregate_logging.adoc
+++ b/install_config/aggregate_logging.adoc
@@ -419,7 +419,8 @@ Elasticsearch deployment configuration.
 The best-performing volumes are local disks, if it is possible to use
 them. Doing so requires some preparation as follows.
 
-. The relevant service account must be given the privilege to mount and edit a local volume, as follows:
+. The relevant service account must be given the privilege to mount and edit a
+local volume, as follows:
 +
 ====
 ----
@@ -430,7 +431,8 @@ $ oadm policy add-scc-to-user privileged  \
 this service account.
 ====
 
-. Each Elasticsearch replica definition must be patched to claim that privilege, for example:
+. Each Elasticsearch replica definition must be patched to claim that privilege,
+for example:
 +
 ----
 $ for dc in $(oc get deploymentconfig --selector logging-infra=elasticsearch -o name); do
@@ -444,7 +446,7 @@ $ for dc in $(oc get deploymentconfig --selector logging-infra=elasticsearch -o
 the local storage, and should not move around even if those nodes are
 taken down for a period of time. This requires giving each Elasticsearch
 replica a node selector that is unique to the node where an administrator
-has allocated storage for it.  xref:#logging-node-selector[See below
+has allocated storage for it. xref:logging-node-selector[See below
 for directions on setting a node selector].
 
 . Once these steps are taken, a local host mount can be applied to each replica
@@ -472,9 +474,9 @@ $ for dc in $(oc get deploymentconfig --selector logging-infra=elasticsearch -o
 ----
 endif::openshift-enterprise[]
 
-If using host mounts is impractical or
-undesirable, it may be necessary to attach block storage as a
-xref:../architecture/additional_concepts/storage.adoc#persistent-volume-claims[PersistentVolumeClaim])
+If using host mounts is impractical or undesirable, it may be necessary to
+attach block storage as a
+xref:../architecture/additional_concepts/storage.adoc#persistent-volume-claims[PersistentVolumeClaim]
 as in the following example:
 
 ----