PR feedback

Author: inventarSarah

docs/platforms/javascript/guides/nestjs/install/commonjs.mdx

@@ -11,7 +11,7 @@ supported:
   [installation methods](../).
 </Alert>
 
-Most node applications today are either written in CommonJS (CJS), or compiled to CJS before running them.
-CommonJS uses `require()` to load modules.
+Most node applications today are either written in or compiled to CommonJS (CJS), which uses `require()` to load modules.
+Nest.js, by default, transpiles your TypeScript code into CommonJS.
 
-You can find installation instructions for CommonJS in the SDK's <PlatformLink to="/">Quick Start guide</PlatformLink>.
+You can follow the installation instructions in the SDK's <PlatformLink to="/">Quick Start guide</PlatformLink>.

docs/platforms/javascript/guides/nestjs/install/esm-without-import.mdx

@@ -1,5 +1,5 @@
 ---
-title: ESM without CLI Flag
+title: ESM Without CLI Flag
 sidebar_order: 11
 description: "Learn about running Sentry in an ESM application, without the --import flag."
 supported:
@@ -17,13 +17,13 @@ When running your application in ESM mode, you will most likely want to <Platfor
 
 This installation method has the fundamental restriction that only native Node.js APIs can be instrumented (such as `fetch` and the `http` module).
 
-As a result, the Sentry SDK will not capture data from database calls, queues, ORMs, third-party libraries, or other framework-specific data.
+As a result, the Sentry SDK will **not** capture data from database calls, queues, ORMs, third-party libraries, or other framework-specific data.
 
 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:
+**Step 1:** Create a file named `instrument.mjs` that imports and initializes Sentry:
 
 ```javascript {tabTitle:ESM} {filename: instrument.mjs}
 import * as Sentry from "@sentry/nestjs";
@@ -38,14 +38,14 @@ Sentry.init({
 });
 ```
 
-You need to import the `instrument.mjs` file before importing any other modules in your application. This is necessary to ensure that Sentry can automatically instrument all modules in your application:
+**Step 2:** Import the `instrument.mjs` file before importing any other modules in your in the `main.ts` file of your application. This ensures that Sentry can automatically instrument all modules in your application:
 
-```javascript {filename: main.js}
+```javascript {filename: main.ts}
 // Import this first!
 import "./instrument";
 
 // Now import other modules
-import http from "http";
-
+import { NestFactory } from "@nestjs/core";
+// ...
 // Your application code goes here
 ```

docs/platforms/javascript/guides/nestjs/install/esm.mdx

@@ -11,9 +11,9 @@ supported:
   [installation methods](../).
 </Alert>
 
-When running your application in ESM mode, you can't use `require()` to load modules. Instead, you have to use the `--import` command line options to load a module before the application starts.
+When running your application in [ECMAScript Modules](https://nodejs.org/api/esm.html#introduction) (ESM) mode, you can't use `require()` to load modules. Instead, you have to use the `--import` command line options to load a module before the application starts.
 
-You need to create a file named `instrument.mjs` that imports and initializes Sentry:
+**Step 1:** Create a file named `instrument.mjs` that imports and initializes Sentry:
 
 ```javascript {tabTitle:ESM} {filename: instrument.mjs}
 import * as Sentry from "@sentry/nestjs";
@@ -28,24 +28,24 @@ Sentry.init({
 });
 ```
 
-Adjust the Node.js call for your application to use the [--import](https://nodejs.org/api/cli.html#--importmodule) parameter and point it at `instrument.mjs`, which contains your `Sentry.init()` code:
+**Step 2:** Adjust your application's start command to use the [--import](https://nodejs.org/api/cli.html#--importmodule) parameter:
 
 ```bash
 # Note: This is only available for Node v18.19.0 onwards.
-node --import ./instrument.mjs dist/main.js
+"start": "--import ./instrument.mjs nest start"
 ```
 
-If it is not possible for you to pass the `--import` flag to the Node.js binary, you can alternatively use the `NODE_OPTIONS` environment variable as follows:
+If you can't pass the `--import` flag to the Node.js binary, you can alternatively use the `NODE_OPTIONS` environment variable as follows:
 
 ```bash
 NODE_OPTIONS="--import ./instrument.mjs" npm run start
 ```
 
-We do not support ESM in Node versions before 18.19.0.
+<Alert>We do not support ESM in Node versions before 18.19.0.</Alert>
 
-## Troubleshooting instrumentation
+## Troubleshooting ESM Instrumentation
 
-By default, all packages are wrapped under the hood by
+By default, all packages are automatically wrapped by
 [import-in-the-middle](https://www.npmjs.com/package/import-in-the-middle) to
 aid instrumenting them.
 

docs/platforms/javascript/guides/nestjs/install/esm__v8.x.mdx

@@ -12,9 +12,9 @@ noindex: true
   [installation methods](../).
 </Alert>
 
-When running your application in ESM mode, you can't use `require()` to load modules. Instead, you have to use the `--import` command line options to load a module before the application starts.
+When running your application in [ECMAScript Modules](https://nodejs.org/api/esm.html#introduction) (ESM) mode, you can't use `require()` to load modules. Instead, you have to use the `--import` command line options to load a module before the application starts.
 
-You need to create a file named `instrument.mjs` that imports and initializes Sentry:
+**Step 1:** Create a file named `instrument.mjs` that imports and initializes Sentry:
 
 ```javascript {tabTitle:ESM} {filename: instrument.mjs}
 import * as Sentry from "@sentry/nestjs";
@@ -29,24 +29,24 @@ Sentry.init({
 });
 ```
 
-Adjust the Node.js call for your application to use the [--import](https://nodejs.org/api/cli.html#--importmodule) parameter and point it at `instrument.js`, which contains your `Sentry.init()` code:
+**Step 2:** Adjust your application's start command to use the [--import](https://nodejs.org/api/cli.html#--importmodule) parameter:
 
 ```bash
 # Note: This is only available for Node v18.19.0 onwards.
-node --import ./instrument.mjs dist/main.js
+"start": "--import ./instrument.mjs nest start"
 ```
 
-If it is not possible for you to pass the `--import` flag to the Node.js binary, you can alternatively use the `NODE_OPTIONS` environment variable as follows:
+If you can't pass the `--import` flag to the Node.js binary, you can alternatively use the `NODE_OPTIONS` environment variable as follows:
 
 ```bash
 NODE_OPTIONS="--import ./instrument.mjs" npm run start
 ```
 
-We do not support ESM in Node versions before 18.19.0.
+<Alert>We do not support ESM in Node versions before 18.19.0.</Alert>
 
 ## Troubleshooting instrumentation
 
-By default, all packages are wrapped under the hood by
+By default, all packages are automatically wrapped by
 [import-in-the-middle](https://www.npmjs.com/package/import-in-the-middle) to
 aid instrumenting them.
 

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

@@ -1,7 +1,7 @@
 ---
 title: Installation Methods
 sidebar_order: 1
-description: "Review our alternate installation methods."
+description: "Review our alternate installation methods for Sentry using Nest.js."
 supported:
   - javascript.nestjs
 ---
@@ -11,24 +11,20 @@ supported:
 ## How To Decide Which Installation Method To Use
 
 Most node applications today are either written in CommonJS (CJS), or compiled to CJS before running them.
-CommonJS uses `require()` to load modules. Our recommended installation method when using CommonJS is to require the `instrument.js` file at the top of your application. However, if your application is run in ESM mode, this will not work. In this case, you can follow the [ESM docs](./esm).
+CommonJS uses `require()` to load modules. Our recommended installation method when using CommonJS is to require the `instrument.js` file at the top of your application. However, if your application is run in ESM mode, this will not work, in which case, you can follow the [ESM docs](./esm).
 
 Note that even if your application is written in ESM (using `import`), it may still be _run_ in CJS. In this case, you should follow the [CommonJS instructions](./commonjs).
 
 ### My application uses the default Nest.js setup
 
 Nest.js transpiles to CJS by default, so you should follow the [CommonJS installation instructions](./commonjs). Keep reading if you have a more customized application or build setup.
 
-### My application is in TypeScript
-
-If you're using TypeScript, your application is likely compiled to CommonJS before running it. In this case, you should follow the [CommonJS instructions](./commonjs).
-
 ### My application uses `require`
 
-If you are using `require()` in your application, you should follow the [CommonJS instructions](./commonjs).
+If you're using `require()` in your application, you should follow the [CommonJS instructions](./commonjs).
 
 ### My application uses `import`
 
-If you are using `import` in your application, your installation method depends on how your application is _run_. If you compile your application (e.g. into a `/dist` folder or similar) before running this, you need to check how the compiled code looks like. Is the compiled code using `require`? Then you should follow the [CommonJS instructions](./commonjs). If the compiled code is using `import`, you should follow the [ESM instructions](./esm).
+If you're using `import` in your application, your installation method depends on how your application is _run_. If you compile your application (for example, into a `/dist` folder or similar) before running it, you need to check how the compiled code looks like. Is the compiled code using `require`? Then you should follow the [CommonJS instructions](./commonjs). If the compiled code is using `import`, you should follow the [ESM instructions](./esm).
 
 If you do not compile your code, you'll need to follow the [ESM instructions](./esm).