updated structure and put more content into expandables. Testing out some ideas.

Author: inventarSarah

docs/platforms/javascript/common/index.mdx

@@ -37,16 +37,7 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 <PlatformSection supported={["javascript.nextjs"]}>
 
-## Step 1: Choose Your Sentry Features (Optional)
-
-During setup, you'll have the option to enable specific Sentry features for your application.
-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.
-- [**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.
-
-## Step 2: Install
+## Step 1: Install
 
 </PlatformSection>
 

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

@@ -4,15 +4,30 @@ To install Sentry using the installation wizard, run the following command withi
 npx @sentry/wizard@latest -i nextjs
 ```
 
-The wizard starts guiding you through the setup process, which also includes enabling the Sentry features listed above.
+The wizard then guides you through the setup process, asking you to enable additional (optional) Sentry features for your application beyond error monitoring.
+
+<Expandable title="Want to learn a bit more about these features?">
+
+- [**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.
+- [**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.
+
+</Expandable>
 
 <Alert level="warning" title="Important">
 
-This guide assumes you enable all Sentry features during the wizard setup and allow it to create an example page and route. If you make different choices, you can still follow along, but you may need to make adjustments as you proceed.
+This guide assumes that you enable all features and allow the wizard to create an example page and route. Keep this in mind as you proceed.
 
 </Alert>
 
-You can always add or remove config options manually later if needed. Though, the earlier you set these up, the better.
+You can always add or remove features manually later if needed. Though, the earlier you set these up, the better.
 
 <Expandable title="What does the installation wizard change inside your application?">
 

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

@@ -1,7 +1 @@
-<Expandable title="Are you developing with Turbopack?">
 
-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).
-
-</Expandable>

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

@@ -1,30 +1,42 @@
-## Step 3: Verify Your Setup
+## Step 2: Verify Your Setup
 
-Let's confirm that Sentry is working properly and sending data to your Sentry project by using the example page and route created by the installation wizard.
+<Expandable title="Are you developing with Turbopack?">
 
-1. Open the example page at [http://localhost:3000/sentry-example-page](http://localhost:3000/sentry-example-page)
+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).
+
+</Expandable>
+
+If you haven't tested your setup yet, let's do it now. You can confirm that Sentry is working properly and sending data to your Sentry project by using the example page and route created by the installation wizard.
+
+1. Open the example page `/sentry-example-page`.
 2. Click the "Throw error" button. This triggers two errors:
    - a frontend error
    - an error within the API route
 
-Sentry will capture both of these errors for you. Additionally, the button click starts a performance trace to measure the time it takes for the API request to complete.
+Sentry captures both of these errors for you. Additionally, the button click starts a performance trace to measure the time it takes for the API request to complete.
 
 <Alert level="success" title="Tip">
 
-Make sure to explore the example files' code in your project to understand what's happening after your button click.
+Don't forget to explore the example files' code in your project to understand what's happening after your button click.
 
 </Alert>
 
 ### View Captured Data in Sentry
 
-Now head over to your Sentry project on [Sentry.io](https://sentry.io) to view the collected data (it takes a couple of moments for the data to appear).
+Now, head over to your project on [Sentry.io](https://sentry.io) to view the collected data (it takes a couple of moments for the data to appear).
 
 <Alert level="warning" title="Important">
 
 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>
 
+<Expandable title="Need help locating the captured errors in your Sentry project?">
+
 1. Open the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues) page and select an error from the issues list to view the full details and context of this error. For an interactive UI walkthrough, click [here](/product/sentry-basics/integrate-frontend/generate-first-error/#ui-walkthrough).
 2. Open the [**Traces**](https://sentry.io/orgredirect/organizations/:orgslug/traces) page and select a trace to reveal more information about each span, its duration, and any errors. For an interactive UI walkthrough, click [here](/product/sentry-basics/distributed-tracing/generate-first-error/#ui-walkthrough).
 3. Open the [**Replays**](https://sentry.io/orgredirect/organizations/:orgslug/replays) page and select an entry from the list to get a detailed view where you can replay the interaction and get more information to help you troubleshoot.
+
+</Expandable>