From 8c45e7b0d650515225974236af9b9f90d5a6f1cf Mon Sep 17 00:00:00 2001
From: felixfon <66350602+felixfon@users.noreply.github.com>
Date: Wed, 5 Mar 2025 01:15:21 +0800
Subject: [PATCH] fix: correct typo in javascript v8-to-v9.mdx (#12847)

---
 docs/platforms/javascript/common/migration/v8-to-v9.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/platforms/javascript/common/migration/v8-to-v9.mdx b/docs/platforms/javascript/common/migration/v8-to-v9.mdx
index db7a902906f7f..a47881968fc3a 100644
--- a/docs/platforms/javascript/common/migration/v8-to-v9.mdx
+++ b/docs/platforms/javascript/common/migration/v8-to-v9.mdx
@@ -157,13 +157,13 @@ The changes outlined in this section describe in what way the SDK may behave dif
   This is no longer the case and sampling decisions will be deferred to downstream SDKs for distributed tracing.
   This is more of a bugfix rather than a breaking change, however, depending on the setup of your SDKs, an increase in sampled traces may be observed.
 
-- If you use the optional `captureConsoleIntegration` and set `attachStackTrace: true` in your `Sentry.init` call, console messages will no longer be marked as unhandled (`handled: false`) but as handled (`handled: true`).
+- If you use the optional `captureConsoleIntegration` and set `attachStacktrace: true` in your `Sentry.init` call, console messages will no longer be marked as unhandled (`handled: false`) but as handled (`handled: true`).
   If you want to keep sending them as unhandled, configure the `handled` option when adding the integration:
 
   ```javascript
   Sentry.init({
     integrations: [Sentry.captureConsoleIntegration({ handled: false })],
-    attachStackTrace: true,
+    attachStacktrace: true,
   });
   ```