Apply suggestions from code review

Co-authored-by: Alex Krawiec <[email protected]>

Author: Lms24

docs/platforms/javascript/common/best-practices/web-workers.mdx

@@ -68,16 +68,16 @@ self.onmessage = (event) => {
 
 <Alert level="warning" title="The Order Matters">
 
-Ensure that in both, your main thread code as well as the worker, you set up Sentry before you start listening to messages.
+Make sure to initialize Sentry in both the main thread and the worker before either starts listening for messages.
 The Sentry SDK sends messages from the worker to the main thread, so if you start listening before Sentry is initialized, 
-the messages will appear in your listeners and you have to handle them manually.
+the messages will appear in your listeners and you will have to handle them manually.
 
 </Alert>
 
 ### Multiple Workers
 
-The `sentryWebWorkerIntegration` supports registering multiple workers. 
-You can add them directly, when you initialize the integration, or later on. 
+The `sentryWebWorkerIntegration` allows you to register multiple workers. 
+You can add them either when you initialize the integration, or later on. 
 This is helpful, if you have workers that are initialized at different points in time in your application lifecycle.
 
 ```javascript {filename:index.js} {1-5, 10-14, 18}
@@ -142,7 +142,7 @@ Likewise, don't use the `Sentry.registerWorker` in the worker. Both methods are
 ### Integrations
 
 Note, that if you use non-default integrations inside web workers, they may not function as expected. 
-However, non-default integrations that are enabled on the main thread SDK, won't be affected and will work as expected. 
+However, non-default integrations that are enabled on the main thread SDK won't be affected and will work as expected. 
 This includes Session Replay.
 
 ## Source Maps

docs/platforms/javascript/common/configuration/integrations/webworker.mdx

@@ -21,14 +21,14 @@ notSupported:
 
 _Import name: `Sentry.webWorkerIntegration`_
 
-This integration, together with `Sentry.registerWorker()`, establishes communication between the browser's main thread and one or multiple [WebWorker](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API)s.
+This integration, together with `Sentry.registerWorker()`, establishes communication between the browser's main thread and one or more [WebWorkers](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API).
 It listens to worker messages from the passed workers and forwards them to the main thread. 
 
 Read our <PlatformLink to="/best-practices/web-workers/">Web Worker Guide</PlatformLink> for more information. 
 
 <Expandable title="What does this integration do?">
 
-This integration listens to a message, sent from the worker when it calls `Sentry.registerWorker({ self })`.
+This integration listens to a message sent from the worker when it calls `Sentry.registerWorker({ self })`.
 The purpose is to sync source map information (debugIds) between the main thread and the worker so that worker
 errors caught by the main thread SDK are properly mapped to the worker's source code.