Initial draft for span events.

src/content/docs/integrations/open-source-telemetry-integrations/opentelemetry/view-your-opentelemetry-data-new-relic.mdx

@@ -13,35 +13,43 @@ After you import OpenTelemetry data into New Relic, you can use a variety of too
 
 ## Explorer: Get the big picture along with the details [#explorer]
 
-The New Relic explorer is a good place to get overview information about your applications, as well as detailed information, such as distributed tracing.
+The New Relic **Explorer** tab is a good place to start gathering information about your services: 
 
-To get started with the explorer:
-
-1. Go to [one.newrelic.com](https://one.newrelic.com) and click **Explorer**.
+1. Go to [one.newrelic.com](https://one.newrelic.com).
 2. In the left sidebar, click **Services - OpenTelemetry**:
 
     ![Screen capture showing how to filter for OpenTelemetry services.](./images/explorer_otel_services.png "Filter for OpenTelemetry to see only those entities.")
 
-3. Click the service you want to know more about.
+3. In the center pane, click the service you want to know more about, or find your service by entering the name in the top filter bar.
 
-If you need help understanding the data, see the explanations which follow.
+If you need help understanding how we display your data, see the left-pane options below.
 
 ### Summary page [#summary]
 
-The opening page of the explorer is the **Summary** page listing various golden signals about your entity. Golden signals are key monitoring details such as response time, throughput, and error rate. By using this information, you can quickly decide if you need to dig deeper.
+After you click on a service in the **Explorer** tab, you see the **Summary** page listing various golden signals about your entity. Golden signals are key monitoring details such as response time, throughput, and error rate. By using this information, you can quickly decide if you need to dig deeper.
 
 ### Distributed tracing [#tracing]
 
-When you access distributed tracing through the explorer, you are looking at traces that include that service. Once you’re in that service, you can filter spans to find the ones you want. For example, to query `service.name` or `trace.id`, you can use the following:
+In this section, you mostly locate traces and examine span details.
+
+#### Locate important traces
+
+In **Distributed tracing**, you can filter traces to find the ones you want. For example, to query `service.name` or `trace.id`, you can enter the  following in the top filter bar:
 
 * `service.name = YOUR_SERVICE_NAME`
 * `trace.id = YOUR_TRACE_ID`
 
-For more ways to filter and analyze your spans, see our [distributed tracing UI page](/docs/understand-dependencies/distributed-tracing/ui-data/understand-use-distributed-tracing-ui).
+For more ways to filter traces, see our [distributed tracing UI page](/docs/understand-dependencies/distributed-tracing/ui-data/understand-use-distributed-tracing-ui).
+
+#### Examine span details
+
+When you find an interesting trace and click on it, the spans appear in a waterfall diagram. You can click on specific spans within the trace, which displays span details in the right panel.
+
+If you are sending in span events, such as logs and errors, you can see their attributes and values by clicking **View span events**.
+
+![Screenshot showing how to find span events.](./images/view-span-events.png)
 
-<Callout variant="tip">
-  If you prefer to search traces across all New Relic accounts in your organization, you can go outside explorer: **[one.newrelic.com](https://one.newrelic.com) > Apps > Favorites > Distributed tracing.**
-</Callout>
+When you are viewing span events, you can also filter them by sliding **Only show exceptions**.
 
 ### Transactions [#trx]