From fe3faddc00315ed125d3db85f3e134baa6580824 Mon Sep 17 00:00:00 2001
From: Sarah Guthals <sarah@guthals.com>
Date: Wed, 12 Jun 2024 16:25:04 -0700
Subject: [PATCH] Update
 docs/product/issues/issue-details/replay-issues/index.mdx

Co-authored-by: vivianyentran <20403606+vivianyentran@users.noreply.github.com>
---
 docs/product/issues/issue-details/replay-issues/index.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/product/issues/issue-details/replay-issues/index.mdx b/docs/product/issues/issue-details/replay-issues/index.mdx
index c387b6fa4e2f0..0be20b1c8890e 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" (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". 
+"Slow clicks" (also called "dead clicks") are only detected on `<button>`, `<input>`, and `<a>` elements that don't lead to 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.