Alex feedback

Author: inventarSarah

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

@@ -8,13 +8,13 @@ The wizard then guides you through the setup process, asking you to enable addit
 
 <Expandable title="Want to learn more about these features?">
 
-- [**Error Monitoring**](/product/issues) (always enabled): Automatically report errors,
+- [**Issues**](/product/issues) (always enabled): Sentry's core error monitoring product that automatically reports 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/):
+- [**Session Replay**](/product/explore/session-replay/web):
   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.
@@ -25,10 +25,10 @@ This guide assumes that you enable all features and allow the wizard to create a
 
 <Expandable title="What does the installation wizard change inside your application?">
 
-- 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`)
-- Add an example page and route to your application to help verify your Sentry setup
+- Creates config files with the default `Sentry.init()` calls for all runtimes (Node.js, Browser, and Edge)
+- Adds a Next.js instrumentation hook to your project (`instrumentation.ts`)
+- Creates or updates your Next.js config with the default Sentry settings
+- Creates `.sentryclirc` with an auth token to upload source maps (this file is automatically added to `.gitignore`)
+- Adds an example page and route to your application to help verify your Sentry setup
 
 </Expandable>

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

@@ -1,6 +1,6 @@
 ## Next Steps
 
-You should now have integrated Sentry into your Next.js application and should already be sending error and performance data to your Sentry project.
+At this point, you should have integrated Sentry into your Next.js application and should already be sending error and performance data to your Sentry project.
 
 Now's a good time to customize your setup and look into more advanced topics.
 Our next recommended steps for you are:

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

@@ -2,15 +2,15 @@
 
 <Expandable level="warning" 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.
+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 from your frontend. Other than that, your dev server 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.
+If you haven't tested your configuration 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` in your browser.
+1. Open the example page `/sentry-example-page` in your browser. For most Next.js applications, this will be at localhost.
 2. Click the "Throw error" button. This triggers two errors:
    - a frontend error
    - an error within the API route