diff --git a/docs/security/fixation-protection.mdx b/docs/security/fixation-protection.mdx
index 09ceda3c54..84bae93ba3 100644
--- a/docs/security/fixation-protection.mdx
+++ b/docs/security/fixation-protection.mdx
@@ -1,17 +1,11 @@
 ---
 title: Fixation protection
-description: Session Fixation is an attack that permits an attacker to hijack a valid user session. The attack explores a limitation in the way the web application manages the session ID, more specifically the vulnerable web application. When authenticating a user, it doesn’t assign a new session ID, making it possible to use an existent session ID.
+description: Session fixation is an attack that permits an attacker to hijack a valid user session. The attack explores a limitation in the way the web application manages the session ID, more specifically the vulnerable web application. When authenticating a user, it doesn’t assign a new session ID, making it possible to use an existent session ID.
 ---
 
-Session Fixation is an attack that permits an attacker to hijack a valid user session. The attack explores a limitation in the way the web application manages the session ID, more specifically the vulnerable web application. When authenticating a user, it doesn't assign a new session ID, making it possible to use an existent session ID.
+Session fixation is a security vulnerability that allows an attacker to hijack a valid user session. This vulnerability arises when web applications reuse existing session IDs instead of generating new ones during the authentication process. By exploiting this flaw, attackers can potentially gain unauthorized access to a user's account and perform malicious actions on their behalf.
 
-[The OWASP® Foundation, Cross Site Request Forgery (CSRF)](https://owasp.org/www-community/attacks/Session_fixation)
-
-Session fixation is a technique for hijacking a user session.
-
-Consider an attacker visits a public computer, navigates to `example.com` and starts the sign in process, but does not finish signing in. Before leaving the computer, the attacker inspects the session token and takes it with them.
-
-Then, consider a victim sits at the same computer, navigates to `example.com`, and signs in with their own account.If `example.com` failed to reset the session token for the victim, then the attacker can hijack the victim's session and act on their behalf.
+See the [OWASP Session Fixation](https://owasp.org/www-community/attacks/Session_fixation) page for specific examples of how this attack works.
 
 ## How does Clerk protect against session fixation?