diff --git a/docs/product/issues/issue-details/replay-issues/index.mdx b/docs/product/issues/issue-details/replay-issues/index.mdx
index 7fb404bf09ce1..c387b6fa4e2f0 100644
--- a/docs/product/issues/issue-details/replay-issues/index.mdx
+++ b/docs/product/issues/issue-details/replay-issues/index.mdx
@@ -21,7 +21,7 @@ While you can enable **session replay** with JavaScript SDK version 7.27.0, or h
 
 ## Detection Criteria
 
-"Slow clicks" are only detected on `<button>`, `<input>`, and `<a>` elements that don't lead to either updates to the DOM or a page scroll within 7 seconds (aka a "dead click"). When the user clicks on one of these elements 3 or more times within that 7 second time frame, it indicates frustration, and the SDK registers a "rage click". 
+"Slow clicks" (also called "dead clicks") are only detected on `<button>`, `<input>`, and `<a>` elements that don't lead to either updates to the DOM or a page scroll within 7 seconds). When the user clicks on one of these elements 3 or more times within that 7 second time frame, it indicates frustration, and the SDK registers a "rage click". 
 
 ### Why am I seeing too many or too few rage clicks?
 There might be fewer rage clicks than you expect if the user stopped waiting for the site to respond before the 7 second threshold and instead chose to to something else. This is why the rage click issues that you *do* see are so valuable, because the user that clicked at least 3 times and continued waiting at least 7 seconds for the site to respond is likely very frustrated.