diff --git a/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx b/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx
index a798433c02947..d1ca9db0f4f0a 100644
--- a/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx
+++ b/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx
@@ -23,12 +23,12 @@ You can configure detector thresholds for file I/O on main thread issues in **Pr
 Span evidence identifies the root cause of the File I/O on Main Thread problem by showing you three main aspects:
 
 - Transaction name
-- Parent Span - Where the file I/O spans occurred
 - Offending Span - The actual spans that are performing file I/O in the main thread
+- Waterfall Trace View - Shows the parent span in which the file I/O spans occurred
 
 ![File I/O Span Evidence](./img/file-io.png)
 
-View it by going to the **Issues** page in Sentry, selecting your Android project, clicking on the file I/O 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 file I/O error you want to examine, then scrolling down to the "Span Evidence" section.
 
 ## Example
 
diff --git a/docs/product/issues/issue-details/performance-issues/img/file-io.png b/docs/product/issues/issue-details/performance-issues/img/file-io.png
index 0095476951cb3..149d483d8ee17 100644
Binary files a/docs/product/issues/issue-details/performance-issues/img/file-io.png and b/docs/product/issues/issue-details/performance-issues/img/file-io.png differ