Apply suggestions from code review

Co-authored-by: Lukas Stracke <[email protected]>

Author: mydea

docs/platforms/javascript/common/options.mdx

@@ -81,7 +81,7 @@ This variable controls the total amount of breadcrumbs that should be captured.
 
 <SdkOption name="attachStacktrace" type='boolean' defaultValue='false'>
 
-When enabled, stack traces are automatically attached to all messages logged. Stack traces are always attached to exceptions; however, when this option is set, stack traces are also sent with messages. This option, for instance, means that stack traces appear next to all log messages.
+When enabled, stack traces are automatically attached to all messages logged. Stack traces are always attached to exceptions; however, when this option is set, stack traces are also sent with messages. This option, for instance, means that stack traces appear next to all messages captured with `Sentry.captureMessage()`.
 
 Grouping in Sentry is different for events with stack traces and without. As a result, you will get new groups as you enable or disable this flag for certain events.
 
@@ -155,7 +155,7 @@ Sentry.init({
 
 <SdkOption name="maxValueLength" type='number' defaultValue='250'>
 
-Maximum number of characters a single value can have before it will be truncated.
+Maximum number of characters every string property on events sent to Sentry can have before it will be truncated.
 
 </SdkOption>
 
@@ -191,7 +191,7 @@ For more advanced configuration options, see the documentation on the <PlatformL
 
 </SdkOption>
 
-<SdkOption name="integrations" type='Array<Integration>' defaultValue='[]'>
+<SdkOption name="integrations" type='Array<Integration> | (integrations: Array<Integration>) => Array<Integration>' defaultValue='[]'>
 
 Pass additional integrations that should be initialized with the SDK. Integrations are pieces of code that can be used to extend the SDK's functionality. They can be used to add custom event processors, context providers, or to hook into the SDK's lifecycle.
 
@@ -212,7 +212,7 @@ See <PlatformLink to="/configuration/integrations/#modifying-default-integration
 The JavaScript SDK uses a transport to send events to Sentry. On modern browsers, most transports use the browsers' fetch API to send events. Transports will drop an event if it fails to send due to a lack of connection.
 
 <PlatformCategorySection supported={["browser"]}>
-  In the browser, a fetch-based transport is used by default.
+  In the browser, a `fetch`-based transport is used by default.
 </PlatformCategorySection>
 
 <PlatformCategorySection supported={["server", "serverless"]}>
@@ -237,7 +237,7 @@ Options used to configure the transport. This is an object with the following po
 
 <PlatformCategorySection supported={["browser", "desktop"]}>
   - `headers`: An object containing headers to be sent with every request. Used
-  by the SDK's fetch and XHR transports. - `fetchOptions`: An object containing
+  by the SDK's `fetch` and XHR transports. - `fetchOptions`: An object containing
   options to be passed to the `fetch` call. Used by the SDK's fetch transport.
 </PlatformCategorySection>