Language tweaks

Signed-off-by: keithhc2 <keithhc2@users.noreply.github.com>

_observability-plugin/app-analytics.md

@@ -6,17 +6,18 @@ nav_order: 80
 
 # Application analytics
 
-Application analytics can now create custom Observability Applications to view the availability status of all their systems, where log events can be combined with trace and metric data, into a single view of system health empowering developers and IT Ops to resolve issues faster and with fewer escalations.Application analytics in Observability is where you can select logs, traces, and metrics to be part of an Observability Application that can be monitored for overall health and visualized on one page. This allows you to quickly pivot between logs, traces, and metrics to dig into the source of any issues. Many teams use similar logs and similar traces and need a structured view.
+You can use application analytics to create custom observability applications to view the availability status of your systems, where you can combine log events with trace and metric data into a single view of overall system health. This lets you quickly pivot between logs, traces, and metrics to dig into the source of any issues.
 
 ## Get started with application analytics
 
-To get started, choose **Observability** in OpenSearch Dashboards, and then choose **Application analytics**. 
+To get started, choose **Observability** in OpenSearch Dashboards, and then choose **Application analytics**.
 
 ### Create an application
 
-1. Choose **Create application**
+1. Choose **Create application**.
-1. Enter a name for your application and optionally add a description
+2. Enter a name for your application and optionally add a description.
-1. Do at least one of the following
+3. Do at least one of the following:
+
 - Use [PPL]({{site.url}}{{site.baseurl}}/observability-plugin/ppl/index) to specify the base query.
 
 You can't change the base query after the application is created.
@@ -24,40 +25,41 @@ You can't change the base query after the application is created.
 
 - Select services & entities from the dropdown or the service map.
 - Select trace groups from the dropdown or the table.
-1. Choose **Create**.
+
+4\. Choose **Create**.
 
 ### Create a visualization
 
-1. Choose the **Log Events** tab
+1. Choose the **Log Events** tab.
-1. Use [PPL]({{site.url}}{{site.baseurl}}/observability-plugin/ppl/index) to build upon your base query
+1. Use [PPL]({{site.url}}{{site.baseurl}}/observability-plugin/ppl/index) to build upon your base query.
-1. Move to the **Visualizations** tab to see your visualizations
+1. Choose the **Visualizations** tab to see your visualizations.
 1. Expand the **Save** dropdown menu, enter a name for your visualization, then choose **Save**.
 
-To see your visualizations, move to the **Panel** tab. 
+To see your visualizations, choose the **Panel** tab.
 
 ### Configure availability
 
-Availability is the status of your application determined by availability levels set on a [time series metric]({{site.url}}{{site.baseurl}}/observability-plugin/app-analytics/#time-series-metric). 
+Availability is the status of your application determined by availability levels set on a [time series metric]({{site.url}}{{site.baseurl}}/observability-plugin/app-analytics/#time-series-metric).
 
-To create an availability level you must configure the following
+To create an availability level, you must configure the following:
 - color: The color of the availability badge on the home page.
 - name: The text in the availability badge on the home page.
-- expression: Comparison operator to determine the availability. 
+- expression: Comparison operator to determine the availability.
 - value: Value to use when calculating availability.
 
 ![Configuring availability]({{site.url}}{{site.baseurl}}/images/app_availability_level.gif)
 
-By default, Application analytics shows results from the last 24 hours of your data. To see data from a different timeframe, use the date and time selector.
+By default, application analytics shows results from the last 24 hours of your data. To see data from a different timeframe, use the date and time selector.
 
 #### Time series metric
 
-A time series metric is any visualization that has a query that spans over a timestamp and is a line chart. Users can use the power of the PPL language to define arbitrary conditions on their logs to create a visualization over time.
+A time series metric is any visualization that has a query that spans over a timestamp and is a line chart. You can then use PPL to define arbitrary conditions on their logs to create a visualization over time.
 
 ##### Example
 ```
 source = <index_name> | ... | ... | stats ... by span(<timestamp_field>, 1h)
 ```
 
-Users can then choose **Line** in visualization configurations to create a time series metric.
+Choose **Line** in visualization configurations to create a time series metric.
 
-![Changing visualization to line chart]({{site.url}}{{site.baseurl}}/images/visualization-line-type.gif)
+![Changing visualization to line chart]({{site.url}}{{site.baseurl}}/images/visualization-line-type.gif)

_observability-plugin/event-analytics.md

@@ -34,22 +34,22 @@ To save a visualization, expand the save dropdown menu next to **Refresh**, ente
 
 ## View logs
 
-Users have several ways to view their logs.
+The following are methods you can use to view logs.
 
 ### Trace log correlation
 
-Users who regularly track events across applications have the capability to correlate logs and traces. To view the correlation, users have to index the traces as per the Open Telemetry standards (similar to Trace analytics). Once users add a **TraceId** field to their logs, they can view the trace information that corresponds to the same execution context as the log.
+If you regularly track events across applications, you can correlate logs and traces. To view the correlation, you have to index the traces according to Open Telemetry standards (similar to trace analytics). Once you add a `TraceId` field to your logs, your can view the correlated trace information in the event explorer log details. This method lets you correlate logs and traces that correspond to the same execution context.
 
 ![Trace Log Correlation]({{site.url}}{{site.baseurl}}/images/trace_log_correlation.gif)
 
-### Surrounding events
+### View surrounding events
 
-Users who want to know more about a log event that they are looking at can select **View surrounding events** to get a bigger picture of what was happening around the time of interest. 
+If you want to know more about a log event you're looking at, you can select **View surrounding events** to get a bigger picture of what was happening around the time of interest.
 
 ![Surrounding Events]({{site.url}}{{site.baseurl}}/images/surrounding_events.gif)
 
-### Live Tail
+### Live tail
 
-Users watching a live event take place can now configure the interval in which content is refreshed saving the hassle of manually refreshing. This provides users with a faster debugging experience, and allows them to monitor their logs in real-time. Users also have the convenience of choosing the interval at which live tail should update. As this feature mimics the "tail -f" command in command line, it only retrieves the most recent live logs by possibly eliminating a heavy load of live logs.
+If you prefer watching events happen live, you can configure an interval so event analytics automatically refreshes the content. Live tail lets you stream logs live to OpenSearch observability event analytics based on the provided PPL query, as well as provide rich functionality such as filters. Doing so improves your debugging experience and lets you monitor your logs in real-time without having to manually refresh. You can also choose intervals and switch  between them to dictate how often live tail should stream live logs. This feature is similar to the CLI's `tail -f` command in that it only retrieves the most recent live logs by possibly eliminating a large portion of live logs. Live tail also provides you with the total count of count of live logs received by OpenSearch during the live stream, which you can use to better understand the incoming traffic.
 
-![Live Tail]({{site.url}}{{site.baseurl}}/images/live_tail.gif)
+![Live Tail]({{site.url}}{{site.baseurl}}/images/live_tail.gif)