diff --git a/platform-includes/getting-started-primer/javascript.nextjs.mdx b/platform-includes/getting-started-primer/javascript.nextjs.mdx
index 5e8e989610b84..b17d52df89472 100644
--- a/platform-includes/getting-started-primer/javascript.nextjs.mdx
+++ b/platform-includes/getting-started-primer/javascript.nextjs.mdx
@@ -9,8 +9,16 @@ Features:
 
 <Note>
 
-`next dev --turbo` is not supported while Turbopack is in beta. Running your devserver with Turbopack will cause the Sentry Next.js SDK not to be loaded in the browser. Data from serverside instrumentation will also be inaccurate or incomplete.
+The Sentry SDK does not fully support `next dev --turbo` while Turbopack does not ship all the features required to run Sentry.
+
+Currently, when you run your devserver with Turbopack, the Sentry Next.js SDK will not be loaded in the browser.
+Keep this in mind when configuring the SDK.
+
+Note that this only affects the devserver.
+The Sentry SDK will run without issues when you do a production build, even if you develop locally with Turbopack.
 
 To support the SDK in the browser with Turbopack, [follow the feature request for client-side instrumentation in the Next.js repository](https://github.com/vercel/next.js/discussions/69294).
 
+You can track Sentry's Turbopack support in the [GitHub Issue in the Sentry SDK repository](https://github.com/getsentry/sentry-javascript/issues/8105).
+
 </Note>