Apply suggestions from code review

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

Author: Luca Forstner

docs/platforms/javascript/common/opentelemetry/custom-setup.mdx

@@ -27,7 +27,7 @@ sidebar_order: 0
 
 Use this guide when you already have a completely custom OpenTelemetry setup or when you intend to add a custom OpenTelemetry setup next to the Sentry SDK.
 
-If you are looking to simply add individual OpenTelemetry Instrumentation to your Sentry setup, it is recommended to read <PlatformLink to="/opentelemetry/using-opentelemetry-apis/#adding-additional-opentelemetry-instrumentation">Adding Additional OpenTelemetry Instrumentation</PlatformLink> instead.
+If you are looking to simply add individual OpenTelemetry instrumentation to your Sentry setup, you should read <PlatformLink to="/opentelemetry/using-opentelemetry-apis/#adding-additional-opentelemetry-instrumentation">Adding Additional OpenTelemetry Instrumentation</PlatformLink> instead.
 
 </Note>
 

docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx

@@ -49,10 +49,10 @@ Sentry.init({
 <Note>
   It is possible to add instrumentations via `registerInstrumentations()` from
   `@opentelemetry/instrumentation`. However, with ESM (`import`/`export` syntax)
-  you need to be careful to do so before `import`ing any modules that should be
+  you need to be careful to do so before importing any modules that should be
   instrumented.
 
-As a rule of thumb, `registerInstrumentations()` should be called right after, and in the same context when registering <PlatformLink to="/opentelemetry/custom-setup/#esm-loaders">ESM Loaders</PlatformLink>.
+As a rule of thumb, `registerInstrumentations()` should be called right after, and in the same context as registering <PlatformLink to="/opentelemetry/custom-setup/#esm-loaders">ESM Loaders</PlatformLink>.
 
 </Note>