diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/consecutive-example.png b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/consecutive-example.png
deleted file mode 100644
index 7cd3ed0cd3362b..00000000000000
Binary files a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/consecutive-example.png and /dev/null differ
diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/parallel-example.png b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/parallel-example.png
deleted file mode 100644
index 13af9860d1e606..00000000000000
Binary files a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/parallel-example.png and /dev/null differ
diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/span-evidence.png b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/span-evidence.png
index 79a52181756d7e..fee7363e215c87 100644
Binary files a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/span-evidence.png and b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/span-evidence.png differ
diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx
index c2716aa6cb8e93..3454ba505e70e0 100644
--- a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx
+++ b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx
@@ -37,10 +37,11 @@ You can identify a Consecutive DB Queries problem by four main aspects in the "S
 - Starting Span - The first span in a set of consecutive spans
 - Parallelizable Spans - The spans that can be parallelized
 - Duration Impact - The fraction of time added to the total transaction time as a result of spans not being ran in parallel
+- Waterfall Trace View - Shows the parent span in which the consecutive DB queries occurred
 
 ![Consecutive DB Queries span evidence](./img/span-evidence.png)
 
-View it by going to the **Issues** page in Sentry, selecting your project, clicking on the Consecutive DB Queries error you want to examine, then scrolling down to the "Span Evidence" section in the "Details" tab.
+View it by going to the **Issues** page in Sentry, selecting your project, clicking on the Consecutive DB Queries error you want to examine, then scrolling down to the "Span Evidence" section.
 
 ## Example
 
@@ -55,8 +56,6 @@ processMyData({ result, count });
 This results in a consecutive DB performance issue. You'll notice these queries occur sequentially in the span tree,
 but they aren't interdependent because the result of one doesn't affect the other. Therefore, they can be executed in parallel.
 
-![Consecutive DB Queries example](./img/consecutive-example.png)
-
 To fix this performance issue, you could use Promise.all():
 
 ```javascript
@@ -68,5 +67,3 @@ processMyData({ result, count });
 ```
 
 This makes the queries execute in parallel, which in this case, reduced the transaction duration by almost half!
-
-![Consecutive DB Queries solved](./img/parallel-example.png)