diff --git a/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx b/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx
index 7330defec8d7c..1e27a9502b420 100644
--- a/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx
+++ b/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx
@@ -109,16 +109,6 @@ In `session` mode, this will upload any pending recording data to Sentry. In `bu
 
 Note that it's safe to call `flush()` at any time, even if Session Replay is stopped, in which case, it will do nothing.
 
-## Dead Clicks and Rage Clicks
-
-The Replay SDK tries to detect cases where a user clicked on something, but nothing happened. This is called a "dead click" -- a click that seems to be "dead" and does nothing, from the user's perspective. This can happen if a bug prevents the UI from being correctly updated after a button is clicked.
-
-Another concept related to this is "rage clicks". A rage click is when a user clicks on an element many times in a short period, which indicates frustration that something isn't working.
-
-When a slow click and a rage click come together, we have a very good indicator that something is actually wrong, and the Replay SDK will generate a "rage click" for this.
-
-Session Replay will generate and link [Rage Click Issues](https://docs.sentry.io/product/issues/issue-details/replay-issues/) to help you identify user frustration and appropriately prioritize issues. 
-
 ## Examples of Custom Sampling
 
 There are ways to enable custom sampling if you're interested in tracking a particular action or group, for example, a specific segment of users or a problematic URL.