diff --git a/docs/product/issues/issue-details/performance-issues/db-main-thread-io.mdx b/docs/product/issues/issue-details/performance-issues/db-main-thread-io.mdx
index 07851dab4ecf4f..896e09f9691899 100644
--- a/docs/product/issues/issue-details/performance-issues/db-main-thread-io.mdx
+++ b/docs/product/issues/issue-details/performance-issues/db-main-thread-io.mdx
@@ -24,8 +24,10 @@ You can configure detector thresholds for Database on Main Thread issues in **Pr
 
 Span evidence identifies the root cause of the Database on Main Thread problem by showing you three main aspects:
 
-- **Transaction name**
-- **Parent Span:** Where the database spans occurred
-- **Offending Span:** The actual spans that are performing database queries in the main thread
+- Transaction name
+- Offending Span - The actual spans that are performing database queries in the main thread
+- Waterfall Trace View - Shows the offending span and its parent span
+
+![Database on Main Thread Span evidence](./img/db-on-main-thread-span-evidence.png)
 
 View it by going to the **Issues** page in Sentry, selecting your project, clicking on the database error you want to examine, then scrolling down to the "Span Evidence" section.
diff --git a/docs/product/issues/issue-details/performance-issues/img/db-on-main-thread-span-evidence.png b/docs/product/issues/issue-details/performance-issues/img/db-on-main-thread-span-evidence.png
new file mode 100644
index 00000000000000..356519de4ce4af
Binary files /dev/null and b/docs/product/issues/issue-details/performance-issues/img/db-on-main-thread-span-evidence.png differ