diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-http/img/span-evidence.png b/docs/product/issues/issue-details/performance-issues/consecutive-http/img/span-evidence.png
index 86c04ae4d58b5..1490622a195d7 100644
Binary files a/docs/product/issues/issue-details/performance-issues/consecutive-http/img/span-evidence.png and b/docs/product/issues/issue-details/performance-issues/consecutive-http/img/span-evidence.png differ
diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx b/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx
index 854ddd12c84e7..b4abae8a84360 100644
--- a/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx
+++ b/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx
@@ -41,11 +41,11 @@ You can configure detector thresholds for Consecutive HTTP issues in **Project S
 You can find additional information about your Consecutive HTTP issue by looking at two main aspects in the "Span Evidence" section:
 
 - **Transaction name**
-- **Sequential HTTP Spans**
+- **Offending Spans**
 
 ![Consecutive HTTP span evidence](./img/span-evidence.png)
 
-You can view the span evidence by going to the **Issues** page in Sentry, selecting your project, selecting the Consecutive HTTP Queries error you want to examine, then scrolling down to the "Span Evidence" section in the "Details" tab.
+You can view the span evidence by going to the **Issues** page in Sentry, selecting your project, selecting the Consecutive HTTP Queries error you want to examine, then scrolling down to the "Span Evidence" section.
 
 ## Fixing Consecutive HTTP Issues