integrate pr feedback

Author: inventarSarah

docs/platforms/javascript/common/index.mdx

@@ -43,7 +43,6 @@ During setup, you'll have the option to enable specific Sentry features for your
 Here's a quick overview of what's what:
 
 - [**Error Monitoring**](/product/issues) (always enabled): Automatically report errors, uncaught exceptions, and unhandled rejections. If you have something that looks like an exception, Sentry can capture it.
-- **Tunneling**: Route browser requests to Sentry through a Next.js rewrite to bypass ad-blockers that might interfere with Sentry's data collection.
 - [**Tracing**](/product/tracing): Track software performance while seeing the impact of errors across multiple systems. For example, distributed tracing allows you to follow a request from the frontend to the backend and back.
 - [**Session Replay**](/product/explore/session-replay/web/getting-started/): Get to the root cause of an issue faster by viewing a video-like reproduction of what was happening in the user's browser before, during, and after the problem.
 

platform-includes/getting-started-install/javascript.nextjs.mdx

@@ -16,7 +16,7 @@ You can always add or remove config options manually later if needed. Though, th
 
 <Expandable title="What does the installation wizard change inside your application?">
 
-- Create config files with the default `Sentry.init()` calls for each runtime (node, browser, edge)
+- Create config files with the default `Sentry.init()` calls for all runtimes (Node.js, Browser, and Edge)
 - Add a Next.js instrumentation hook to your project (`instrumentation.ts`)
 - Create or update your Next.js config with the default Sentry settings
 - Create `.sentryclirc` with an auth token to upload source maps (this file is automatically added to `.gitignore`)

platform-includes/getting-started-next-steps/javascript.nextjs.mdx

@@ -5,10 +5,10 @@ You should now have integrated Sentry into your Next.js application and should a
 Now's a good time to customize your setup and look into more advanced topics.
 Our next recommended steps for you are:
 
-- Learn more about our [Vercel integration](/organization/integrations/deployment/vercel/)
-- Continue to [customize your configuration](/platforms/javascript/guides/nextjs/configuration/)
 - Learn how to [manually capture errors](/platforms/javascript/guides/nextjs/usage/)
+- Continue to [customize your configuration](/platforms/javascript/guides/nextjs/configuration/)
 - Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts
+- Learn more about our [Vercel integration](/organization/integrations/deployment/vercel/)
 
 <Expandable permalink={false} title="Did you experience any issues with this guide?">
 

platform-includes/getting-started-primer/javascript.nextjs.mdx

@@ -1,8 +1,6 @@
 <Expandable title="Are you developing with Turbopack?">
 
-The Sentry SDK doesn't fully support `next dev --turbo` as Turbopack is still under development.
-
-However, Sentry will work fine in your production builds.
+The Sentry SDK doesn't fully support `next dev --turbo` as Turbopack is still under development. This means that the Sentry SDK will not capture any data for the frontend. Other than that, your devserver should be fully operational.
 
 Check the latest information on [Sentry's support for Turbopack on GitHub](https://github.com/getsentry/sentry-javascript/issues/8105).
 

platform-includes/getting-started-verify/javascript.nextjs.mdx

@@ -21,7 +21,7 @@ Now head over to your Sentry project on [Sentry.io](https://sentry.io) to view t
 
 <Alert level="warning" title="Important">
 
-Errors triggered from within your browser's developer tools are sandboxed, so they will not trigger Sentry's error monitoring.
+Errors triggered from within your browser's developer tools (i.e., the browser console) are sandboxed, so they will not trigger Sentry's error monitoring.
 
 </Alert>