Apply suggestions from code review

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

Author: krystofwoldrich

docs/platforms/react-native/integrations/plugin.mdx

@@ -5,7 +5,7 @@ description: "Learn more about pluggable integrations: HttpClient and RewriteFra
 
 The Sentry SDK uses integrations to hook into the functionality of popular libraries to automatically instrument your application and give you the best data out of the box.
 
-Integrations automatically add error instrumentation, performance instrumentation, and/or extra context information to your application. Some are enabled by default, but you can disable them or modify their settings. Other can be added to extend the default functionality of the SDK.
+Integrations automatically add error instrumentation, performance instrumentation, and/or extra context information to your application. Some are enabled by default, but you can disable them or modify their settings. Others can be added to extend the default functionality of the SDK.
 
 ## Adding an Integration
 
@@ -92,7 +92,7 @@ Sentry.init({
 
 #### Usage Examples
 
-For example, if the full path to your file is `bundles/bundle1.js`:
+We'll use `bundles/bundle1.js` as an example full path to your file for the table below:
 
 | Usage                                  | Path in Stack Trace | Description                                                                                                                      |
 | -------------------------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------- |

docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx

@@ -34,7 +34,7 @@ We currently provide three routing instrumentations out of the box to instrument
 
 ### Additional Instrumentation
 
-- [Custom Navigation](/platforms/react-native/tracing/instrumentation/custom-navigation/) to add custom navigation library integration
+- [Custom Navigation](/platforms/react-native/tracing/instrumentation/custom-navigation/) to add the custom navigation library integration
 - [Custom Instrumentation](/platforms/react-native/tracing/instrumentation/custom-navigation/) to add custom performance data to your application
 
 ## Features
@@ -112,11 +112,11 @@ Sentry.init({
 
 ### tracePropagationTargets
 
-The default value of `tracePropagationTargets` is `['localhost', /^\//]`. The React Native SDK will attach the `sentry-trace` header to all outgoing XHR/fetch requests whose destination contains a string in the list or matches a regex in the list. If your frontend is making requests to a different domain, you will need to add the domain there to propagate the `sentry-trace` header to the backend services, which is required to link transactions together as part of a single trace. **The `tracePropagationTargets` option matches against the entire request URL, not just the domain. Using stricter regex to match certain parts of the URL ensures that requests do not unnecessarily have the `sentry-trace` header attached.**
+The default value of `tracePropagationTargets` is `['localhost', /^\//]`. The React Native SDK will attach the `sentry-trace` header to all outgoing XHR/fetch requests whose destination contains a string in the list or matches a regex in the list. If your frontend is making requests to a different domain, you'll need to add the domain there to propagate the `sentry-trace` header to the backend services, which is required to link transactions together as part of a single trace. **The `tracePropagationTargets` option matches against the entire request URL, not just the domain. Using stricter regex to match certain parts of the URL ensures that requests don't unnecessarily have the `sentry-trace` header attached.**
 
 <PlatformContent includePath="performance/tracePropagationTargets-example" />
 
-You will need to configure your web server CORS to allow the `sentry-trace` header. The configuration might look like `"Access-Control-Allow-Headers: sentry-trace"`, but the configuration depends on your setup. If you do not allow the `sentry-trace` header, the request might be blocked.
+You'll need to configure your web server CORS to allow the `sentry-trace` header. The configuration might look like `"Access-Control-Allow-Headers: sentry-trace"`, but the configuration depends on your setup. If you don't allow the `sentry-trace` header, the request might get blocked.
 
 ### beforeStartSpan
 
@@ -163,13 +163,13 @@ Sentry.init({
 
 ### idleTimeoutMs
 
-The idle time, measured in ms, to wait until the transaction will be finished, if there are no unfinished spans. The transaction will use the end timestamp of the last finished span as the endtime for the transaction.
+The amount of idle time, measured in ms, you have to wait for the transaction to finish if there are no unfinished spans. The transaction will use the end timestamp of the last finished span as the endtime for the transaction.
 
 The default is `1_000`.
 
 ### finalTimeoutMs
 
-The maximum duration of the transaction, measured in ms. If the transaction duration hits the `finalTimeout` value, it will be finished.
+The maximum duration of the transaction, measured in ms. If the transaction duration hits the `finalTimeout` value, it will be done.
 
 The default is `60_0000`.
 

docs/platforms/react-native/tracing/instrumentation/custom-instrumentation.mdx

@@ -20,9 +20,9 @@ import * as Sentry from "@sentry/react-native";
 
 There are three key functions for creating spans:
 
-- [startSpan](#starting-an-active-span-startspan): Creates a new span that is active, and which is automatically ended. You'll likely want to use this function.
-- [startSpanManual](#starting-an-active-span-with-manual-end-startspanmanual): Creates a new span that is active, which has to be ended manually.
-- [startInactiveSpan](#starting-inactive-spans-startinactivespan): Creates a new span that is inactive, which has to be ended manually.
+- [startSpan](#starting-an-active-span-startspan): Creates a new span that is active and ends automatically. You'll likely want to use this function.
+- [startSpanManual](#starting-an-active-span-with-manual-end-startspanmanual): Creates a new span that is active and has to be ended manually.
+- [startInactiveSpan](#starting-inactive-spans-startinactivespan): Creates a new span that is inactive and has to be ended manually.
 
 ## Active vs. Inactive Spans