Apply suggestions from code review - integrations

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

Author: krystofwoldrich

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

@@ -1,7 +1,7 @@
 ---
 title: Custom Integrations
 sidebar_order: 200
-description: "Learn how you can enable a custom integration."
+description: "Learn how to enable a custom integration."
 ---
 
 In addition to the integrations that come with the SDK, you can also write custom integrations.
@@ -32,7 +32,7 @@ All hooks on an integration are optional. The only required field is the `name`.
 ### `setup`
 
 The `setup` hook is called when the SDK is initialized. It receives the client instance as an argument.
-You should use this if you want to run some code on initialization.
+You should use this if you want to run some code upon initialization.
 
 ```javascript
 const integration = {
@@ -45,7 +45,7 @@ const integration = {
 
 ### `processEvent`
 
-This hook can be used to modify events before they are sent to Sentry. It receives the event as an argument and should return the modified event. The hook also receives a hint object that may hold additional event metadata, and the client that is sending the event. You can also return `null` to drop the event from being sent.
+This hook can be used to modify events before they're sent to Sentry. It receives the event as an argument and should return the modified event. The hook also receives a hint object that may hold additional event metadata, as well as the client that's sending the event. You can also return `null` to drop the event from being sent.
 
 ```javascript
 const integration = {
@@ -66,11 +66,11 @@ You can also return a promise that resolves with an event or `null`. However, th
 
 ### `preprocessEvent`
 
-This hook is similar to `processEvent`, but it is called before the event is passed to any other `processEvent` hook. It can be used in places where the order of processing is important.
+This hook is similar to `processEvent`, but it's called before the event is passed to any other `processEvent` hook. It can be used in places where the order of processing is important.
 
-In most cases, you should just use `processEvent`. Only use `preprocessEvent` if you need to ensure that your hook is called before any other `processEvent` hook.
+You can use `processEvent` for most cases, but only when you need to ensure that your hook is called before any other `processEvent` hook use `preprocessEvent`.
 
-Similar to `processEvent`, this hooks receives the event, hint, and client as arguments. However, this hook does not allow to return a modified event or `null` to drop the event - instead, you can only mutate the passed in event in this hook:
+Similar to `processEvent`, this hook receives the event, hint, and client as arguments. However, this hook won't allow the return of a modified event and won't `null` to drop the event. You can only mutate the passed in event in this hook:
 
 ```javascript
 const integration = {
@@ -87,8 +87,7 @@ const integration = {
 
 ### `setupOnce`
 
-This hook is similar to `setup`, but it is only run once, even if the SDK is re-initialized. It does not receive any arguments.
-You should probably not use this, but use `setup` instead. The only reason to use `setupOnce` is e.g. when you may be calling `Sentry.init()` multiple times and you want to ensure a certain piece of code is only run once.
+This hook is similar to `setup`, but it's only run once, even if the SDK is re-initialized. It won't receive any arguments. We recommend that you use `setup` instead. The only reason to use `setupOnce` is when you may be calling `Sentry.init()` multiple times and you want to ensure a certain piece of code is only run once.
 
 ```javascript
 const integration = {
@@ -101,12 +100,8 @@ const integration = {
 
 ### `afterAllSetup`
 
-This hook is triggered after `setupOnce()` and `setup()` have been called for all integrations.
-You can use it if it is important that all other integrations have been run before.
+While we recommend that you use the `setup` hook in most cases, `afterAllSetup` can be used to make sure that all other integrations have been run. This hook receives the `client` that is being set up as the first argument and is triggered after `setupOnce()` and `setup()` have been called for all integrations. 
 
-In most cases, you should not need to use this hook, and should use `setup` instead.
-
-The hook receives the `client` that is being set up as the first argument.
 
 ```javascript
 const integration = {