edit

Author: mburke5678

_topic_map.yml

@@ -141,8 +141,6 @@ Topics:
   File: efk-logging-deploy
 - Name: Uninstalling the EFK stack
   File: efk-logging-uninstall
-- Name: Troubleshooting Kubernetes
-  File: efk-logging-troubleshooting
 - Name: Working with Elasticsearch
   File: efk-logging-elasticsearch
 - Name: Working with Fluentd
@@ -159,5 +157,7 @@ Topics:
   File: efk-logging-manual-rollout
 - Name: Configuring systemd-journald and rsyslog
   File: efk-logging-systemd
+- Name: Troubleshooting Kubernetes
+  File: efk-logging-troubleshooting
 - Name: Exported fields
   File: efk-logging-exported-fields

modules/efk-logging-elasticsearch-persistent-storage-about.adoc

@@ -48,12 +48,12 @@ openshift_logging_es_pvc_size=104802308Ki
 openshift_logging_es_pvc_prefix=es-logging
 ----
 
-If using dynamically provisioned PVs, the {product-title} logging installer creates PVCs 
+If you use dynamically provisioned PVs, the {product-title} logging installer creates PVCs 
 that use the default storage class or the PVC specified with the `openshift_logging_elasticsearch_pvc_storage_class_name` parameter.
 
-If using NFS storage, the {product-title} installer creates the persistent volumes, based on the `openshift_logging_storage_*` parameters 
+If you use NFS storage, the {product-title} installer creates the persistent volumes, based on the `openshift_logging_storage_*` parameters 
 and the {product-title} logging installer creates PVCs, using the `openshift_logging_es_pvc_*` paramters.
-Make sure you specify the correct parameters in order to use persistent volumes with EFK.
+Make sure you specify the correct parameters to use persistent volumes with EFK.
 Also set the `openshift_enable_unsupported_configurations=true` parameter in the Ansible inventory file, 
 as the logging installer blocks the installation of NFS with core infrastructure by default.
 
@@ -63,18 +63,5 @@ Using NFS storage as a volume or a persistent volume (or via NAS such as
 Gluster) is not supported for Elasticsearch storage, as Lucene relies on file
 system behavior that NFS does not supply. Data corruption and other problems can
 occur. 
-
-----
-$ truncate -s 1T /nfs/storage/elasticsearch-1
-$ mkfs.xfs /nfs/storage/elasticsearch-1
-$ mount -o loop /nfs/storage/elasticsearch-1 /usr/local/es-storage
-$ chown 1000:1000 /usr/local/es-storage
-----
-
-Then, use *_/usr/local/es-storage_* as a host-mount as described below.
-Use a different backing file as storage for each Elasticsearch node.
-
-This loopback must be maintained manually outside of {product-title}, on the
-node. You must not maintain it from inside a container.
 ====
 

modules/efk-logging-elasticsearch-persistent-storage-local.adoc

@@ -77,8 +77,7 @@ $ oc patch dc/logging-es-<suffix> \
    -p '{"spec":{"template":{"spec":{"nodeSelector":{"logging-es-node":"1"}}}}}'
 ----
 
-. Once these steps are taken, a local host mount can be applied to each replica
-as in this example, assuming storage is mounted at the same path on each node:
+. Apply a local host mount to each replica. The following example assumes storage is mounted at the same path on each node:
 +
 ----
 $ for dc in $(oc get deploymentconfig --selector logging-infra=elasticsearch -o name); do

modules/efk-logging-elasticsearch-persistent-storage.adoc

@@ -12,7 +12,7 @@ Fluentd writes logs to a specified file or to the default location, `/var/log/fl
 To set the output location for the Fluentd logs: 
 
 . Edit the `LOGGING_FILE_PATH` parameter 
-in the default inventory file. You can specify a particular file or to STDOUT:
+in the default inventory file. You can specify a particular file or `STDOUT`:
 +
 ----
 LOGGING_FILE_PATH=console <1>