Apply suggestions from code review

Co-authored-by: Katie Byers <[email protected]>

Author: lforst

src/platform-includes/sourcemaps/overview/javascript.mdx

@@ -12,7 +12,7 @@ We've compiled a list of guides on how to upload source maps to Sentry for the m
 
 ### Other Tools
 
-If you're not using one of these tools, we assume you already know how to generate source maps for your toolchain and we recommend you upload them using the <PlatformLink to="/sourcemaps/uploading/cli/">Sentry CLI</PlatformLink>.
+If you're not using one of these tools, we assume you already know how to generate source maps with your toolchain and we recommend you upload them using <PlatformLink to="/sourcemaps/uploading/cli/">Sentry CLI</PlatformLink>.
 
 <PlatformSection notSupported={["node"]}>
 

src/platform-includes/sourcemaps/overview/javascript.remix.mdx

@@ -1,4 +1,4 @@
-## Upload Source Maps for a Svelte Project
+## Upload Source Maps for a Remix Project
 
 Sentry uses [releases](/product/releases/) to match the correct source maps to your events.
 This page is a guide on how to create releases and upload source maps to Sentry when bundling your Remix app.
@@ -11,10 +11,10 @@ Please refer to the [Remix CLI docs](https://remix.run/docs/en/v1/other-api/dev#
 
 ### 2. Create a Release and Upload Source Maps
 
-The Sentry Remix SDK provides an automatic script to create a release and upload source maps after you built your project.
+The Sentry Remix SDK provides a script to automatically create a release and upload source maps after you've built your project.
 Under the hood, it uses the Sentry CLI.
 
-This script requires some configuration that can either be done through a `.sentryclirc` file in the root of your project or through environment variables:
+This script requires some configuration, which can either be done through a `.sentryclirc` file in the root of your project or through environment variables:
 
 <Note>
 
@@ -61,7 +61,7 @@ For more advanced configuration, [use `sentry-cli` directly to upload source map
 
 ### 3. Remove Remix Source Maps
 
-Remix validly discourages the user to have source maps in production. After uploading the maps to Sentry we suggest you delete the `.map` files, here's a simple example in bash:
+Remix validly discourages the user from hosting source maps in production. After uploading the maps to Sentry, we suggest you delete the `.map` files. Here's a simple example in bash:
 
 ```bash
 rm ./public/**/*.map

src/platform-includes/sourcemaps/overview/javascript.svelte.mdx

@@ -53,7 +53,7 @@ export default defineConfig({
       include: "./dist",
 
       // Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/
-      // and needs the `project:releases` and `org:read` scopes
+      // and need `project:releases` and `org:read` scopes
       authToken: process.env.SENTRY_AUTH_TOKEN,
 
       // Optionally uncomment the line below to override automatic release name detection
@@ -65,7 +65,7 @@ export default defineConfig({
 
 ### Other Bundlers
 
-If you're using bundlers other than Vite, check out our general guide on how to <PlatformLink to="/sourcemaps/uploading/">upload source maps</PlatformLink> with them, or refer to their documentation.
+If you're using a bundler other than Vite, check out our general guide on how to <PlatformLink to="/sourcemaps/uploading/">upload source maps</PlatformLink>, or refer to your bundler's documentation.
 
 <Note>
 

src/platform-includes/sourcemaps/primer/javascript.nextjs.mdx

@@ -1,4 +1,4 @@
-To show readable stack traces in your Sentry errors, once configured, the `@sentry/nextjs` SDK will generate and upload source maps automatically.
+`@sentry/nextjs` will generate and upload source maps automatically, in order to enable errors to have readable stacktraces.
 
 To upload source maps, the `@sentry/nextjs` SDK uses the [Sentry Webpack Plugin](https://github.com/getsentry/sentry-webpack-plugin) under the hood. See the [Manual Configuration](../manual-setup/) page and the Sentry [Webpack Plugin documentation](https://github.com/getsentry/sentry-webpack-plugin#cli-configuration) for more details.
 

src/platform-includes/sourcemaps/upload/cli/javascript.mdx

@@ -1,4 +1,4 @@
-When choosing [`sentry-cli`](/product/cli/) as the method to upload your source files, we assume you already know how to generate source maps within your build tool chain.
+If you choose [`sentry-cli`](/product/cli/) as the method to upload your source files, we assume you already know how to generate source maps within your build tool chain.
 
 Sentry uses [releases](/product/releases/) to match the correct uploaded source maps to your events. You can use `sentry-cli` to create releases and upload source maps to Sentry.
 
@@ -9,7 +9,7 @@ To be able to match Sentry errors with the correct release, you must provide a `
 ```javascript
 Sentry.init({
   // Make sure this value is identical to the name you give the release that you
-  // will create below using Sentry CLI
+  // create below using Sentry CLI
   release: "<release_name>",
 });
 ```
@@ -65,7 +65,7 @@ You can verify your uploaded artifacts by navigating to **[Project] > Project Se
 
 </Note>
 
-Until now, the release is in a draft state (“_unreleased_”). Once all source maps have been uploaded and your app has been published successfully, finalize the release with the following command:
+At this point, the release is in a draft state (“_unreleased_”). Once all source maps have been uploaded and your app has been published successfully, finalize the release with the following command:
 
 ```bash
 sentry-cli releases finalize <release_name>

src/platform-includes/sourcemaps/upload/esbuild/javascript.mdx

@@ -12,7 +12,7 @@ yarn add @sentry/esbuild-plugin --dev
 
 ## Configure
 
-Learn more about the configuration of the plugin using our [Sentry esbuild Plugin documentation](https://github.com/getsentry/sentry-javascript-bundler-plugins/tree/main/packages/esbuild-plugin).
+Learn more about configuring the plugin in our [Sentry esbuild Plugin documentation](https://github.com/getsentry/sentry-javascript-bundler-plugins/tree/main/packages/esbuild-plugin).
 
 Example:
 
@@ -34,7 +34,7 @@ require("esbuild").build({
       include: "./dist",
 
       // Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/
-      // and needs the `project:releases` and `org:read` scopes
+      // and need `project:releases` and `org:read` scopes
       authToken: process.env.SENTRY_AUTH_TOKEN,
 
       // Optionally uncomment the line below to override automatic release name detection

src/platform-includes/sourcemaps/upload/primer/javascript.mdx

@@ -1,4 +1,4 @@
-We provide guides on how to upload source maps to Sentry for the most popular JavaScript build tools.
+We provide guides on uploading source maps to Sentry for the most popular JavaScript build tools.
 Pick one from the list below to learn more.
 
 <PlatformSection notSupported={["node"]}>

src/platform-includes/sourcemaps/upload/rollup/javascript.mdx

@@ -13,7 +13,7 @@ yarn add @sentry/rollup-plugin --dev
 
 ## Configuration
 
-Learn more about the configuration of the plugin using our [Sentry Rollup Plugin documentation](https://github.com/getsentry/sentry-javascript-bundler-plugins/tree/main/packages/rollup-plugin).
+Learn more about configuring the plugin in our [Sentry Rollup Plugin documentation](https://github.com/getsentry/sentry-javascript-bundler-plugins/tree/main/packages/rollup-plugin).
 
 Example:
 
@@ -32,7 +32,7 @@ export default {
       include: "./out",
 
       // Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/
-      // and needs the `project:releases` and `org:read` scopes
+      // and need `project:releases` and `org:read` scopes
       authToken: process.env.SENTRY_AUTH_TOKEN,
 
       // Optionally uncomment the line below to override automatic release name detection

src/platform-includes/sourcemaps/upload/systemjs/javascript.mdx

@@ -1,5 +1,5 @@
 Sentry uses [releases](/product/releases/) to match the correct source maps to your events.
-If you're using SystemJS to bundle your project, your should configure SystemJS to generate source maps and use Sentry CLI to create the release and upload source maps.
+If you're using SystemJS to bundle your project, your should configure SystemJS to generate source maps and use Sentry CLI to create the release and upload the source maps.
 
 ## 1. Update SDK Options
 
@@ -8,7 +8,7 @@ To be able to match Sentry errors with the correct release, you must provide a `
 ```javascript
 Sentry.init({
   // Make sure this value is identical to the name you give the release that you
-  // will create below using Sentry CLI
+  // create below using Sentry CLI
   release: "<release_name>",
 });
 ```
@@ -35,7 +35,7 @@ This example configuration will inline your original, un-transformed source code
 
 <Note>
 
-You can find instructions on how to install Sentry CLI here: https://docs.sentry.io/product/cli/installation/
+You can find installation instructions for Sentry CLI here: https://docs.sentry.io/product/cli/installation/
 
 For more info on Sentry CLI configuration visit the [Sentry CLI configuration docs](/product/cli/configuration/).
 
@@ -78,11 +78,11 @@ sentry-cli releases files <release_name> upload-sourcemaps /path/to/files
 
 <Note>
 
-You can verify your uploaded artifacts by navigating to **[Project] > Project Settings (gear icon in top right corner) > Source Maps** on Sentry.
+You can verify that your upload was successful by navigating to **[Project] > Project Settings (gear icon in top right corner) > Source Maps** on Sentry.
 
 </Note>
 
-Until now, the release is in a draft state (“_unreleased_”). Once all source maps have been uploaded, and your app has been published successfully, finalize the release with the following command:
+At this point, the release is in a draft state (“_unreleased_”). Once all source maps have been uploaded, and your app has been published successfully, finalize the release with the following command:
 
 ```bash
 sentry-cli releases finalize <release_name>

src/platform-includes/sourcemaps/upload/typescript/javascript.mdx

@@ -1,6 +1,6 @@
 <Note>
 
-This guide is only applicable if you're using `tsc` to compile your project. If you use another tool (such as, Webpack) in combination with TypeScript, you'll most likely want to follow that guide instead.
+This guide is only applicable if you're using `tsc` to compile your project. If you use another tool (such as Webpack) in combination with TypeScript, you'll most likely want to follow that guide instead.
 
 </Note>
 
@@ -17,7 +17,7 @@ First, configure the TypeScript compiler to output source maps:
     "sourceMap": true,
     "inlineSources": true,
 
-    // Configure the `sourceRoot`` property as / to strip the build path prefix from
+    // Set `sourceRoot` to  `/` to strip the build path prefix from
     // generated source code references. This allows Sentry to match source files
     // relative to your source root folder.
     "sourceRoot": "/"
@@ -32,7 +32,7 @@ To be able to match Sentry errors with the correct release, you must provide a `
 ```javascript
 Sentry.init({
   // Make sure this value is identical to the name you give the release that you
-  // will create below using Sentry CLI
+  // create below using Sentry CLI
   release: "<release_name>",
 });
 ```
@@ -41,7 +41,7 @@ Sentry.init({
 
 <Note>
 
-You can find instructions on how to install Sentry CLI here: https://docs.sentry.io/product/cli/installation/
+You can find installation instructions for Sentry CLI here: https://docs.sentry.io/product/cli/installation/
 
 For more info on Sentry CLI configuration visit the [Sentry CLI configuration docs](/product/cli/configuration/).
 
@@ -84,11 +84,11 @@ sentry-cli releases files <release_name> upload-sourcemaps /path/to/files
 
 <Note>
 
-You can verify your uploaded artifacts by navigating to **[Project] > Project Settings (gear icon in top right corner) > Source Maps** on Sentry.
+You can verify that your upload was successful by navigating to **[Project] > Project Settings (gear icon in top right corner) > Source Maps** on Sentry.
 
 </Note>
 
-Until now, the release is in a draft state (“_unreleased_”). Once all source maps have been uploaded and your app has been published successfully, finalize the release with the following command:
+At this point, the release is in a draft state (“_unreleased_”). Once all source maps have been uploaded and your app has been published successfully, finalize the release with the following command:
 
 ```bash
 sentry-cli releases finalize <release_name>

src/platform-includes/sourcemaps/upload/uglifyjs/javascript.mdx

@@ -1,5 +1,5 @@
 Sentry uses [releases](/product/releases/) to match the correct source maps to your events.
-If you're using UglifyJS to transpile your project you should configure UglifyJS to generate source maps and use Sentry CLI to create the release and upload source maps.
+If you're using UglifyJS to transpile your project you should configure UglifyJS to generate source maps and use Sentry CLI to create the release and upload the source maps.
 
 ## 1. Update SDK Options
 
@@ -8,7 +8,7 @@ To be able to match Sentry errors with the correct release, you must provide a `
 ```javascript
 Sentry.init({
   // Make sure this value is identical to the name you give the release that you
-  // will create below using Sentry CLI
+  // create below using Sentry CLI
   release: "<release_name>",
 });
 ```
@@ -27,7 +27,7 @@ uglifyjs app.js \
 
 <Note>
 
-You can find instructions on how to install Sentry CLI here: https://docs.sentry.io/product/cli/installation/
+You can find installation instructions for Sentry CLI here: https://docs.sentry.io/product/cli/installation/
 
 For more info on Sentry CLI configuration visit the [Sentry CLI configuration docs](/product/cli/configuration/).
 
@@ -74,7 +74,7 @@ You can verify your uploaded artifacts by navigating to **[Project] > Project Se
 
 </Note>
 
-Until now, the release is in a draft state (“_unreleased_”). Once all source maps have been uploaded, and your app has been published successfully, finalize the release with the following command:
+At this point, the release is in a draft state (“_unreleased_”). Once all source maps have been uploaded, and your app has been published successfully, finalize the release with the following command:
 
 ```bash
 sentry-cli releases finalize <release_name>

src/platform-includes/sourcemaps/upload/vite/javascript.mdx

@@ -12,7 +12,7 @@ yarn add @sentry/vite-plugin --dev
 
 ## Configuration
 
-Learn more about the configuration of the plugin using our [Sentry Vite Plugin documentation](https://github.com/getsentry/sentry-javascript-bundler-plugins/tree/main/packages/vite-plugin).
+Learn more about configuring the plugin in our [Sentry Vite Plugin documentation](https://github.com/getsentry/sentry-javascript-bundler-plugins/tree/main/packages/vite-plugin).
 
 Example:
 

src/platform-includes/sourcemaps/upload/webpack/javascript.mdx

@@ -13,7 +13,7 @@ yarn add --dev @sentry/webpack-plugin
 
 ## Configuration
 
-Learn more about the configuration of the plugin using our [Sentry Webpack Plugin documentation](https://github.com/getsentry/sentry-webpack-plugin).
+Learn more about configuring the plugin in our [Sentry Webpack Plugin documentation](https://github.com/getsentry/sentry-webpack-plugin).
 
 Example: