Merge pull request openshift#12887 from openshift/revert-12882-NEWBZ1…

…647168

Revert "~ Added examples of node labels and xref link, per BZ1647168"

install_config/aggregate_logging.adoc

@@ -836,11 +836,11 @@ $ for dc in $(oc get deploymentconfig --selector logging-infra=elasticsearch -o
 ----
 
 . The Elasticsearch replicas must be located on the correct nodes to use the local
-storage, and should not move, even if those nodes are taken down for a
+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 a node where an administrator has allocated storage for it. To
-configure a node selector, edit each Elasticsearch deployment configuration, adding or
-editing the *nodeSelector* section to specify a unique label that you have
+configure a node selector, edit each Elasticsearch deployment configuration and
+add or edit the *nodeSelector* section to specify a unique label that you have
 applied for each desired node:
 +
 ====
@@ -857,17 +857,6 @@ spec:
 label, in this case `logging-es-node=1`. Use the `oc label` command to apply
 labels to nodes as needed.
 
-For example, if your deployment has three infrastructures, you could add labels for those
-infrastructures as follows:
-----
-oc label node <nodename1> logging-es-node=1
-oc label node <nodename2> logging-es-node=2
-oc label node <nodename3> logging-es-node=3
-----
-
-For information about adding a label to an infrastructure, see
-xref:../admin_guide/manage_nodes.html#updating-labels-on-nodes[Updating Labels on Nodes].
-+
 To automate applying the node selector you can instead use the `oc patch` command:
 
 ----