Apply suggestions from code review before v5

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

Author: krystofwoldrich

docs/platforms/react-native/migration/before-v5.mdx

@@ -1,7 +1,7 @@
 ---
 title: Migrate to 5.x
 sidebar_order: 200
-description: "Learn about migrating to the SDK version 5."
+description: "Learn how to migrate to version 5 of the SDK ."
 ---
 
 ## From 4.x to 5.x
@@ -17,17 +17,17 @@ Rename the following `Sentry.init` options:
 - `ReactNativeTracingOptions.idleTimeout` to `ReactNativeTracingOptions.idleTimeoutMs`
 - `ReactNativeTracingOptions.maxTransactionDuration` to `ReactNativeTracingOptions.finalTimeoutMs`
 
-If you are using `TouchEventBoundary` and `accessibilityLabel` set the following:
+If you're using `TouchEventBoundary` and `accessibilityLabel` set the following:
 
 ```javascript
 Sentry.wrap(App, {
   touchEventBoundaryProps: { labelName: "accessibilityLabel" },
 });
 ```
 
-Current stack trace for `Sentry.captureMessage` has been moved from `event.exception` to `event.threads`.
+The current stack trace for `Sentry.captureMessage` has been moved from `event.exception` to `event.threads`.
 
-Default `breadcrumb.level` is `info`, value `critical` has been removed and `log` is transformed to `debug` on iOS and Android.
+The default `breadcrumb.level` is `info`, value `critical` has been removed and `log` has been transformed to `debug` on iOS and Android.
 
 The bundled `sentry-cli` version has been bumped to [v2.10.0](https://github.com/getsentry/sentry-cli/releases/tag/2.10.0). Check your usage of `sentry-cli` to reflect [breaking changes](https://github.com/getsentry/sentry-cli/releases/tag/2.0.0). Note, that `upload-dsym` has been replaced by `debug-files upload` and requires a path. Make sure to check your `Upload Debug Symbols` build step in your Xcode project. The command should look like the example below:
 
@@ -50,15 +50,15 @@ The following metadata are synchronized from `sentry-cocoa` to `react-native`:
 - `environment`
 - `breadcrumbs`
 
-The synchronized `fingerprint` might affect grouping of issues in Sentry. React Native `event.fingerprint` is merged with iOS `fingerprint` without duplicates with RN items being first in the order.
+The synchronized `fingerprint` might affect issue grouping in Sentry. React Native `event.fingerprint` is merged with iOS `fingerprint` without duplicates with RN items being first in the order.
 
 `sentry-cocoa` has been bumped to v8.0.0, please follow the related migration [here](/platforms/apple/migration/#migrating-from-7x-to-8x).
 
 `sentry-wizard` doesn't patch iOS projects for React Native 0.65 to 0.68. These versions have to be [patched manually](/platforms/react-native/manual-setup/manual-setup/#bundle-react-native-code-and-images).
 
 ### Changes to Minimum Supported Versions
 
-The minimum supported iOS version has been bumped iOS 11. The minimum Android API has been bumped to 21. The minimum supported React Native version is 0.65.0.
+The minimum supported iOS version has been bumped to iOS 11. The minimum Android API has been bumped to 21. The minimum supported React Native version is 0.65.0.
 
 ## From 4.8.x to 4.9.x
 
@@ -100,9 +100,9 @@ See the JS SDK migration guide [here](https://github.com/getsentry/sentry-javasc
 
 ## From 3.x to 4.x
 
-By bumping Sentry JavaScript to v7, new breaking changes were introduced, to know more what was changed, check the [breaking changes changelog](https://github.com/getsentry/sentry-javascript/blob/7.0.0/CHANGELOG.md#breaking-changes) from Sentry Javascript.
+By bumping Sentry JavaScript to v7, new breaking changes were introduced, to learn more about what was changed, check out the [breaking changes changelog](https://github.com/getsentry/sentry-javascript/blob/7.0.0/CHANGELOG.md#breaking-changes) from Sentry Javascript.
 
-By bumping Sentry Android to v6, new breaking changes were introduced, to know more what was changed, check the [migration guide](/platforms/android/migration/#migrating-from-iosentrysentry-android-5x-to-iosentrysentry-android-600).
+By bumping Sentry Android to v6, new breaking changes were introduced, to learn more about what was changed, check out the [migration guide](/platforms/android/migration/#migrating-from-iosentrysentry-android-5x-to-iosentrysentry-android-600).
 
 ## From 3.0.x to 3.1.x
 
@@ -117,9 +117,9 @@ const routingInstrumentation = new Sentry.ReactNavigationInstrumentation();
 
 ## From 2.x to 3.x
 
-There are no changes needed when migrating from versions `2.x` to `3.x`, although you will need to make sure that you run `pod install` on iOS and to rebuild your app on both platforms.
+There are no changes needed when migrating from versions `2.x` to `3.x`, although you will need to make sure that you run `pod install` on iOS and that you rebuild your app on both platforms.
 
-### Event origin and environment tags
+### Event Origin and Environment Tags
 
 When upgrading from prior versions to `3.x`, you may see a mismatch in the values of the `event.environment` tag compared to events sent from the SDK prior to this version. Events that originate from native iOS code will now have the `event.environment` tag set to `native`. Read more about these tags on the [event information guide](/platforms/react-native/usage/event-information/#event-origin-and-environment-tags).
 
@@ -131,7 +131,7 @@ The breaking changes are relevant only to Android. There are no breaking changes
 
 Sentry React Native version `2.5.0` depends on Sentry Android `5.0.0`. Please [refer to the Android migration guide for Android-specific changes](/platforms/android/migration/#migrating-from-iosentrysentry-android-430-to-iosentrysentry-android-500).
 
-`Settings.Secure.ANDROID_ID` has been removed and replaced with a randomly-generated `installationId`. This may affect the number of unique users displayed on the the Issues page and Alerts. If you always set a custom user using `Sentry.setUser(customUser)`, the behavior has not changed. While you don't have to make any update, if you want to maintain the old behavior, use the following code snippet which makes use of the [react-native-device-info](https://github.com/react-native-device-info/react-native-device-info) library.
+`Settings.Secure.ANDROID_ID` has been removed and replaced with a randomly-generated `installationId`. This may affect the number of unique users displayed on the the Issues page and Alerts. If you've always set a custom user using `Sentry.setUser(customUser)`, the behavior hasn't changed. While you don't have to make any updates, if you want to maintain the old behavior, use the following code snippet which makes use of the [react-native-device-info](https://github.com/react-native-device-info/react-native-device-info) library.
 
 ```javascript
 import { Platform } from "react-native";
@@ -161,7 +161,7 @@ if (Platform.OS === "android") {
 
 ## React Navigation Instrumentation from <2.3.0
 
-We changed the initialization method for the React Navigation v5 and above routing instrumentation to avoid a potential issue when using linking. You now register the navigation container inside the `onReady` prop passed to the `NavigationContainer`.
+We changed the initialization method for the React Navigation v5 and above, routing instrumentation to avoid a potential issue when using linking. You now register the navigation container inside the `onReady` prop passed to the `NavigationContainer`.
 
 From:
 
@@ -235,23 +235,23 @@ class App extends React.Component {
 
 Sentry's most recent version of our React Native SDK enables release health tracking and native stack traces by default.
 
-This version of the SDK uses the [envelope endpoint](https://develop.sentry.dev/sdk/envelopes/). If you are using self-hosted Sentry, the SDK requires Sentry version 20.6.0 and above. If you are using our SaaS product ([sentry.io](https://sentry.io)), no changes or actions needed.
+This version of the SDK uses the [envelope endpoint](https://develop.sentry.dev/sdk/envelopes/). If you're using self-hosted Sentry, the SDK requires Sentry version 20.6.0 and above. If you're using our SaaS product ([sentry.io](https://sentry.io)), no changes or actions are needed.
 
 ### iOS/MacOS
 
-While the migration does not introduce breaking changes for iOS/MacOS on the React Native side, we recommend running `pod install` after the upgrade.
+While the migration doesn't introduce breaking changes for iOS/MacOS on the React Native side, we recommend running `pod install` after the upgrade.
 
 <Note>
 
-If you are using our Cocoa SDK directly, follow that [migration guide for 5.x to 6.x](/platforms/apple/migration/#migrating-from-5x-to-6x).
+If you're using our Cocoa SDK directly, follow the [migration guide for 5.x to 6.x](/platforms/apple/migration/#migrating-from-5x-to-6x).
 
 </Note>
 
-On iOS/MacOS, we now cache events in envelopes on the disk. As a result, you might lose a few cached events during the migration. Due to the effort involved, the migration from 5.x to 6.x does not move these few cached events into envelopes.
+On iOS/MacOS, we now cache events in envelopes on the disk. As a result, you might lose a few cached events during the migration. Due to the high level of effort involved, the migration from 5.x to 6.x won't move these few cached events into envelopes.
 
 ### Android
 
-If you are on React Native &lt;0.60, you will need to update this line in your `MainApplication.java`:
+If you're on React Native &lt;0.60, you'll need to update this line in your `MainApplication.java`:
 
 From (earlier version):
 
@@ -273,7 +273,7 @@ import io.sentry.react.RNSentryPackage;
 import io.sentry.react.RNSentryPackage
 ```
 
-Other than the one line change noted above, the migration should not cause breaking changes on the React Native side.
+Other than the one line change noted above, the migration shouldn't cause breaking changes on the React Native side.
 
 <Note>
 <markdown>
@@ -285,7 +285,7 @@ If you use our Android SDK directly, you should follow its [migration guide for
 
 ## From 0.x to 1.x
 
-If you are upgrading from an earlier version of Sentry's React Native SDK, you should unlink the package to ensure the generated code is updated to the latest version:
+If you're upgrading from an earlier version of Sentry's React Native SDK, you should unlink the package to ensure the generated code is updated to the latest version:
 
 ```bash
 react-native unlink react-native-sentry
@@ -299,4 +299,4 @@ npm uninstall react-native-sentry --save
 yarn remove react-native-sentry
 ```
 
-From there you can follow the standard installation instructions for `@sentry/react-native`.
+From there, you can follow the standard installation instructions for `@sentry/react-native`.