Apply suggestions from code review

Author: mydea

src/platform-includes/getting-started-config/javascript.angular.mdx

@@ -25,7 +25,7 @@ Sentry.init({
   // of transactions for performance monitoring.
   // We recommend adjusting this value in production
   tracesSampleRate: 1.0,
-  
+
   // Capture Replay for 10% of all sessions,
   // plus for 100% of sessions with an error
   replaysSessionSampleRate: 0.1,

src/platform-includes/getting-started-config/javascript.ember.mdx

@@ -16,7 +16,7 @@ Sentry.init({
   // of transactions for performance monitoring.
   // We recommend adjusting this value in production,
   tracesSampleRate: 1.0,
-  
+
   // Capture Replay for 10% of all sessions,
   // plus for 100% of sessions with an error
   replaysSessionSampleRate: 0.1,

src/platform-includes/getting-started-config/javascript.mdx

@@ -8,7 +8,7 @@ Sentry.init({
 
   // Alternatively, use `process.env.npm_package_version` for a dynamic release version
   // if your build tool supports it.
-  release: '[email protected]',
+  release: "[email protected]",
   integrations: [new Sentry.BrowserTracing(), new Sentry.Replay()],
 
   // Set tracesSampleRate to 1.0 to capture 100%

src/platform-includes/getting-started-config/javascript.react.mdx

@@ -12,7 +12,7 @@ Sentry.init({
   // of transactions for performance monitoring.
   // We recommend adjusting this value in production
   tracesSampleRate: 1.0,
-  
+
   // Capture Replay for 10% of all sessions,
   // plus for 100% of sessions with an error
   replaysSessionSampleRate: 0.1,

src/platform-includes/getting-started-config/javascript.remix.mdx

@@ -2,7 +2,7 @@ To use this SDK, initialize Sentry in your Remix entry points for both the clien
 
 Create two files in the root directory of your project, `entry.client.tsx` and `entry.server.tsx` (if they don't exist yet). In these files, add your initialization code for the client-side SDK and server-side SDK, respectively.
 
-The two configuration types are mostly the same, except that some configuration, like the one for Session Replay, only works in `entry.client.tsx`.
+The two configuration types are mostly the same, except that some configuration features, like Session Replay, only work in `entry.client.tsx`.
 
 ```typescript {tabTitle:Client} {filename: entry.client.tsx}
 import { useLocation, useMatches } from "@remix-run/react";
@@ -22,12 +22,12 @@ Sentry.init({
     // Replay is only available in the client
     new Sentry.Replay(),
   ],
-  
+
   // Set tracesSampleRate to 1.0 to capture 100%
   // of transactions for performance monitoring.
   // We recommend adjusting this value in production
   tracesSampleRate: 1.0,
-  
+
   // Capture Replay for 10% of all sessions,
   // plus for 100% of sessions with an error
   replaysSessionSampleRate: 0.1,
@@ -51,7 +51,7 @@ Sentry.init({
       ),
     }),
   ],
-  
+
   // Set tracesSampleRate to 1.0 to capture 100%
   // of transactions for performance monitoring.
   // We recommend adjusting this value in production

src/platform-includes/getting-started-config/javascript.svelte.mdx

@@ -15,7 +15,7 @@ Sentry.init({
   // of transactions for performance monitoring.
   // We recommend adjusting this value in production
   tracesSampleRate: 1.0,
-  
+
   // Capture Replay for 10% of all sessions,
   // plus for 100% of sessions with an error
   replaysSessionSampleRate: 0.1,

src/platform-includes/getting-started-config/javascript.vue.mdx

@@ -22,12 +22,12 @@ Sentry.init({
     }),
     new Sentry.Replay(),
   ],
-  
+
   // Set tracesSampleRate to 1.0 to capture 100%
   // of transactions for performance monitoring.
   // We recommend adjusting this value in production
   tracesSampleRate: 1.0,
-  
+
   // Capture Replay for 10% of all sessions,
   // plus for 100% of sessions with an error
   replaysSessionSampleRate: 0.1,

src/platform-includes/getting-started-install/node.mdx

@@ -4,4 +4,4 @@ npm install --save @sentry/node
 
 ```bash {tabTitle:Yarn}
 yarn add @sentry/node
-```
+```

src/platform-includes/set-fingerprint/database-connection/javascript.mdx

@@ -7,7 +7,7 @@ Sentry.init({
     const exception = hint.originalException;
 
     if (exception instanceof DatabaseConnectionError) {
-      event.fingerprint = ['database-connection-error'];
+      event.fingerprint = ["database-connection-error"];
     }
 
     return event;

src/platform-includes/set-fingerprint/rpc/javascript.mdx

@@ -18,7 +18,7 @@ Sentry.init({
 
     if (exception instanceof MyRPCError) {
       event.fingerprint = [
-        '{{ default }}',
+        "{{ default }}",
         String(exception.functionName),
         String(exception.errorCode),
       ];

src/platforms/common/usage/sdk-fingerprinting.mdx

@@ -33,14 +33,18 @@ You can use variable substitution to fill dynamic values into the fingerprint ge
 
 ## Group Errors With Greater Granularity
 
-Let's imagine your application queries a Remote Procedure Call Model (RPC) interface or external Application Programming Interface (API) service, so the stack trace is generally the same (even if the outgoing request is very different).
+In some scenarios, you'll want to group errors more granularly.
+
+For example, if your application queries a Remote Procedure Call Model (RPC) interface or external Application Programming Interface (API) service, the stack trace is generally the same, even if the outgoing request is very different.
 
 The following example will split up the default group Sentry would create (represented by `{{ default }}`) further, taking some attributes on the error object into account:
 
 <PlatformContent includePath="set-fingerprint/rpc" />
 
 ## Group Errors More Aggressively
 
-If a generic error, such as a database connection error, has many different stack traces and never groups them together, you can overwrite Sentry's grouping by omitting `{{ default }}` from the array:
+You can also overwrite Sentry's grouping entirely.
+
+For example, if a generic error, such as a database connection error, has many different stack traces and never groups them together, you can overwrite Sentry's grouping by omitting `{{ default }}` from the array:
 
 <PlatformContent includePath="set-fingerprint/database-connection" />

src/platforms/javascript/common/configuration/sentry-testkit/index.mdx

@@ -21,7 +21,7 @@ yarn add sentry-testkit --dev
 ### Using in tests
 
 ```javascript
-import sentryTestkit from 'sentry-testkit';
+import sentryTestkit from "sentry-testkit";
 
 const { testkit, sentryTransport } = sentryTestkit();
 

src/platforms/javascript/guides/gatsby/index.mdx

@@ -47,10 +47,10 @@ Sentry.init({
   // of transactions for performance monitoring.
   // We recommend adjusting this value in production
   tracesSampleRate: 1.0,
-  
+
   // Capture Replay for 10% of all sessions,
   // plus for 100% of sessions with an error
   replaysSessionSampleRate: 0.1,
   replaysOnErrorSampleRate: 1.0,
 });
-```
+```

src/platforms/javascript/guides/nextjs/manual-setup.mdx

@@ -26,7 +26,7 @@ If you're updating your Sentry SDK to the latest version, check out our [migrati
 
 Create three files in the root directory of your project, `sentry.client.config.js`, `sentry.server.config.js` and `sentry.edge.config.js`. In these files, add your initialization code for the client-side SDK and server-side SDK, respectively. We've included some examples below.
 
-The three configuration types are mostly the same, except that some configuration, like the one for Session Replay, only works in `sentry.client.config.js`.
+Please note that there are slight differences between these files since they run in different places (browser, server, edge), so copy them carefully!
 
 ```javascript {tabTitle:Client} {filename:sentry.client.config.(js|ts)}
 import * as Sentry from "@sentry/nextjs";
@@ -40,7 +40,7 @@ Sentry.init({
   // of transactions for performance monitoring.
   // We recommend adjusting this value in production
   tracesSampleRate: 1.0,
-  
+
   // Capture Replay for 10% of all sessions,
   // plus for 100% of sessions with an error
   replaysSessionSampleRate: 0.1,