Update stream-analytics-troubleshoot-output.md

Author: mamccrea

articles/stream-analytics/stream-analytics-troubleshoot-output.md

@@ -12,26 +12,25 @@ ms.custom: seodec18
 
 # Troubleshoot Azure Stream Analytics outputs
 
-This page describes common issues with output connections and how to troubleshoot and address them. Enable diagnostic logs as a best practice.
+This article describes common issues with Azure Stream Analytics output connections, how to troubleshoot output issues, and how to correct the issues. Many troublshooting steps require diagnostic logs to be enabled for your Stream Analytics job. If you do not have diagnosic logs enabled, see [Troubleshoot Azure Stream Analytics by using diagnostics logs](stream-analytics-job-diagnostic-logs.md).
 
 ## Output not produced by job
 1.  Verify connectivity to outputs by using the **Test Connection** button for each output.
 
 2.  Look at [**Monitoring Metrics**](stream-analytics-monitoring.md) on the **Monitor** tab. Because the values are aggregated, the metrics are delayed by a few minutes.
 
-   * If Input Events > 0, the job is able to read input data. If Input Events is not > 0, then there is an issue with the job input. Review the [input troubleshooting](stream-analytics-troubleshoot-input.md) page for more information.
+   * If Input Events are greater than 0, the job is able to read input data. If Input Events are not greater than 0, then there is an issue with the job's input. See [Troubleshoot input connections](stream-analytics-troubleshoot-input.md) to learn how to troubleshoot input connection issues.
 
-   * If Data Conversion Errors > 0 and climbing, review the [data errors]() page for more information.
+   * If Data Conversion Errors are greater than 0 and climbing, see [Azure Stream Analytics data errors](data-errors.md) for detailed information about data conversion errors.
 
-    - If Runtime Errors > 0, it means that the job can receive the data but is generating errors while processing the query.
-      - To find the errors, go to the [Audit Logs](../azure-resource-manager/management/view-activity-logs.md) and filter on *Failed* status.
-
-    - If InputEvents > 0 and OutputEvents = 0, it means that one of the following is true:
-      - Query processing resulted in zero output events.
-      - Events or its fields might be malformed, resulting in zero output after query processing.
-      - The job was unable to push data to the output sink for connectivity or authentication reasons.
+   * If Runtime Errors are greater than 0, your job can receive data but it's generating errors while processing the query. To find the errors, go to the [Audit Logs](../azure-resource-manager/management/view-activity-logs.md) and filter on *Failed* status.
+   
+   * If InputEvents is greather than 0 and OutputEvents equals 0, one of the following is true:
+      * Query processing resulted in zero output events.
+      * Events or fields might be malformed, resulting in zero output after query processing.
+      * The job was unable to push data to the output sink for connectivity or authentication reasons.
 
-    - In all the previously mentioned error cases, operations log messages explain additional details (including what is happening), except in cases where the query logic filtered out all events. If the processing of multiple events generates errors, the errors are aggregated every 10 minutes.
+   In all the previously mentioned error cases, operations log messages explain additional details (including what is happening), except in cases where the query logic filtered out all events. If the processing of multiple events generates errors, the errors are aggregated every 10 minutes.
 
 ## Job output is delayed
 
@@ -85,7 +84,6 @@ Note the following observations when configuring IGNORE_DUP_KEY for several type
 ## Column names are lower-cased by Azure Stream Analytics
 When using the original compatibility level (1.0), Azure Stream Analytics used to change column names to lower case. This behavior was fixed in later compatibility levels. In order to preserve the case, we advise customers to move to the compatibility level 1.1 and later. You can find more information on [Compatibility level for Azure Stream Analytics jobs](https://docs.microsoft.com/azure/stream-analytics/stream-analytics-compatibility-level).
 
-
 ## Get help
 
 For further assistance, try our [Azure Stream Analytics forum](https://social.msdn.microsoft.com/Forums/azure/home?forum=AzureStreamAnalytics).