Apply suggestions from code review

Co-authored-by: Liza Mock <[email protected]>

Author: AbhiPrasad

src/platform-includes/performance/configure-sample-rate/javascript.mdx

@@ -8,7 +8,7 @@ Sentry.init({
 
   // This enables automatic instrumentation (highly recommended), but is not
   // necessary for purely manual usage.
-  // If you only want manual usage remove the BrowserTracing integration and add
+  // If you only want to use manually, remove the BrowserTracing integration and add
   // Sentry.addTracingExtensions() above your Sentry.init() call.
   integrations: [new Sentry.BrowserTracing()],
 

src/platform-includes/performance/configure-sample-rate/javascript.react.mdx

@@ -6,7 +6,7 @@ Sentry.init({
 
   // This enables automatic instrumentation (highly recommended), but is not
   // necessary for purely manual usage.
-  // If you only want manual usage remove the BrowserTracing integration and add
+  // If you only want to use manually, remove the BrowserTracing integration and add
   // Sentry.addTracingExtensions() above your Sentry.init() call.
   integrations: [new Sentry.BrowserTracing()],
 

src/platform-includes/performance/configure-sample-rate/javascript.vue.mdx

@@ -9,7 +9,7 @@ Sentry.init({
 
   // This enables automatic instrumentation (highly recommended), but is not
   // necessary for purely manual usage
-  // If you only want manual usage remove the BrowserTracing integration and add
+  // If you only want to use manually, remove the BrowserTracing integration and add
   // Sentry.addTracingExtensions() above your Sentry.init() call.
   integrations: [new Sentry.BrowserTracing()],
 

src/platforms/javascript/common/configuration/tree-shaking/index.mdx

@@ -24,7 +24,7 @@ To make optional code eligible for tree shaking, you can replace various flags i
 `__SENTRY_TRACING__`
 
 : Replacing this flag with `false` will tree shake all code in the SDK that is related to performance monitoring.
-**Attention:** `__SENTRY_TRACING__` must not be replaced with `false` when when you're using any performance monitoring related SDK features (e.g. `Sentry.startTransaction()`). This flag is intended to be used in combination with packages like `@sentry/next` or `@sentry/sveltekit` that automatically include performance monitoring functionality.
+**Attention:** `__SENTRY_TRACING__` must not be replaced with `false` when you're using any performance monitoring-related SDK features (e.g. `Sentry.startTransaction()`). This flag is intended to be used in combination with packages like `@sentry/next` or `@sentry/sveltekit`, which automatically include performance monitoring functionality.
 
 <PlatformSection notSupported={["javascript.nextjs"]}>
 

src/platforms/javascript/common/configuration/webworkers/index.mdx

@@ -85,7 +85,7 @@ self.onmessage = message => {
 
 ### Integrations
 
-Using non-default integrations inside Web Workers may not work as expected. Non-default integrations enabled outside workers' scope are not affected by worker-level configurations and will still work as expected.
+Note, that if you use non-default integrations inside web workers, they may not function as expected. But non-default integrations that are enabled outside of a worker’s scope won’t be affected and will function as expected.
 
 ### Source Maps
 

src/platforms/javascript/guides/ember/configuration/ember-options.mdx

@@ -27,7 +27,7 @@ The following documentation is for Ember specific configuration, for Sentry opti
 
 ### Performance Monitoring Considerations
 
-The Sentry tracing integration is already set up via the Ember addon with custom Ember instrumentation for routing, components, and the runloop. It sideloads Sentry performance monitoring as a chunk to instrument your application. If you would like to disable this automatic instrumentation and no longer receive the associated transactions, you can set `disablePerformance` in your config as in this example:
+The Sentry tracing integration is already set up via the Ember add on with custom Ember instrumentation for routing, components, and the runloop. It sideloads Sentry performance monitoring as a chunk to instrument your application. If you'd like to disable this automatic instrumentation and stop receiving the associated transactions,  set `disablePerformance` in your config. See example below:
 
 ```javascript
 ENV["@sentry/ember"] = {