diff --git a/docs/platforms/javascript/common/configuration/options.mdx b/docs/platforms/javascript/common/configuration/options.mdx
index 99d101c191547..61146c9ff4cba 100644
--- a/docs/platforms/javascript/common/configuration/options.mdx
+++ b/docs/platforms/javascript/common/configuration/options.mdx
@@ -136,7 +136,7 @@ Sentry.init({
 
 </SdkOption>
 
-<SdkOption name="maxValueLength" type='number' defaultValue='250'>
+<SdkOption name="maxValueLength" type='number'>
 
 Maximum number of characters every string property on events sent to Sentry can have before it will be truncated.
 
diff --git a/docs/platforms/javascript/common/troubleshooting/index.mdx b/docs/platforms/javascript/common/troubleshooting/index.mdx
index b397cf4ed7e2c..130849616f26c 100644
--- a/docs/platforms/javascript/common/troubleshooting/index.mdx
+++ b/docs/platforms/javascript/common/troubleshooting/index.mdx
@@ -48,7 +48,7 @@ For more details, see the [full documentation on Event Payload](https://develop.
 
 <Expandable permalink title="Max JSON payload size">
 
-`maxValueLength` has a default value of 250, but you can adjust this value according to your needs if your messages are longer. Please note that not every single value is affected by this option.
+By default, `maxValueLength` is undefined and nothing is truncated, but you can change this value according to your needs if your messages are longer (for example, to `250`). Please note that not every single value is affected by this option.
 
 </Expandable>
 
@@ -670,10 +670,10 @@ shamefully-hoist=true
     ```
 
   </Expandable>
-  
+
   <Expandable permalink title="Client Instrumentation Hook - Slow execution detected">
     Seeing this warning in your dev build might be misleading due to Next.js dev server internals.
-    
+
     In case you are using Session Replay and experience performance issues with the client instrumentation hook, you can try lazy-loading session replay as described [here](/platforms/javascript/guides/nextjs/session-replay/#lazy-loading-replay).
 
     If you want to init the SDK itself at a later point, this will result in tracing data loosing accuracy and errors could happen before the SDK is initialized. This should be a tradeoff you make based on your use case, although we recommend initializing the SDK as early as possible.