diff --git a/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx
index 1b19f192405b1..086a8329d6a7d 100644
--- a/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx
@@ -4,6 +4,9 @@ description: "Learn what spans are captured after tracing is enabled."
 sidebar_order: 10
 notSupported:
   - javascript.cordova
+  - javascript.deno
+  - javascript.cloudflare
+  - javascript.bun
 ---
 
 <Alert>
diff --git a/docs/platforms/javascript/guides/bun/index.mdx b/docs/platforms/javascript/guides/bun/index.mdx
index 278ab78f34b44..5fd3d1203e835 100644
--- a/docs/platforms/javascript/guides/bun/index.mdx
+++ b/docs/platforms/javascript/guides/bun/index.mdx
@@ -56,7 +56,7 @@ Sentry.init({
 });
 ```
 
-Once you set a `tracesSampleRate`, performance instrumentation is automatically enabled for you. See <PlatformLink to="/tracing/instrumentation/automatic-instrumentation">Automatic Instrumentation</PlatformLink> to learn about all the things that the SDK automatically instruments for you.
+Once you set a `tracesSampleRate`, performance instrumentation is automatically enabled for you.
 
 You can also manually capture performance data - see <PlatformLink to="/tracing/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> for details.