review suggestions

Author: s1gr1d

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

@@ -7,25 +7,25 @@ description: "Learn about using 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 flag is crucial for ensuring proper server-side initialization, as Sentry needs to be initialized before the rest of the application runs.
+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 are not able to add Node CLI flags or environment variables that are scoped to the function runtime
+- 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
 
 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/dynamic-import/">dynamic import</PlatformLink> as this might be a better choice for you.
+Check out the guide for using <PlatformLink to="/install/dynamic-import/">dynamic import</PlatformLink> instead.
 
 ## Initializing Sentry with `--import`
 
 To successfully use the `--import` flag, follow these steps:
 
 ### 1. Disable Dynamic Import
 
-First, you have to first disable the dynamic import.
-This can be done by setting `dynamicImportForServerEntry` to `false`:
+First, disable the dynamic import by setting `dynamicImportForServerEntry` to `false`:
 
 ```javascript {filename: nuxt.config.ts} {5}
 export default defineNuxtConfig({

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

@@ -8,8 +8,25 @@ description: "Learn about how the Nuxt SDK leverages dynamic input() in the buil
 
 The `import()` expression (also called "dynamic import") allows conditional and flexible module loading in ESM.
 For the Sentry Nuxt SDK, it provides an approach to initialize server-side configuration before application startup.
+This early initialization is required to set up the SDK's instrumentation of various libraries correctly.
 
-## Scenarios where `import()` does not work
+## Initializing Sentry with Dynamic `import()`
+
+By default, the Sentry Nuxt SDK includes a Rollup plugin which wraps the server entry file with a dynamic `import()`.
+With this, Sentry can be initialized before all other modules of the application.
+
+The server entry file will look something like this:
+
+```javascript {filename:.output/server/index.mjs}
+// Note: file may have some imports and code related to debug IDs
+Sentry.init({
+  dsn: "..."
+});
+
+import('./chunks/nitro/nitro.mjs').then(function (n) { return n.r; });
+```
+
+## Scenarios where `import()` doesn't work
 
 We are currently investigating an issue where the server-side is not correctly initialized with a recent update of Nitro (the server-side toolkit in Nuxt).
 We are working on figuring this out ([see issue here](https://github.com/getsentry/sentry-javascript/issues/14514)). As a temporary workaround, you can add the following overrides to your application:
@@ -38,22 +55,6 @@ We are working on figuring this out ([see issue here](https://github.com/getsent
 You can also check out the guide for using the <PlatformLink to="/install/cli-import//">CLI flag `--import`</PlatformLink> as this might be a better choice for you.
 
 
-## Initializing Sentry with Dynamic `import()`
-
-By default, the Sentry Nuxt SDK includes a Rollup plugin which wraps the server entry file with a dynamic `import()`.
-With this, Sentry can be initialized before all other modules of the application.
-
-The server entry file will look something like this:
-
-```javascript {filename:.output/server/index.mjs}
-// Note: file may have some imports and code related to debug IDs
-Sentry.init({
-  dsn: "..."
-});
-
-import('./chunks/nitro/nitro.mjs').then(function (n) { return n.r; });
-```
-
 ## Re-exporting serverless handler functions
 
 Sentry automatically detects serverless handler functions in the build output and re-exports them from the server entry file.
@@ -62,7 +63,7 @@ By default, Sentry re-exports functions named `handler`, `server`, and `default`
 In case your serverless function has another, custom name you can override this with `entrypointWrappedFunctions`:
 
 
-```javascript {filename: nuxt.config.ts} {6}
+```javascript {filename: nuxt.config.ts} {7}
 export default defineNuxtConfig({
   modules: ["@sentry/nuxt/module"],
 
@@ -77,3 +78,5 @@ export default defineNuxtConfig({
 
 
 
+
+

docs/platforms/javascript/guides/nuxt/install/index.mdx

@@ -4,12 +4,11 @@ sidebar_order: 1.5
 description: "Review our alternate installation methods."
 ---
 
-<PageGrid />
+
 
 Nuxt uses ES Modules for server-side builds, which requires Sentry to register Node [customization hooks](https://nodejs.org/api/module.html#customization-hooks).
 Those customization hooks need to be registered before the rest of the application.
 
 To be able to run Sentry before the rest of the application and fully monitor the server-side, Sentry can be initialized using one of those two approaches:
 
-- Dynamically import server code after initializing Sentry (default)
-- Preload Sentry configuration with the Node `--import` CLI flag
+<PageGrid />