diff --git a/docs/platforms/javascript/guides/angular/manual-setup.mdx b/docs/platforms/javascript/guides/angular/manual-setup.mdx
index 52710f4ed6111..14107a5273ede 100644
--- a/docs/platforms/javascript/guides/angular/manual-setup.mdx
+++ b/docs/platforms/javascript/guides/angular/manual-setup.mdx
@@ -24,7 +24,13 @@ You need:
 Choose the features you want to configure, and this guide will show you how:
 
 <OnboardingOptionButtons
-  options={["error-monitoring", "performance", "session-replay", "user-feedback", "logs"]}
+  options={[
+    "error-monitoring",
+    "performance",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
 />
 
 <PlatformContent includePath="getting-started-features-expandable" />
@@ -133,7 +139,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 });
 
@@ -198,7 +204,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 });
 
diff --git a/docs/platforms/javascript/guides/astro/index.mdx b/docs/platforms/javascript/guides/astro/index.mdx
index 6cc9947d70ecc..8a9e9f5616482 100644
--- a/docs/platforms/javascript/guides/astro/index.mdx
+++ b/docs/platforms/javascript/guides/astro/index.mdx
@@ -17,16 +17,25 @@ This page walks you through adding Sentry to your Astro project, configuring it,
 
 Before we get started, make sure you have the following:
 
-* You need a Sentry [account](https://sentry.io/signup/) and [project](/product/projects/)
-* An Astro project that uses Astro `3.0.0` or newer.
-* A Node runtime:
-  * This SDK currently only works on Node runtimes (e.g. Node adapter, Vercel with Lambda functions).
-Non-Node runtimes, like Vercel's Edge runtime or Cloudflare Pages, are currently not supported.
-* If you're using Astro's Netflify adapter (`@astrojs/netlify`), you need version `5.0.0` or newer.
+- You need a Sentry [account](https://sentry.io/signup/) and [project](/product/projects/)
+- An Astro project that uses Astro `3.0.0` or newer.
+- A Node runtime:
+  - This SDK currently only works on Node runtimes (e.g. Node adapter, Vercel with Lambda functions).
+    Non-Node runtimes, like Vercel's Edge runtime or Cloudflare Pages, are currently not supported.
+- If you're using Astro's Netflify adapter (`@astrojs/netlify`), you need version `5.0.0` or newer.
 
 ## Install
 
-<OnboardingOptionButtons options={["error-monitoring", "performance", "profiling", "session-replay", "user-feedback", "logs"]} />
+<OnboardingOptionButtons
+  options={[
+    "error-monitoring",
+    "performance",
+    "profiling",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
+/>
 
 Sentry captures data by using an SDK within your application's runtime.
 
@@ -70,7 +79,6 @@ To set up the Sentry SDK, register the Sentry integration and initialize the SDK
 
 ### Astro Integration Setup
 
-
 ```javascript {filename:astro.config.mjs}
 import { defineConfig } from "astro/config";
 import sentry from "@sentry/astro";
@@ -89,8 +97,12 @@ export default defineConfig({
 ```
 
 <Alert level="warning">
-  Passing runtime-specific configuration options (`dsn`, `release`, `environment`, `sampleRate`, `tracesSampleRate`, `replaysSessionSampleRate`, `replaysOnErrorSampleRate`) to the Sentry integration will be deprecated in future versions.
-  We recommend passing your configuration directly to the respective `Sentry.init()` calls in `sentry.client.config.js` and `sentry.server.config.js` instead.
+  Passing runtime-specific configuration options (`dsn`, `release`,
+  `environment`, `sampleRate`, `tracesSampleRate`, `replaysSessionSampleRate`,
+  `replaysOnErrorSampleRate`) to the Sentry integration will be deprecated in
+  future versions. We recommend passing your configuration directly to the
+  respective `Sentry.init()` calls in `sentry.client.config.js` and
+  `sentry.server.config.js` instead.
 </Alert>
 
 ### Client-Side Setup
@@ -122,7 +134,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -148,7 +160,7 @@ Sentry.init({
 ```javascript {filename:sentry.server.config.js}
 import * as Sentry from "@sentry/astro";
 // ___PRODUCT_OPTION_START___ profiling
-import { nodeProfilingIntegration } from '@sentry/profiling-node';
+import { nodeProfilingIntegration } from "@sentry/profiling-node";
 // ___PRODUCT_OPTION_END___ profiling
 
 Sentry.init({
@@ -167,7 +179,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -179,7 +191,7 @@ Sentry.init({
 
   // Set sampling rate for profiling
   // This is relative to tracesSampleRate
-  profilesSampleRate: 1.0
+  profilesSampleRate: 1.0,
   // ___PRODUCT_OPTION_END___ profiling
 });
 ```
@@ -211,13 +223,13 @@ Trigger a test error somewhere in your Astro app, for example in one of your pag
 ```
 
 <Alert>
-  Errors triggered from within Browser DevTools are sandboxed and won't trigger an error handler.
-  Place the snippet directly in your code instead.
+  Errors triggered from within Browser DevTools are sandboxed and won't trigger
+  an error handler. Place the snippet directly in your code instead.
 </Alert>
 
 <Alert>
-  Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage
-  documentation</PlatformLink>.
+  Learn more about manually capturing an error or message in our{" "}
+  <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 </Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
@@ -245,7 +257,7 @@ export default defineConfig({
 
 <Alert>
 
-  Auto instrumentation only works for Astro 3.5.2 or newer. If you're using an older version, you need to [manually add the Sentry middleware](#manually-add-server-instrumentation) instead.
+Auto instrumentation only works for Astro 3.5.2 or newer. If you're using an older version, you need to [manually add the Sentry middleware](#manually-add-server-instrumentation) instead.
 
 </Alert>
 
diff --git a/docs/platforms/javascript/guides/cloudflare/index.mdx b/docs/platforms/javascript/guides/cloudflare/index.mdx
index 599e75a45077d..3dc50d6bbb8c6 100644
--- a/docs/platforms/javascript/guides/cloudflare/index.mdx
+++ b/docs/platforms/javascript/guides/cloudflare/index.mdx
@@ -9,10 +9,9 @@ categories:
   - serverless
 ---
 
-
 You can use the Sentry Cloudflare SDK with popular frameworks running on Cloudflare:
 
-- **[Astro](frameworks/astro/)** 
+- **[Astro](frameworks/astro/)**
 - **[Hono](frameworks/hono/)**
 - **[Remix](frameworks/remix/)**
 - **[SvelteKit](frameworks/sveltekit/)**
@@ -41,7 +40,10 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 ### Setup (Cloudflare Workers)
 
-<PlatformContent includePath="getting-started-config" platform="javascript.cloudflare.workers" />
+<PlatformContent
+  includePath="getting-started-config"
+  platform="javascript.cloudflare.workers"
+/>
 
 If you do not have access to the `onRequest` middleware API, you can use the `wrapRequestHandler` API instead. For example:
 
@@ -81,14 +83,14 @@ export const onRequest = [
       dsn: "___PUBLIC_DSN___",
 
       release: versionId,
- 
+
       // Adds request headers and IP for users, for more info visit:
       // https://docs.sentry.io/platforms/javascript/guides/cloudflare/configuration/options/#sendDefaultPii
       sendDefaultPii: true,
       // ___PRODUCT_OPTION_START___ logs
 
       // Enable logs to be sent to Sentry
-      _experiments: { enableLogs: true },
+      enableLogs: true,
       // ___PRODUCT_OPTION_END___ logs
 
       // ___PRODUCT_OPTION_START___ performance
@@ -97,7 +99,7 @@ export const onRequest = [
       // https://docs.sentry.io/platforms/javascript/configuration/options/#traces-sample-rate
       tracesSampleRate: 1.0,
       // ___PRODUCT_OPTION_END___ performance
-    }
+    };
   }),
   // Add more middlewares here
 ];
diff --git a/docs/platforms/javascript/guides/ember/index.mdx b/docs/platforms/javascript/guides/ember/index.mdx
index 5edbd3a6cb3c0..e4de94aade84c 100644
--- a/docs/platforms/javascript/guides/ember/index.mdx
+++ b/docs/platforms/javascript/guides/ember/index.mdx
@@ -8,7 +8,7 @@ categories:
 
 <Alert>
 
-  Sentry's Ember addon enables automatic reporting of errors, exceptions, and transactions.
+Sentry's Ember addon enables automatic reporting of errors, exceptions, and transactions.
 
 </Alert>
 
@@ -24,7 +24,15 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 ## Install
 
-<OnboardingOptionButtons options={["error-monitoring", "performance", "session-replay", "user-feedback", "logs"]} />
+<OnboardingOptionButtons
+  options={[
+    "error-monitoring",
+    "performance",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
+/>
 
 Sentry captures data by using an SDK within your application's runtime.
 
@@ -46,11 +54,11 @@ import * as Sentry from "@sentry/ember";
 
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
-  
+
   // Adds request headers and IP for users, for more info visit:
   // https://docs.sentry.io/platforms/javascript/guides/ember/configuration/options/#sendDefaultPii
   sendDefaultPii: true,
-  
+
   // ___PRODUCT_OPTION_START___ session-replay
   integrations: [
     Sentry.replayIntegration(),
@@ -65,7 +73,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -96,7 +104,7 @@ export default class App extends Application {
 
 <Alert>
 
-  This SDK uses Ember configuration conventions to manage its automatic instrumentation and other Sentry options. This additional configuration can be found under <PlatformLink to="/configuration/ember-options/">Ember options</PlatformLink>.
+This SDK uses Ember configuration conventions to manage its automatic instrumentation and other Sentry options. This additional configuration can be found under <PlatformLink to="/configuration/ember-options/">Ember options</PlatformLink>.
 
 </Alert>
 
diff --git a/docs/platforms/javascript/guides/gatsby/index.mdx b/docs/platforms/javascript/guides/gatsby/index.mdx
index e6842ef532ec8..46f1d1b8d891c 100644
--- a/docs/platforms/javascript/guides/gatsby/index.mdx
+++ b/docs/platforms/javascript/guides/gatsby/index.mdx
@@ -15,7 +15,15 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 ## Install
 
-<OnboardingOptionButtons options={["error-monitoring", "performance", "session-replay", "user-feedback", "logs"]} />
+<OnboardingOptionButtons
+  options={[
+    "error-monitoring",
+    "performance",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
+/>
 
 To use Sentry with your Gatsby application, you will need to use `@sentry/gatsby` (Sentry's Gatsby SDK):
 
@@ -53,17 +61,16 @@ module.exports = {
 
 Then, configure your `Sentry.init`. For this, create a new file called `sentry.config.js` in the root of your project and add the following code:
 
-
 ```javascript {filename:sentry.config.(js|ts)}
 import * as Sentry from "@sentry/gatsby";
 
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
-  
+
   // Adds request headers and IP for users, for more info visit:
   // https://docs.sentry.io/platforms/javascript/guides/gatsby/configuration/options/#sendDefaultPii
   sendDefaultPii: true,
-  
+
   integrations: [
     // ___PRODUCT_OPTION_START___ performance
     Sentry.browserTracingIntegration(),
@@ -81,7 +88,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
diff --git a/docs/platforms/javascript/guides/nextjs/index.mdx b/docs/platforms/javascript/guides/nextjs/index.mdx
index 7e01df44ba11b..97602d8a94f46 100644
--- a/docs/platforms/javascript/guides/nextjs/index.mdx
+++ b/docs/platforms/javascript/guides/nextjs/index.mdx
@@ -20,7 +20,13 @@ In addition to capturing errors, you can monitor interactions between multiple s
 Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.
 
 <OnboardingOptionButtons
-  options={["error-monitoring", "performance", "session-replay", "user-feedback", "logs"]}
+  options={[
+    "error-monitoring",
+    "performance",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
 />
 
 ## Step 1: Install
@@ -82,7 +88,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -94,7 +100,7 @@ Sentry.init({
   tracesSampleRate: 1.0,
   // ___PRODUCT_OPTION_END___ performance
   // ___PRODUCT_OPTION_START___ session-replay
-  // Capture Replay for 10% of all 
+  // Capture Replay for 10% of all
   // plus for 100% of sessions with an error
   // Learn more at
   // https://docs.sentry.io/platforms/javascript/session-replay/configuration/#general-integration-configuration
@@ -118,7 +124,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup.mdx
index fccd01f0959dc..092f6597dacb2 100644
--- a/docs/platforms/javascript/guides/nextjs/manual-setup.mdx
+++ b/docs/platforms/javascript/guides/nextjs/manual-setup.mdx
@@ -151,7 +151,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
   // Note: if you want to override the automatic release value, do not set a
   // `release` value here - use the environment variable `SENTRY_RELEASE`, so
@@ -184,7 +184,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ...
@@ -216,7 +216,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ...
@@ -459,6 +459,7 @@ Make sure to keep your auth token secret and out of version control.
 You can prevent ad blockers from blocking Sentry events using tunneling. Use the `tunnelRoute` option to add an API endpoint in your application that forwards Sentry events to Sentry servers.
 
 For better ad-blocker evasion, you can either:
+
 - Set `tunnelRoute: true` to automatically generate a random tunnel route for each build, making it harder for ad-blockers to detect and block monitoring requests
 - Set `tunnelRoute: "/my-tunnel-route"` to use a static route of your choosing
 
@@ -481,9 +482,12 @@ module.exports = withSentryConfig(nextConfig, {
 ```
 
 <Expandable level="warning" title="Using Next.js middleware on Turbopack">
-  If you're using Turbopack, client-side event recording will fail if your Next.js middleware intercepts the configured tunnel route. To fix this, set the route to a fixed string (like `/error-monitoring`) and add a negative matcher like `(?!error-monitoring)` in your middleware to exclude the tunnel route.
-  
-  If you're not using Turbopack, Sentry will automatically skip the tunnel route in your middleware.
+  If you're using Turbopack, client-side event recording will fail if your
+  Next.js middleware intercepts the configured tunnel route. To fix this, set
+  the route to a fixed string (like `/error-monitoring`) and add a negative
+  matcher like `(?!error-monitoring)` in your middleware to exclude the tunnel
+  route. If you're not using Turbopack, Sentry will automatically skip the
+  tunnel route in your middleware.
 </Expandable>
 
 ## Step 6: Instrument Vercel Cron Jobs (Optional)
diff --git a/docs/platforms/javascript/guides/nuxt/manual-setup.mdx b/docs/platforms/javascript/guides/nuxt/manual-setup.mdx
index e41f7aa9c5003..22d0d0ebfd88b 100644
--- a/docs/platforms/javascript/guides/nuxt/manual-setup.mdx
+++ b/docs/platforms/javascript/guides/nuxt/manual-setup.mdx
@@ -112,7 +112,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 });
 ```
@@ -155,7 +155,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 });
 ```
diff --git a/docs/platforms/javascript/guides/react-router/index.mdx b/docs/platforms/javascript/guides/react-router/index.mdx
index c6454579c0123..91b6856662666 100644
--- a/docs/platforms/javascript/guides/react-router/index.mdx
+++ b/docs/platforms/javascript/guides/react-router/index.mdx
@@ -118,7 +118,7 @@ Initialize the Sentry React SDK in your `entry.client.tsx` file:
 +  // ___PRODUCT_OPTION_START___ logs
 +
 +  // Enable logs to be sent to Sentry
-+  _experiments: { enableLogs: true },
++  enableLogs: true,
 +  // ___PRODUCT_OPTION_END___ logs
 +  // ___PRODUCT_OPTION_START___ performance
 +
@@ -246,7 +246,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
   // ___PRODUCT_OPTION_START___ profiling
 
@@ -446,7 +446,7 @@ export default {
   buildEnd: async ({ viteConfig, reactRouterConfig, buildManifest }) => {
     // ...
     // Call this at the end of the hook
-+   (await sentryOnBuildEnd({ viteConfig, reactRouterConfig, buildManifest }));
+    +(await sentryOnBuildEnd({ viteConfig, reactRouterConfig, buildManifest }));
   },
 } satisfies Config;
 ```
diff --git a/docs/platforms/javascript/guides/react/index.mdx b/docs/platforms/javascript/guides/react/index.mdx
index 06b2cc6ef2141..c87a1ab2890cc 100644
--- a/docs/platforms/javascript/guides/react/index.mdx
+++ b/docs/platforms/javascript/guides/react/index.mdx
@@ -20,7 +20,13 @@ categories:
 Choose the features you want to configure, and this guide will show you how:
 
 <OnboardingOptionButtons
-  options={["error-monitoring", "performance", "session-replay", "user-feedback", "logs"]}
+  options={[
+    "error-monitoring",
+    "performance",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
 />
 
 <PlatformContent includePath="getting-started-features-expandable" />
@@ -81,7 +87,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -120,6 +126,7 @@ const container = document.getElementById(“app”);
 const root = createRoot(container);
 root.render(<App />);
 ```
+
 </OnboardingOption>
 <OnboardingOption isStep>
 ## Capture React Errors
diff --git a/docs/platforms/javascript/guides/remix/manual-setup.mdx b/docs/platforms/javascript/guides/remix/manual-setup.mdx
index fce4b28a11845..41ae1876ec09f 100644
--- a/docs/platforms/javascript/guides/remix/manual-setup.mdx
+++ b/docs/platforms/javascript/guides/remix/manual-setup.mdx
@@ -16,7 +16,14 @@ description: "Learn how to manually set up Sentry in your Remix app and capture
 Choose the features you want to configure, and this guide will show you how:
 
 <OnboardingOptionButtons
-  options={["error-monitoring", "performance", "profiling", "session-replay", "user-feedback", "logs"]}
+  options={[
+    "error-monitoring",
+    "performance",
+    "profiling",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
 />
 
 <PlatformContent includePath="getting-started-features-expandable" />
@@ -98,7 +105,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 });
 ```
@@ -182,7 +189,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // Optionally capture action formData attributes with errors.
diff --git a/docs/platforms/javascript/guides/solid/index.mdx b/docs/platforms/javascript/guides/solid/index.mdx
index 25da692de4f2f..5e1ffb6533545 100644
--- a/docs/platforms/javascript/guides/solid/index.mdx
+++ b/docs/platforms/javascript/guides/solid/index.mdx
@@ -16,7 +16,15 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 ## Install
 
-<OnboardingOptionButtons options={["error-monitoring", "performance", "session-replay", "user-feedback", "logs"]} />
+<OnboardingOptionButtons
+  options={[
+    "error-monitoring",
+    "performance",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
+/>
 
 Sentry captures data by using an SDK within your application's runtime.
 
@@ -38,10 +46,7 @@ Configuration should happen as early as possible in your application's lifecycle
 
 To use the SDK, initialize it in your Solid entry point before bootstrapping your app. In a typical Solid project, that is your `index.jsx` file.
 
-<Alert>
-  We currently support Solid 1.8.4 and up.
-</Alert>
-
+<Alert>We currently support Solid 1.8.4 and up.</Alert>
 
 ```javascript {filename: index.jsx}
 import * as Sentry from "@sentry/solid";
@@ -56,11 +61,11 @@ import App from "./app";
 if (!DEV) {
   Sentry.init({
     dsn: "___PUBLIC_DSN___",
-    
+
     // Adds request headers and IP for users, for more info visit:
     // https://docs.sentry.io/platforms/javascript/guides/solid/configuration/options/#sendDefaultPii
     sendDefaultPii: true,
-    
+
     integrations: [
       // ___PRODUCT_OPTION_START___ performance
       solidRouterBrowserTracingIntegration(),
@@ -78,7 +83,7 @@ if (!DEV) {
     // ___PRODUCT_OPTION_START___ logs
 
     // Enable logs to be sent to Sentry
-    _experiments: { enableLogs: true },
+    enableLogs: true,
     // ___PRODUCT_OPTION_END___ logs
 
     // ___PRODUCT_OPTION_START___ performance
diff --git a/docs/platforms/javascript/guides/svelte/index.mdx b/docs/platforms/javascript/guides/svelte/index.mdx
index 29a90deefe55a..c25b93d7fea23 100644
--- a/docs/platforms/javascript/guides/svelte/index.mdx
+++ b/docs/platforms/javascript/guides/svelte/index.mdx
@@ -18,7 +18,13 @@ categories:
 Choose the features you want to configure, and this guide will show you how:
 
 <OnboardingOptionButtons
-  options={["error-monitoring", "performance", "session-replay", "user-feedback", "logs"]}
+  options={[
+    "error-monitoring",
+    "performance",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
 />
 
 <PlatformContent includePath="getting-started-features-expandable" />
@@ -38,6 +44,7 @@ yarn add @sentry/svelte
 ```bash {tabTitle:pnpm}
 pnpm add @sentry/svelte
 ```
+
 </OnboardingOption>
 
 <OnboardingOption isStep>
@@ -78,7 +85,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -136,7 +143,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -167,6 +174,7 @@ const app = new App({
 
 export default app;
 ```
+
 </OnboardingOption>
 
 <OnboardingOption isStep>
diff --git a/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx b/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx
index 8759d5eaa3f31..d8e66a7f1808a 100644
--- a/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx
+++ b/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx
@@ -94,7 +94,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 });
 
@@ -133,7 +133,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 });
 
diff --git a/docs/platforms/javascript/guides/tanstackstart-react/index.mdx b/docs/platforms/javascript/guides/tanstackstart-react/index.mdx
index c2e315fee6b41..1370f4f08a1f8 100644
--- a/docs/platforms/javascript/guides/tanstackstart-react/index.mdx
+++ b/docs/platforms/javascript/guides/tanstackstart-react/index.mdx
@@ -5,15 +5,14 @@ description: "Learn how to set up and configure Sentry in your TanStack Start Re
 
 <Alert>
 
-  This SDK is currently in **ALPHA**. Alpha features are still in progress, may have bugs and might include breaking changes.
-  Please reach out on  [GitHub](https://github.com/getsentry/sentry-javascript/issues/new/choose) if you have any feedback or concerns.
-  This SDK is for [TanStack Start (React)](https://tanstack.com/start/latest/docs/framework/react/overview), for
-  using [TanStack Router (React)](https://tanstack.com/router/latest/docs/framework/react/overview) see our React docs for
-  [TanStack Router](/platforms/javascript/guides/react/features/tanstack-router).
+This SDK is currently in **ALPHA**. Alpha features are still in progress, may have bugs and might include breaking changes.
+Please reach out on [GitHub](https://github.com/getsentry/sentry-javascript/issues/new/choose) if you have any feedback or concerns.
+This SDK is for [TanStack Start (React)](https://tanstack.com/start/latest/docs/framework/react/overview), for
+using [TanStack Router (React)](https://tanstack.com/router/latest/docs/framework/react/overview) see our React docs for
+[TanStack Router](/platforms/javascript/guides/react/features/tanstack-router).
 
 </Alert>
 
-
 <PlatformContent includePath="getting-started-prerequisites" />
 
 ## Step 1: Install
@@ -21,7 +20,13 @@ description: "Learn how to set up and configure Sentry in your TanStack Start Re
 Choose the features you want to configure, and this guide will show you how:
 
 <OnboardingOptionButtons
-  options={["error-monitoring", "performance", "session-replay", "user-feedback", "logs"]}
+  options={[
+    "error-monitoring",
+    "performance",
+    "session-replay",
+    "user-feedback",
+    "logs",
+  ]}
 />
 
 <PlatformContent includePath="getting-started-features-expandable" />
@@ -77,7 +82,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -114,7 +119,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -175,7 +180,9 @@ import * as Sentry from "@sentry/tanstackstart-react";
 
 registerGlobalMiddleware({
   middleware: [
-    createMiddleware({ type: 'function' }).server(Sentry.sentryGlobalServerMiddlewareHandler()),
+    createMiddleware({ type: "function" }).server(
+      Sentry.sentryGlobalServerMiddlewareHandler()
+    ),
   ],
 });
 ```
@@ -183,7 +190,9 @@ registerGlobalMiddleware({
 ### Capture Errors in your Error Boundaries and Components
 
 <Alert level="info">
-  Automatic error monitoring is not yet supported on the on the server-side of TanStack Start. Use `captureException` to manually capture errors in your server-side code.
+  Automatic error monitoring is not yet supported on the on the server-side of
+  TanStack Start. Use `captureException` to manually capture errors in your
+  server-side code.
 </Alert>
 
 The Sentry SDK cannot capture errors that you manually caught yourself with error boundaries.
@@ -198,9 +207,12 @@ class MyErrorBoundary extends React.Component {
   // ...
 }
 
-export const MySentryWrappedErrorBoundary = Sentry.withErrorBoundary(MyErrorBoundary, {
-  // ... sentry error wrapper options
-});
+export const MySentryWrappedErrorBoundary = Sentry.withErrorBoundary(
+  MyErrorBoundary,
+  {
+    // ... sentry error wrapper options
+  }
+);
 ```
 
 If you defined `errorComponent`s in your Code-Based TanStack Router routes, capture the `error` argument with `captureException` inside a `useEffect` hook:
diff --git a/docs/platforms/javascript/guides/vue/index.mdx b/docs/platforms/javascript/guides/vue/index.mdx
index 6db1a53b1509c..837feb3018a75 100644
--- a/docs/platforms/javascript/guides/vue/index.mdx
+++ b/docs/platforms/javascript/guides/vue/index.mdx
@@ -82,7 +82,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -142,7 +142,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
diff --git a/platform-includes/getting-started-config/javascript.cloudflare.workers.mdx b/platform-includes/getting-started-config/javascript.cloudflare.workers.mdx
index 445e825cc1e24..76e40c9f14fd5 100644
--- a/platform-includes/getting-started-config/javascript.cloudflare.workers.mdx
+++ b/platform-includes/getting-started-config/javascript.cloudflare.workers.mdx
@@ -21,7 +21,7 @@ export default Sentry.withSentry(
       // ___PRODUCT_OPTION_START___ logs
 
       // Enable logs to be sent to Sentry
-      _experiments: { enableLogs: true },
+      enableLogs: true,
       // ___PRODUCT_OPTION_END___ logs
 
       // ___PRODUCT_OPTION_START___ performance
diff --git a/platform-includes/getting-started-config/javascript.mdx b/platform-includes/getting-started-config/javascript.mdx
index ccf847a38e13f..5e4de083a78eb 100644
--- a/platform-includes/getting-started-config/javascript.mdx
+++ b/platform-includes/getting-started-config/javascript.mdx
@@ -1,10 +1,10 @@
 <OnboardingOptionButtons
   options={[
-    'error-monitoring',
-    'performance',
-    'session-replay',
-    'user-feedback',
-    'logs',
+    "error-monitoring",
+    "performance",
+    "session-replay",
+    "user-feedback",
+    "logs",
   ]}
 />
 
@@ -17,7 +17,7 @@ import * as Sentry from "@sentry/browser";
 
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
-  
+
   // Adds request headers and IP for users, for more info visit:
   // https://docs.sentry.io/platforms/javascript/configuration/options/#sendDefaultPii
   sendDefaultPii: true,
@@ -42,7 +42,7 @@ Sentry.init({
 
   // ___PRODUCT_OPTION_START___ logs
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 
   // ___PRODUCT_OPTION_START___ performance
@@ -78,7 +78,7 @@ Sentry.init({
   window.sentryOnLoad = function () {
     Sentry.init({
       dsn: "___PUBLIC_DSN___",
-      
+
       // Adds request headers and IP for users, for more info visit:
       // https://docs.sentry.io/platforms/javascript/configuration/options/#sendDefaultPii
       sendDefaultPii: true,
@@ -103,7 +103,7 @@ Sentry.init({
 
       // ___PRODUCT_OPTION_START___ logs
       // Enable logs to be sent to Sentry
-      _experiments: { enableLogs: true },
+      enableLogs: true,
       // ___PRODUCT_OPTION_END___ logs
 
       // ___PRODUCT_OPTION_START___ performance
@@ -122,7 +122,7 @@ Sentry.init({
       // Capture Replay for 10% of all sessions,
       // plus for 100% of sessions with an error
       // Learn more at
-     // https://docs.sentry.io/platforms/javascript/session-replay/configuration/#general-integration-configuration
+      // https://docs.sentry.io/platforms/javascript/session-replay/configuration/#general-integration-configuration
       replaysSessionSampleRate: 0.1,
       replaysOnErrorSampleRate: 1.0,
       // ___PRODUCT_OPTION_END___ session-replay
@@ -141,7 +141,7 @@ Sentry.init({
 <script>
   Sentry.init({
     dsn: "___PUBLIC_DSN___",
-    
+
     // Adds request headers and IP for users, for more info visit:
     // https://docs.sentry.io/platforms/javascript/configuration/options/#sendDefaultPii
     sendDefaultPii: true,
@@ -166,7 +166,7 @@ Sentry.init({
 
     // ___PRODUCT_OPTION_START___ logs
     // Enable logs to be sent to Sentry
-    _experiments: { enableLogs: true },
+    enableLogs: true,
     // ___PRODUCT_OPTION_END___ logs
 
     // ___PRODUCT_OPTION_START___ performance
diff --git a/platform-includes/getting-started-config/javascript.node.mdx b/platform-includes/getting-started-config/javascript.node.mdx
index 029592c6b27f9..77f233159eb27 100644
--- a/platform-includes/getting-started-config/javascript.node.mdx
+++ b/platform-includes/getting-started-config/javascript.node.mdx
@@ -7,12 +7,12 @@ const { nodeProfilingIntegration } = require("@sentry/profiling-node");
 // Ensure to call this before requiring any other modules!
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
-  
+
   // Adds request headers and IP for users, for more info visit:
   // https://docs.sentry.io/platforms/javascript/guides/node/configuration/options/#sendDefaultPii
   sendDefaultPii: true,
   // ___PRODUCT_OPTION_START___ profiling
-  
+
   integrations: [
     // Add our Profiling integration
     nodeProfilingIntegration(),
@@ -39,7 +39,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 });
 ```
@@ -53,7 +53,7 @@ import { nodeProfilingIntegration } from "@sentry/profiling-node";
 // Ensure to call this before importing any other modules!
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
-  
+
   // Adds request headers and IP for users, for more info visit:
   // https://docs.sentry.io/platforms/javascript/guides/node/configuration/options/#sendDefaultPii
   sendDefaultPii: true,
@@ -85,7 +85,7 @@ Sentry.init({
   // ___PRODUCT_OPTION_START___ logs
 
   // Enable logs to be sent to Sentry
-  _experiments: { enableLogs: true },
+  enableLogs: true,
   // ___PRODUCT_OPTION_END___ logs
 });
 ```
diff --git a/platform-includes/llm-rules-logs/javascript.nextjs.mdx b/platform-includes/llm-rules-logs/javascript.nextjs.mdx
index 541cac7f1d7be..180c70259b1ea 100644
--- a/platform-includes/llm-rules-logs/javascript.nextjs.mdx
+++ b/platform-includes/llm-rules-logs/javascript.nextjs.mdx
@@ -3,11 +3,10 @@
 When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
-
 # Logs
 
 - Where logs are used, ensure Sentry is imported using `import * as Sentry from "@sentry/nextjs"`
-- Enable logging in Sentry using `Sentry.init({ _experiments: { enableLogs: true } })`
+- Enable logging in Sentry using `Sentry.init({ enableLogs: true })`
 - Reference the logger using `const { logger } = Sentry`
 - Sentry offers a `consoleLoggingIntegration` that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
@@ -23,10 +22,7 @@ import * as Sentry from "@sentry/nextjs";
 Sentry.init({
   dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
 
-  _experiments: {
-    enableLogs: true,
-  },
-
+  enableLogs: true,
 });
 ```
 
@@ -68,4 +64,5 @@ logger.fatal("Database connection pool exhausted", {
 });
 ```
 ````
+
 </Expandable>
diff --git a/platform-includes/llm-rules-logs/javascript.node.mdx b/platform-includes/llm-rules-logs/javascript.node.mdx
index 87bf2b2bdbb2c..d2af35a702439 100644
--- a/platform-includes/llm-rules-logs/javascript.node.mdx
+++ b/platform-includes/llm-rules-logs/javascript.node.mdx
@@ -3,11 +3,10 @@
 When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
-
 # Logs
 
 - Where logs are used, ensure Sentry is imported using `import * as Sentry from "@sentry/node"`
-- Enable logging in Sentry using `Sentry.init({ _experiments: { enableLogs: true } })`
+- Enable logging in Sentry using `Sentry.init({ enableLogs: true })`
 - Reference the logger using `const { logger } = Sentry`
 - Sentry offers a `consoleLoggingIntegration` that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
@@ -23,10 +22,7 @@ import * as Sentry from "@sentry/node";
 Sentry.init({
   dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
 
-  _experiments: {
-    enableLogs: true,
-  },
-
+  enableLogs: true,
 });
 ```
 
@@ -68,4 +64,5 @@ logger.fatal("Database connection pool exhausted", {
 });
 ```
 ````
+
 </Expandable>
diff --git a/platform-includes/llm-rules-logs/javascript.react.mdx b/platform-includes/llm-rules-logs/javascript.react.mdx
index 8e74806e70f0c..2daf071136de7 100644
--- a/platform-includes/llm-rules-logs/javascript.react.mdx
+++ b/platform-includes/llm-rules-logs/javascript.react.mdx
@@ -3,11 +3,10 @@
 When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
-
 # Logs
 
 - Where logs are used, ensure Sentry is imported using `import * as Sentry from "@sentry/react"`
-- Enable logging in Sentry using `Sentry.init({ _experiments: { enableLogs: true } })`
+- Enable logging in Sentry using `Sentry.init({ enableLogs: true })`
 - Reference the logger using `const { logger } = Sentry`
 - Sentry offers a `consoleLoggingIntegration` that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
@@ -21,10 +20,7 @@ The Sentry initialization needs to be updated to enable the logs feature.
 Sentry.init({
   dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
 
-  _experiments: {
-    enableLogs: true,
-  },
-
+  enableLogs: true,
 });
 ```
 
@@ -66,4 +62,5 @@ logger.fatal("Database connection pool exhausted", {
 });
 ```
 ````
+
 </Expandable>
diff --git a/platform-includes/llm-rules-platform/_default.mdx b/platform-includes/llm-rules-platform/_default.mdx
index 30aecb702dedf..3b31671cbc7de 100644
--- a/platform-includes/llm-rules-platform/_default.mdx
+++ b/platform-includes/llm-rules-platform/_default.mdx
@@ -2,9 +2,8 @@
 
 Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration. When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
-{/* ATTENTION: The rules defined here must match those in the app's onboarding documentation (see: https://github.com/getsentry/sentry/blob/master/static/app/gettingStartedDocs/javascript/javascript.tsx).
-If you make any changes, please update the getting started doc accordingly. */}
-
+{/_ ATTENTION: The rules defined here must match those in the app's onboarding documentation (see: https://github.com/getsentry/sentry/blob/master/static/app/gettingStartedDocs/javascript/javascript.tsx).
+If you make any changes, please update the getting started doc accordingly. _/}
 
 ````markdown {filename:rules.md}
 These examples should be used as guidance when configuring Sentry functionality within a project.
@@ -79,7 +78,7 @@ async function fetchUserData(userId) {
 # Logs
 
 - Where logs are used, ensure Sentry is imported using `import * as Sentry from "@sentry/browser"`
-- Enable logging in Sentry using `Sentry.init({ _experiments: { enableLogs: true } })`
+- Enable logging in Sentry using `Sentry.init({ enableLogs: true })`
 - Reference the logger using `const { logger } = Sentry`
 - Sentry offers a `consoleLoggingIntegration` that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
@@ -93,9 +92,7 @@ import * as Sentry from "@sentry/browser";
 Sentry.init({
   dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
 
-  _experiments: {
-    enableLogs: true,
-  },
+  enableLogs: true,
 });
 ```
 
diff --git a/platform-includes/llm-rules-platform/javascript.nextjs.mdx b/platform-includes/llm-rules-platform/javascript.nextjs.mdx
index 1caf400252669..59af26fbef047 100644
--- a/platform-includes/llm-rules-platform/javascript.nextjs.mdx
+++ b/platform-includes/llm-rules-platform/javascript.nextjs.mdx
@@ -2,8 +2,8 @@
 
 Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration. When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
-{/* ATTENTION: The rules defined here must match those in the app's onboarding documentation (see: https://github.com/getsentry/sentry/blob/master/static/app/gettingStartedDocs/javascript/nextjs.tsx).
-If you make any changes, please update the getting started doc accordingly. */}
+{/_ ATTENTION: The rules defined here must match those in the app's onboarding documentation (see: https://github.com/getsentry/sentry/blob/master/static/app/gettingStartedDocs/javascript/nextjs.tsx).
+If you make any changes, please update the getting started doc accordingly. _/}
 
 ````markdown {filename:rules.md}
 These examples should be used as guidance when configuring Sentry functionality within a project.
@@ -78,7 +78,7 @@ async function fetchUserData(userId) {
 # Logs
 
 - Where logs are used, ensure Sentry is imported using `import * as Sentry from "@sentry/nextjs"`
-- Enable logging in Sentry using `Sentry.init({ _experiments: { enableLogs: true } })`
+- Enable logging in Sentry using `Sentry.init({ enableLogs: true })`
 - Reference the logger using `const { logger } = Sentry`
 - Sentry offers a consoleLoggingIntegration that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
@@ -95,9 +95,7 @@ import * as Sentry from "@sentry/nextjs";
 Sentry.init({
   dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
 
-  _experiments: {
-    enableLogs: true,
-  },
+  enableLogs: true,
 });
 ```
 
@@ -115,7 +113,7 @@ Sentry.init({
 
 ## Logger Examples
 
-`logger.fmt` is a template literal function that should be used to bring variables into the structured logs. 
+`logger.fmt` is a template literal function that should be used to bring variables into the structured logs.
 
 ```javascript
 logger.trace("Starting database connection", { database: "users" });
diff --git a/platform-includes/llm-rules-platform/javascript.node.mdx b/platform-includes/llm-rules-platform/javascript.node.mdx
index 7e9091691bf50..a3a6afe1dff47 100644
--- a/platform-includes/llm-rules-platform/javascript.node.mdx
+++ b/platform-includes/llm-rules-platform/javascript.node.mdx
@@ -2,8 +2,8 @@
 
 Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration. When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
-{/* ATTENTION: The rules defined here must match those in the app's onboarding documentation (see: https://github.com/getsentry/sentry/blob/master/static/app/gettingStartedDocs/node/node.tsx).
-If you make any changes, please update the getting started doc accordingly. */}
+{/_ ATTENTION: The rules defined here must match those in the app's onboarding documentation (see: https://github.com/getsentry/sentry/blob/master/static/app/gettingStartedDocs/node/node.tsx).
+If you make any changes, please update the getting started doc accordingly. _/}
 
 ````markdown {filename:rules.md}
 These examples should be used as guidance when configuring Sentry functionality within a project.
@@ -73,7 +73,7 @@ async function fetchUserData(userId) {
 # Logs
 
 - Where logs are used, ensure they are imported using `import * as Sentry from "@sentry/node"`
-- Enable logging in Sentry using `Sentry.init({ _experiments: { enableLogs: true } })`
+- Enable logging in Sentry using `Sentry.init({ enableLogs: true, })`
 - Reference the logger using `const { logger } = Sentry`
 - Sentry offers a consoleLoggingIntegration that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
@@ -89,9 +89,7 @@ import * as Sentry from "@sentry/node";
 Sentry.init({
   dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
 
-  _experiments: {
-    enableLogs: true,
-  },
+  enableLogs: true,
 });
 ```
 
diff --git a/platform-includes/llm-rules-platform/javascript.react.mdx b/platform-includes/llm-rules-platform/javascript.react.mdx
index c4a25b644b6b6..48630589e1c33 100644
--- a/platform-includes/llm-rules-platform/javascript.react.mdx
+++ b/platform-includes/llm-rules-platform/javascript.react.mdx
@@ -2,8 +2,8 @@
 
 Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration. When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
-{/* ATTENTION: The rules defined here must match those in the app's onboarding documentation (see: https://github.com/getsentry/sentry/blob/master/static/app/gettingStartedDocs/javascript/react.tsx).
-If you make any changes, please update the getting started doc accordingly. */}
+{/_ ATTENTION: The rules defined here must match those in the app's onboarding documentation (see: https://github.com/getsentry/sentry/blob/master/static/app/gettingStartedDocs/javascript/react.tsx).
+If you make any changes, please update the getting started doc accordingly. _/}
 
 ````markdown {filename:rules.md}
 These examples should be used as guidance when configuring Sentry functionality within a project.
@@ -73,7 +73,7 @@ async function fetchUserData(userId) {
 # Logs
 
 - Where logs are used, ensure Sentry is imported using `import * as Sentry from "@sentry/react"`
-- Enable logging in Sentry using `Sentry.init({ _experiments: { enableLogs: true } })`
+- Enable logging in Sentry using `Sentry.init({ enableLogs: true })`
 - Reference the logger using `const { logger } = Sentry`
 - Sentry offers a consoleLoggingIntegration that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
@@ -87,9 +87,7 @@ import * as Sentry from "@sentry/react";
 Sentry.init({
   dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
 
-  _experiments: {
-    enableLogs: true,
-  },
+  enableLogs: true,
 });
 ```