Collector log rewording

Author: aurbiztondo-splunk

gdi/opentelemetry/troubleshoot-logs.rst

@@ -1,29 +1,28 @@
 .. _tshoot-logs:
 
 ****************************************************************
-Troubleshoot Collector logs
+Troubleshoot log collection
 ****************************************************************
 
 .. meta::
       :description: Describes known issues when collecting logs with the Splunk Distribution of OpenTelemetry Collector.
 
+This document describes common issues related to log collection with the Collector.
 
-.. note:: See also the :new-page:`OpenTelemetry Project troublehooting docs <https://opentelemetry.io/docs/collector/troubleshooting>` for more information about debugging.
+To troubleshoot the health and performance of the Collector see the :new-page:`OpenTelemetry Project troublehooting docs <https://opentelemetry.io/docs/collector/troubleshooting>`. It includes information about troubleshooting tools and debugging.
 
-Here are some common issues related to log collection on the Collector.
-
-Source isn't generating logs
+My source isn't generating logs
 =========================================
 
-If using Linux, run the following commands to check if the source is generating Collector logs:
+If using Linux, run the following commands to check if the source is generating logs:
 
 .. code-block:: bash
 
   tail -f /var/log/myTestLog.log
   journalctl -u my-service.service -f
 
 
-If using Windows, run the following command to check if the source is generating Collector logs:
+If using Windows, run the following command to check if the source is generating logs:
 
 .. code-block:: shell
 
@@ -44,11 +43,11 @@ Do the following to check the Fluentd configuration:
 
 While every attempt is made to properly configure permissions, it is possible that td-agent does not have the permission required to collect logs. Debug logging should indicate this issue.
 
-It is possible that the ``<parser>`` section configuration does not match the log events.
+It's possible that the ``<parser>`` section configuration does not match the log events.
 
 If you see a message such as "2021-03-17 02:14:44 +0000 [debug]: #0 connect new socket", Fluentd is working as expected. You need to activate debug logging to see this message.
 
-Collector isn't configured properly
+The Collector isn't configured properly
 =========================================
 
 .. note:: Fluentd is part of the Splunk Distribution of OpenTelemetry Collector, but deactivated by default for Linux and Windows. To activate it, use the ``--with-fluentd`` option when installing the Collector for Linux, or the ``with_fluentd = 1`` option when installing the Collector for Windows.
@@ -90,8 +89,7 @@ Depending on its configuration, the Splunk Distribution of the OpenTelemetry Col
 
 To turn off logs colletion, see :ref:`exclude-log-data` for more information.
 
-
-Send logs from the Collector to Splunk Cloud Platform or Enterprise
+Send logs to Splunk Cloud Platform or Enterprise using the Collector
 ==================================================================================
 
 To send logs from the Collector to Splunk Cloud Platform or Splunk Enterprise, see :ref:`send_logs_to_splunk`.