diff --git a/docs/product/explore/traces/index.mdx b/docs/product/explore/traces/index.mdx
index ac76a1e0dbb4cb..fa94f926616a3b 100644
--- a/docs/product/explore/traces/index.mdx
+++ b/docs/product/explore/traces/index.mdx
@@ -24,11 +24,11 @@ To get started, go to the [Traces](https://sentry.io/orgredirect/organizations/:
 Each set of search conditions helps you find a specific kind of span within a trace. You can either:
 
 - Use a single set of conditions to search across all spans.
-**Example:** Single condition: Find traces where a user with email `ztv@example.com` loaded a specific frontend route:
+**Single Condition Example:** Find traces where a user with email `ztv@example.com` loaded a specific frontend route:
 ![Exampe of search with one span conditions set](./img/traces-one-span-conditions-example.png)
 
 - Use multiple sets of conditions to search for traces containing all specified span types.
-**Example:** Multiple conditions: Find traces where a user with the email `ztv@example.com` loaded a page on your frontend on a specific route AND a slow database query was present:
+**Multiple Conditions Example:** Find traces where a user with the email `ztv@example.com` loaded a page on your frontend on a specific route AND a slow database query was present:
 ![Example of search with multiple span conditions](./img/traces-multiple-span-conditions-example.png)
 
 Because traces range accross multiple projects, there's no project filter, but you can filter by projects with similar sets of span conditions by adding `project:your-project-here` in the search.
@@ -66,7 +66,7 @@ Search results are displayed as a list of traces. Each row corresponds to a sing
 
 ### Span Details
 
-Expand a trace to see the matching spans in the following table format:
+Expand a trace to see the matching spans and the following information:
 
 - **Span ID**: Links to the span in the Trace View.
 - **Description**: Includes project, `span.op`, and `span.description`.