review suggestions

Author: s1gr1d

docs/platforms/javascript/common/install/esm-without-import.mdx

@@ -20,10 +20,12 @@ supported:
 When running your application in ESM mode, you will most likely want to <PlatformLink to="/install/esm">follow the ESM instructions</PlatformLink>. However, if you want to avoid using the `--import` command line option, for example if you have no way of configuring a CLI flag, you can also follow an alternative setup that involves importing the `instrument.mjs` file directly in your application.
 
 <Alert level='warning' title='Restrictions of this installation method'>
-This installation method has a fundamental restriction: It only supports limited performance instrumentation. Only basic `http` instrumentation will work, and no DB or framework-specific instrumentation will be available.
-
-Because of this, we recommend using this only if the `--import` flag is not an option for you.
+  This installation method has fundamental restrictions:
+  - It only supports limited performance instrumentation.
+  - Only basic `http` instrumentation will work.
+  - No DB or framework-specific instrumentation will be available.
 
+  We recommend using this only if the `--import` flag is not an option for you.
 </Alert>
 
 You need to create a file named `instrument.mjs` that imports and initializes Sentry:

docs/platforms/javascript/guides/nuxt/install/cli-import.mdx

@@ -1,28 +1,27 @@
 ---
 title: --import CLI flag (default)
 sidebar_order: 1
-description: "Learn about using the node --import CLI flag."
+description: "Learn how to use the node --import CLI flag."
 ---
 
 ## Understanding the `--import` CLI Flag
 
-The [`--import` CLI flag](https://nodejs.org/api/cli.html#--importmodule) in Node allows you to preload modules before the application starts. This is the default
-way in ESM to load a module before the application starts.
+The [`--import` CLI flag](https://nodejs.org/api/cli.html#--importmodule) in Node is the default way in ESM to preload a module before the application starts.
 If you cannot use the SDK's <PlatformLink to="/install/dynamic-import/">default dynamic import behaviour</PlatformLink>, setting
 this flag is crucial for ensuring proper server-side initialization, as Sentry needs to be initialized before the rest of the application runs.
 
 ## Scenarios where `--import` does not work
 
 - You're not able to add Node CLI flags or environment variables that are scoped to the function runtime
-- As of now, **Netlify** only supports adding scoped environment variables in the paid plan
-- As of now, **Vercel** does not provide an option for scoping environment variables
+- **Netlify** only allows scoped environment variables on its paid plans at this time
+- **Vercel** doesn't currently provide an option for scoping environment variables
 
 If any of those points apply to you, you cannot use the `--import` flag to initialize Sentry on the server-side.
 Check out the guide for using <PlatformLink to="/install/top-level-import/">a top-level import</PlatformLink> or a <PlatformLink to="/install/dynamic-import/">dynamic import</PlatformLink> instead.
 
 ## Initializing Sentry with `--import`
 
-By default, the SDK will add the Sentry server config to the build output (typically `.output/server/sentry.server.config.mjs`).
+By default, the SDK will add the Sentry server config to the build output (typically, `.output/server/sentry.server.config.mjs`).
 
 ### 1. Adding `--import` to `node` command
 
@@ -42,7 +41,6 @@ To make things easier, add a script in the `package.json`:
 ```json {filename:package.json}
 {
   "scripts": {
-    "preview": "NODE_OPTIONS='--import ./server/sentry.server.config.mjs' nuxt preview",
     "start": "node --import ./.output/server/sentry.server.config.mjs .output/server/index.mjs"
   }
 }

docs/platforms/javascript/guides/nuxt/install/dynamic-import.mdx

@@ -24,13 +24,13 @@ export default defineNuxtConfig({
 })
 ```
 
-After setting this, the Sentry Nuxt SDK adds a Rollup plugin which wraps the server entry file with a dynamic `import()`.
+After setting this, the Sentry Nuxt SDK adds some build-time configuration to ensure your app is wrapped with `import()`.
 With this, Sentry can be initialized before all other modules of the application.
 
-The server entry file will look something like this:
+The Nuxt server entry file will look something like this:
 
 ```javascript {filename:.output/server/index.mjs}
-// Note: The file may have some imports and code related to debug IDs
+// Note: The file may have some imports and code, related to debug IDs
 Sentry.init({
   dsn: "..."
 });
@@ -44,7 +44,7 @@ Depending on your setup and which version of Nitro is used, the server-side is s
 The build output **must not** include a regular `import` of the Nitro runtime (e.g. `import './chunks/nitro/nitro.mjs'`).
 See the ([GitHub issue here](https://github.com/getsentry/sentry-javascript/issues/14514)) for more information.
 
-As a temporary workaround, you can add the following overrides to your application:
+As a temporary workaround, you can add the following overrides in your application:
 
 ```json {tabTitle:npm} {filename:package.json}
 "overrides": {
@@ -67,16 +67,14 @@ As a temporary workaround, you can add the following overrides to your applicati
 }
 ```
 
-You can also check out the guide for using the <PlatformLink to="/install/cli-import">CLI flag `--import`</PlatformLink> or <PlatformLink to="/install/top-level-import/">a top-level import</PlatformLink> as this might be a better choice for you.
-
+You can also check out the guide for installing the SDK with a <PlatformLink to="/install/cli-import">CLI flag `--import`</PlatformLink> or a <PlatformLink to="/install/top-level-import/">top-level import</PlatformLink>.
 
 ## Re-exporting serverless handler functions
 
 Sentry automatically detects serverless handler functions in the build output and re-exports them from the server entry file.
 
 By default, Sentry re-exports functions named `handler`, `server`, and `default` exports. This will work in most cases and no other action is required.
-In case your serverless function has another, custom name you can override this with `experimental_entrypointWrappedFunctions`:
-
+If your serverless function has a custom name, you can override it with `experimental_entrypointWrappedFunctions`:
 
 ```javascript {filename: nuxt.config.ts} {7}
 export default defineNuxtConfig({

docs/platforms/javascript/guides/nuxt/install/top-level-import.mdx

@@ -4,20 +4,23 @@ sidebar_order: 2
 description: "Learn about how the Nuxt SDK adds a top-level import to the build output."
 ---
 
-## Understanding top-level `import`
+## Understanding Top-level `import`
 
 Sentry needs to be initialized before the application starts.
 If the default way of adding an <PlatformLink to="/install/cli-import">`--import` CLI flag</PlatformLink> flag does not work for you,
-set up the SDK for adding a top-level `import`. This will import the Sentry server-side config at the top of the server entry file.
-In this scenario, Sentry is not initialized before application startup, but as early as otherwise possible.
+set up the SDK for adding a top-level `import`. This will import the Sentry server-side config at the top of the Nuxt server entry file.
+In this case, Sentry isn’t initialized before the app starts, but is set up as early as possible.
 
 <Alert level='warning' title='Restrictions of this installation method'>
-  This installation method has a fundamental restriction: It only supports limited performance instrumentation. Only basic `http` instrumentation will work, and no DB or framework-specific instrumentation will be available.
+  This installation method has fundamental restrictions:
+  - It only supports limited performance instrumentation.
+  - Only basic `http` instrumentation will work.
+  - No DB or framework-specific instrumentation will be available.
 
-  Because of this, we recommend using this only if the `--import` flag is not an option for you.
+  We recommend using this only if the `--import` flag is not an option for you.
 </Alert>
 
-## Initializing Sentry with a top-level `import`
+## Initializing Sentry With a Top-level `import`
 
 Enable the top-level `import` by setting `autoInjectServerSentry`:
 
@@ -29,11 +32,11 @@ export default defineNuxtConfig({
 })
 ```
 
-By default, the SDK will add the Sentry server config to the build output (typically `.output/server/sentry.server.config.mjs`).
+By default, the SDK will add the Sentry server config to the build output (typically, `.output/server/sentry.server.config.mjs`).
 
-With the top-level `import`, the server entry file will look something like this:
+With the top-level `import`, the Nuxt server entry file will look something like this:
 
 ```javascript {filename:.output/server/index.mjs}
 import './sentry.server.config.mjs';
-// Note: The file may have some imports and code related to debug IDs
+// Note: The file may have some imports and code, related to debug IDs
 ```

docs/platforms/javascript/guides/nuxt/manual-setup.mdx

@@ -127,9 +127,9 @@ dotenv.config();
 
 #### Load Sentry config
 
-Sentry can only be loaded on the server-side if it is explicitly added via `--import`.
+Sentry can only be loaded on the server-side by being explicitly added via `--import`.
 
-Refer to the documentation of using <PlatformLink to="/install/cli-import">`--import` CLI flag</PlatformLink> for setup instructions.
+Check out the <PlatformLink to="/install/cli-import">`--import` CLI flag</PlatformLink> docs for setup instructions.
 
 <Alert level="warning">
   In the beta state of the Nuxt SDK, some features may not work with certain deployment providers. Check the progress on GitHub: [Compatibility with different Deployment Platforms](https://github.com/getsentry/sentry-javascript/issues/14029)