small copy change

Author: rishabhpoddar

v2/emailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx

@@ -121,15 +121,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -153,15 +145,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 

v2/emailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx

@@ -201,15 +201,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -233,15 +225,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 

v2/passwordless/common-customizations/sessions/jwt-signing-key-rotation.mdx

@@ -121,15 +121,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -153,15 +145,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 

v2/passwordless/common-customizations/sessions/with-jwt/jwt-verification.mdx

@@ -201,15 +201,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -233,15 +225,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 

v2/session/common-customizations/sessions/jwt-signing-key-rotation.mdx

@@ -121,15 +121,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -153,15 +145,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 

v2/session/common-customizations/sessions/with-jwt/jwt-verification.mdx

@@ -201,15 +201,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -233,15 +225,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 

v2/thirdparty/common-customizations/sessions/jwt-signing-key-rotation.mdx

@@ -121,15 +121,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -153,15 +145,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 

v2/thirdparty/common-customizations/sessions/with-jwt/jwt-verification.mdx

@@ -201,15 +201,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -233,15 +225,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 

v2/thirdpartyemailpassword/common-customizations/sessions/jwt-signing-key-rotation.mdx

@@ -121,15 +121,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -153,15 +145,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 

v2/thirdpartyemailpassword/common-customizations/sessions/with-jwt/jwt-verification.mdx

@@ -201,15 +201,7 @@ func main() {
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::
 
 </TabItem>
@@ -233,15 +225,7 @@ init(
 ```
 
 :::caution
-Once you make the change to this boolean, you will need to run the following query in your database for it to take affect for existing sessions (otherwise those users will be stuck in an infinite refresh loop):
-
-If `useDynamicAccessTokenSigningKey` is false: 
-- `UPDATE session_info SET use_static_key = true;`
-
-Else if `useDynamicAccessTokenSigningKey` is true:
-- `UPDATE session_info SET use_static_key = false;`
-
-If you are using the managed core, you can send an email to us about this, and we will run the query for you.
+Updating this value will cause a spike in the session refresh API, as and when users visit your application.
 :::