feat(replay-javascript): Streamline verify instructions (#11301)

Streamline the verify instructions for configuring replay using a JS SDK so they match the in-product docs.

Author: ArthurKnaus

platform-includes/session-replay/setup/javascript.angular.mdx

@@ -22,20 +22,12 @@ Sentry.init({
 });
 ```
 
-With the settings above, session replays with errors are always captured.
-You can verify this by triggering a test error somewhere in your Angular app, for example in your main app component:
+### Verify
 
-```html {filename: app.component.html}
-<button (click)="throwTestError()">Test Sentry Error</button>
-```
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
 
-Then, in your `app.component.ts` add:
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
 
-```javascript {filename: app.component.ts}
-public throwTestError(): void {
-  throw new Error("Sentry Test Error");
-}
-```
 
 ### PII & Privacy Considerations
 

platform-includes/session-replay/setup/javascript.astro.mdx

@@ -37,6 +37,14 @@ Session Replay can only be included on the client side.
 
 </Alert>
 
+### Verify
+
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
+
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
+
+
+
 ### PII & Privacy Considerations
 
 Personally identifiable information (PII) and privacy are important considerations when enabling Session Replay. There are multiple ways in which Sentry helps you avoid collecting PII, including:

platform-includes/session-replay/setup/javascript.capacitor.mdx

@@ -30,14 +30,12 @@ Sentry.init({
 });
 ```
 
-Session replays with errors, will always be captured with the settings above.
-You can verify this by adding the following snippet anywhere in your code and running it:
+### Verify
+
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
+
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
 
-```javascript
-setTimeout(() => {
-  throw new Error("Sentry Test Error");
-});
-```
 
 ### PII & Privacy Considerations
 Personally identifiable information (PII) and privacy are important considerations when enabling Session Replay. There are multiple ways in which Sentry helps you avoid collecting PII, including:

platform-includes/session-replay/setup/javascript.electron.mdx

@@ -22,14 +22,13 @@ Sentry.init({
 });
 ```
 
-With the settings above, session replays with errors are always captured.
-You can verify this by adding the following snippet anywhere in your renderer code and running it:
+### Verify
+
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
+
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
+
 
-```javascript
-setTimeout(() => {
-  throw new Error("Sentry Test Error");
-});
-```
 ### PII & Privacy Considerations
 
 Personally identifiable information (PII) and privacy are important considerations when enabling Session Replay. There are multiple ways in which Sentry helps you avoid collecting PII, including:

platform-includes/session-replay/setup/javascript.ember.mdx

@@ -22,14 +22,12 @@ Sentry.init({
 });
 ```
 
-With the settings above, session replays with errors are always captured.
-You can verify this by adding the following snippet anywhere in your code and running it:
+### Verify
+
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
+
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
 
-```javascript
-setTimeout(() => {
-  throw new Error("Sentry Test Error");
-});
-```
 
 ### PII & Privacy Considerations
 

platform-includes/session-replay/setup/javascript.gatsby.mdx

@@ -22,19 +22,12 @@ Sentry.init({
 });
 ```
 
-With the settings above, session replays with errors are always captured.
-You can verify this by adding the following button to your app and pressing it:
-
-```javascript
-<button
-  type="button"
-  onClick={() => {
-    throw new Error("Sentry Test Error");
-  }}
->
-  Break the world
-</button>
-```
+### Verify
+
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
+
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
+
 
 ### PII & Privacy Considerations
 

platform-includes/session-replay/setup/javascript.mdx

@@ -23,14 +23,13 @@ Sentry.init({
 });
 ```
 
-With the settings above, session replays with errors are always captured.
-You can verify this by adding the following snippet anywhere in your code and running it:
+### Verify
+
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
+
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
+
 
-```javascript
-setTimeout(() => {
-  throw new Error("Sentry Test Error");
-});
-```
 ### PII & Privacy Considerations
 
 Personally identifiable information (PII), and privacy are important considerations when enabling Session Replay. There are multiple ways in which Sentry helps you avoid collecting PII, including:

platform-includes/session-replay/setup/javascript.nextjs.mdx

@@ -24,19 +24,12 @@ Sentry.init({
 });
 ```
 
-With the settings above, session replays with errors are always captured.
-You can verify this by adding the following button to your app and pressing it:
-
-```javascript
-<button
-  type="button"
-  onClick={() => {
-    throw new Error("Sentry Test Error");
-  }}
->
-  Break the world
-</button>
-```
+### Verify
+
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
+
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
+
 
 ### PII & Privacy Considerations
 

platform-includes/session-replay/setup/javascript.react.mdx

@@ -22,19 +22,12 @@ Sentry.init({
 });
 ```
 
-With the settings above, session replays with errors are always captured.
-You can verify this by adding the following button to your app and pressing it:
-
-```javascript
-<button
-  type="button"
-  onClick={() => {
-    throw new Error("Sentry Test Error");
-  }}
->
-  Break the world
-</button>
-```
+### Verify
+
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
+
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
+
 
 ### PII & Privacy Considerations
 

platform-includes/session-replay/setup/javascript.remix.mdx

@@ -24,19 +24,12 @@ Sentry.init({
 });
 ```
 
-With the settings above, session replays with errors are always captured.
-You can verify this by adding the following button to your app and pressing it:
-
-```javascript
-<button
-  type="button"
-  onClick={() => {
-    throw new Error("Sentry Test Error");
-  }}
->
-  Break the world
-</button>
-```
+### Verify
+
+While you're testing, we recommend that you set `replaysSessionSampleRate` to `1.0`. This ensures that every user session will be sent to Sentry.
+
+Once testing is complete, **we recommend lowering this value in production**. We still recommend keeping `replaysOnErrorSampleRate` set to `1.0`, so that, whenever possible, every error has an associated replay with additional debugging context.
+
 
 ### PII & Privacy Considerations