diff --git a/packages/docs-gesture-handler/docs/components/buttons.mdx b/packages/docs-gesture-handler/docs/components/buttons.mdx
index 041d387fbe..720556a0ad 100644
--- a/packages/docs-gesture-handler/docs/components/buttons.mdx
+++ b/packages/docs-gesture-handler/docs/components/buttons.mdx
@@ -138,7 +138,7 @@ This type of button component is ideal for use with rectangular elements or cont
 underlayColor?: string;
 ```
 
-Background color that will be dimmed when button is in active state.
+Background color that will be dimmed when the button is in an active state.
 
 <HeaderWithBadges platforms={['iOS']}>
 ### activeOpacity
@@ -148,7 +148,7 @@ Background color that will be dimmed when button is in active state.
 activeOpacity?: number;
 ```
 
-Opacity applied to the underlay when button is in active state.
+Opacity applied to the underlay when the button is in an active state.
 
 ## BorderlessButton
 
@@ -188,27 +188,27 @@ const AccessibleButton = () => (
 
 ## Design patterns
 
-Components listed here were not designed to behave and look in the same way on both platforms but rather to be used for handling similar behaviour on iOS and Android taking into consideration their design concepts.
+Components listed here were not designed to behave and look in the same way on both platforms, but rather to be used for handling similar behaviour on iOS and Android taking into consideration their design concepts.
 
 If you wish to get specific information about platforms design patterns, visit [official Apple docs](https://developer.apple.com/design/human-interface-guidelines/components/menus-and-actions/buttons) and [Material.io guideline](https://material.io/components/buttons#text-button), which widely describe how to implement coherent design.
 
-This library allows to use native components with native feedback in adequate situations.
+This library allows the use of native components with native feedback in adequate situations.
 
-If you do not wish to implement custom design approach, [`RectButton`](#rectbutton) and [`BorderlessButton`](#borderlessbutton) seem to be absolutely enough and there's no need to use anything else. In all the remaining cases you can always rely on [`BaseButton`](#basebutton) which is a superclass for the other button classes and can be used as a generic `Touchable` replacement that can be customized to your needs.
+If you do not wish to implement a custom design approach, [`RectButton`](#rectbutton) and [`BorderlessButton`](#borderlessbutton) seem to be absolutely enough and there's no need to use anything else. In all the remaining cases, you can always rely on [`BaseButton`](#basebutton) which is a superclass for the other button classes and can be used as a generic `Touchable` replacement that can be customized to your needs.
 
 Below we list some of the common usecases for button components to be used along with the type of button that should be used according to the platform specific design guidelines.
 
 ### Lists and action buttons
 
-If you have a list with clickable items or have an action button that need to display as a separate UI block (vs being inlined in a text) you should use [`RectButton`](#rectbutton). It changes opacity on click and additionally supports a [ripple effect](#ripplecolor-android-only) on Android.
+If you have a list with clickable items or have an action button that needs to display as a separate UI block (vs being inlined in a text) you should use [`RectButton`](#rectbutton). It changes opacity on click and additionally supports a [ripple effect](#ripplecolor-android-only) on Android.
 
 <GifGallery>
   <img src={useBaseUrl('gifs/androidsettings.gif')} width="280" />
   <img src={useBaseUrl('gifs/iossettings.gif')} width="280" />
 </GifGallery>
 
-To determine emphasis of button it's vital to use fill color or leave it transparent especially on Android.
-For medium emphasis you may consider outlined buttons which are used for lower impact than fill buttons.
+To determine the emphasis of a button, it's vital to use a fill color or leave it transparent, especially on Android.
+For medium emphasis, you may consider outlined buttons which are used for lower impact than fill buttons.
 
 <GifGallery>
   <img src={useBaseUrl('gifs/androidbutton.gif')} width="280" />
diff --git a/packages/docs-gesture-handler/docs/components/reanimated-drawer-layout.mdx b/packages/docs-gesture-handler/docs/components/reanimated-drawer-layout.mdx
index 378d47b1a6..93ba3b45a0 100644
--- a/packages/docs-gesture-handler/docs/components/reanimated-drawer-layout.mdx
+++ b/packages/docs-gesture-handler/docs/components/reanimated-drawer-layout.mdx
@@ -92,7 +92,7 @@ export enum DrawerKeyboardDismissMode {
 }
 `}/>
 
-Determines if system keyboard should be closed upon dragging the drawer.
+Determines if the system keyboard should be closed upon dragging the drawer.
 
 ### animationSpeed
 
@@ -250,7 +250,7 @@ Either a component rendered in the content view or a function. If `children` is
 enableContextMenu: boolean;
 ```
 
-Specifies whether context menu should be enabled after clicking on underlying view with right mouse button. Default value is set to `false` if [`MouseButton.RIGHT`](#mousebutton-web--android-only) is specified.
+Specifies whether the context menu should be enabled after clicking on the underlying view with the right mouse button. Default value is set to `false` if [`MouseButton.RIGHT`](#mousebutton-web--android-only) is specified.
 
 <HeaderWithBadges platforms={['web']}>
 ### userSelect
@@ -260,7 +260,7 @@ Specifies whether context menu should be enabled after clicking on underlying vi
 userSelect: 'none' | 'auto' | 'text';
 ```
 
-This parameter allows to specify which `userSelect` property should be applied to underlying view. Default value is set to `"none"`.
+This parameter allows specifying which `userSelect` property should be applied to the underlying view. Default value is set to `"none"`.
 
 <HeaderWithBadges platforms={['web']}>
 ### activeCursor
@@ -270,7 +270,7 @@ This parameter allows to specify which `userSelect` property should be applied t
 activeCursor: ActiveCursor;
 ```
 
-This parameter allows to specify which cursor should be used when gesture activates. Supports all [CSS cursor values](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/cursor#keyword) (e.g. `"grab"`, `"zoom-in"`). Default value is set to `"auto"`.
+This parameter allows specifying which cursor should be used when the gesture activates. Supports all [CSS cursor values](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/cursor#keyword) (e.g. `"grab"`, `"zoom-in"`). Default value is set to `"auto"`.
 
 ## Drawer ref methods
 
@@ -295,7 +295,7 @@ export type DrawerMovementOption = {
 openDrawer: (options?: DrawerMovementOption) => void;
 ```
 
-Allows to manually open the drawer.
+Allows manually opening the drawer.
 
 ### closeDrawer
 
@@ -303,7 +303,7 @@ Allows to manually open the drawer.
 closeDrawer: (options?: DrawerMovementOption) => void;
 ```
 
-Allows to manually close the drawer.
+Allows manually closing the drawer.
 
 ## Example
 
diff --git a/packages/docs-gesture-handler/docs/components/reanimated_swipeable.mdx b/packages/docs-gesture-handler/docs/components/reanimated_swipeable.mdx
index 6fdc72ef21..9d8b323f93 100644
--- a/packages/docs-gesture-handler/docs/components/reanimated_swipeable.mdx
+++ b/packages/docs-gesture-handler/docs/components/reanimated_swipeable.mdx
@@ -258,7 +258,7 @@ Enables two-finger gestures on supported devices, for example iPads with trackpa
 enabled: boolean;
 ```
 
-Indicates whether `ReanimatedSwipeable` should be analyzing stream of touch events or not. Defaults to `true`.
+Indicates whether `ReanimatedSwipeable` should be analyzing the stream of touch events or not. Defaults to `true`.
 
 ### testID
 
@@ -295,7 +295,7 @@ type HitSlop =
 `}/>
 
 This parameter enables control over what part of the connected view area can be used to begin recognizing the gesture.
-When a negative number is provided the bounds of the view will reduce the area by the given number of points in each of the sides evenly.
+When a negative number is provided, the bounds of the view will reduce the area by the given number of points in each of the sides evenly.
 See [hitSlop section](/docs/gestures/use-pan-gesture#hitslop) in `Pan` gesture for more details.
 
 ## Swipeable ref methods
diff --git a/packages/docs-gesture-handler/docs/components/touchables.md b/packages/docs-gesture-handler/docs/components/touchables.md
index 23129eecf9..9271b6738f 100644
--- a/packages/docs-gesture-handler/docs/components/touchables.md
+++ b/packages/docs-gesture-handler/docs/components/touchables.md
@@ -8,7 +8,7 @@ sidebar_label: Touchables
 Touchables will be removed in the future version of Gesture Handler. Use [`Pressable`](/docs/components/pressable) instead.
 :::
 
-Gesture Handler library provides an implementation of RN's touchable components that are based on [native buttons](buttons.mdx) and does not rely on JS responder system utilized by RN. Our touchable implementation follows the same API and aims to be a drop-in replacement for touchables available in React Native.
+Gesture Handler library provides an implementation of RN's touchable components that are based on [native buttons](buttons.mdx) and do not rely on the JS responder system utilized by RN. Our touchable implementation follows the same API and aims to be a drop-in replacement for touchables available in React Native.
 
 React Native's touchables API can be found here:
 
@@ -17,15 +17,14 @@ React Native's touchables API can be found here:
 - [Touchable Opacity](https://reactnative.dev/docs/touchableopacity)
 - [Touchable Without Feedback](https://reactnative.dev/docs/touchablewithoutfeedback)
 
-All major touchable properties (except from `pressRetentionOffset`) have been adopted and should behave in a similar way as with RN's touchables.
+All major touchable properties (except for `pressRetentionOffset`) have been adopted and should behave in a similar way as with RN's touchables.
 
-The motivation for using RNGH touchables as a replacement for these imported from React Native is to follow built-in native behavior more closely by utilizing platform native touch system instead of relying on the JS responder system.
+The motivation for using RNGH touchables as a replacement for these imported from React Native is to follow built-in native behavior more closely by utilizing the platform native touch system instead of relying on the JS responder system.
 These touchables and their feedback behavior are deeply integrated with native
 gesture ecosystem and could be connected with other native components (e.g. `ScrollView`) and Gesture Handlers easily and in a more predictable way, which
 follows native apps' behavior.
 
-Our intention was to make switch for these touchables as simple as possible. In order to use RNGH's touchables the only thing you need to do is to change library from which you import touchable components.
-need only to change imports of touchables.
+Our intention was to make the switch for these touchables as simple as possible. In order to use RNGH's touchables, the only thing you need to do is to change the library from which you import touchable components.
 
 :::info
 Gesture Handler's `TouchableOpacity` uses native driver for animations by default. If this causes problems for you, you can set `useNativeAnimations` prop to false.
diff --git a/packages/docs-gesture-handler/docs/fundamentals/callbacks-events.mdx b/packages/docs-gesture-handler/docs/fundamentals/callbacks-events.mdx
index 4ac1d88dd1..4cad941787 100644
--- a/packages/docs-gesture-handler/docs/fundamentals/callbacks-events.mdx
+++ b/packages/docs-gesture-handler/docs/fundamentals/callbacks-events.mdx
@@ -43,7 +43,7 @@ Called when a handler begins to recognize gestures. If `onBegin` was called, it
 onActivate: (event: GestureEvent<HandlerData>) => void
 ```
  
-Called when activation criteria for handler are met. If `onActivate` was called, it is guaranteed that `onDeactivate` will be called later.
+Called when activation criteria for the handler are met. If `onActivate` was called, it is guaranteed that `onDeactivate` will be called later.
 
 ### onUpdate
 
@@ -59,7 +59,7 @@ Called each time a pointer tracked by the gesture changes state, typically due t
 onDeactivate: (event: GestureEvent<HandlerData>, didSucceed: boolean) => void
 ```
 
-Called after when handler stops recognizing gestures, but only if handler activated. It is called before `onFinalize`. If the handler was interrupted, the `didSucceed` argument is set to `false`. Otherwise it is set to `true`.
+Called when handler stops recognizing gestures, but only if the handler activated. It is called before `onFinalize`. If the handler was interrupted, the `didSucceed` argument is set to `false`. Otherwise it is set to `true`.
 
 ### onFinalize
 
@@ -67,7 +67,7 @@ Called after when handler stops recognizing gestures, but only if handler activa
 onFinalize: (event: GestureEvent<HandlerData>, didSucceed: boolean) => void
 ```
 
-Called when handler stops recognizing gestures. If handler managed to activate, the `didSucceed` argument is set to `true` and `onFinalize` will be called right after `onDeactivate`. Otherwise it is set to `false`.
+Called when handler stops recognizing gestures. If the handler managed to activate, the `didSucceed` argument is set to `true` and `onFinalize` will be called right after `onDeactivate`. Otherwise it is set to `false`.
 
 ### onTouchesDown
 
@@ -190,7 +190,7 @@ export type TouchData = {
 
 `TouchData` contains information about a single touch. 
 
-- `id` - A number representing id of the touch. It may be used to track the touch between events as the id will not change while it is being tracked.
+- `id` - A number representing the id of the touch. It may be used to track the touch between events as the id will not change while it is being tracked.
 
 - `x` - X coordinate of the current position of the touch relative to the view attached to the [`GestureDetector`](/docs/fundamentals/gesture-detectors#gesture-detector). Expressed in point units.
 
diff --git a/packages/docs-gesture-handler/docs/fundamentals/gesture-composition.mdx b/packages/docs-gesture-handler/docs/fundamentals/gesture-composition.mdx
index 156407c8af..d1ec00b077 100644
--- a/packages/docs-gesture-handler/docs/fundamentals/gesture-composition.mdx
+++ b/packages/docs-gesture-handler/docs/fundamentals/gesture-composition.mdx
@@ -27,7 +27,7 @@ RNGH3 simplifies gesture interaction through dedicated composition hooks and con
 
 Only one of the provided gestures can become active at the same time. The first gesture to become active will cancel the rest of the gestures. It accepts variable number of arguments.
 
-For example, lets say that you have a component that you want to make draggable but you also want to show additional options on long press. Presumably you would not want the component to move after the long press activates. You can accomplish this using `useCompetingGestures`:
+For example, let's say that you have a component that you want to make draggable but you also want to show additional options on long press. Presumably you would not want the component to move after the long press activates. You can accomplish this using `useCompetingGestures`:
 
 <CollapsibleCode 
 label="Show full example"
@@ -39,7 +39,7 @@ src={Competing}/>
 
 All of the provided gestures can activate at the same time. Activation of one will not cancel the other.
 
-For example, if you want to make a gallery app, you might want user to be able to zoom, rotate and pan around photos. You can do it with `useSimultaneousGestures`:
+For example, if you want to make a gallery app, you might want the user to be able to zoom, rotate and pan around photos. You can do it with `useSimultaneousGestures`:
 
 > Note: the `useSharedValue` and `useAnimatedStyle` are part of [`react-native-reanimated`](https://docs.swmansion.com/react-native-reanimated/).
 
@@ -51,7 +51,7 @@ src={Simultaneous}/>
 
 ### useExclusiveGestures
 
-Only one of the provided gestures can become active. Priority is determined by the order of the aguments, where the first gesture has the highest priority, and the last has the lowest. A gesture can activate only after all higher-priority gestures before it have failed.
+Only one of the provided gestures can become active. Priority is determined by the order of the arguments, where the first gesture has the highest priority, and the last has the lowest. A gesture can activate only after all higher-priority gestures before it have failed.
 
 For example, if you want to make a component that responds to single tap as well as to a double tap, you can accomplish that using `useExclusiveGestures`:
 
@@ -66,7 +66,7 @@ src={Exclusive}/>
 
 ### requireToFail
 
-`requireToFail` allows to delay activation of the handler until all handlers passed as arguments to this method fail (or don't begin at all).
+`requireToFail` allows delaying activation of the handler until all handlers passed as arguments to this method fail (or don't begin at all).
 
 For example, you may want to have two nested components, both of them can be tapped by the user to trigger different actions: outer view requires one tap, but the inner one requires 2 taps. If you don't want the first tap on the inner view to activate the outer handler, you must make the outer gesture wait until the inner one fails:
 
@@ -78,7 +78,7 @@ src={RequireToFail}/>
 
 ### block
 
-`block` works similarly to `requireToFail` but the direction of the relation is reversed - instead of being one-to-many relation, it's many-to-one. It's especially useful for making lists where the `ScrollView` component needs to wait for every gesture underneath it. All that's required to do is to pass a ref, for example:
+`block` works similarly to `requireToFail` but the direction of the relation is reversed - instead of being a one-to-many relation, it's many-to-one. It's especially useful for making lists where the `ScrollView` component needs to wait for every gesture underneath it. All that's required to do is to pass a ref, for example:
 
 <CollapsibleCode 
 label="Show full example"
diff --git a/packages/docs-gesture-handler/docs/fundamentals/gesture-detector.mdx b/packages/docs-gesture-handler/docs/fundamentals/gesture-detector.mdx
index 448855177d..b493219d90 100644
--- a/packages/docs-gesture-handler/docs/fundamentals/gesture-detector.mdx
+++ b/packages/docs-gesture-handler/docs/fundamentals/gesture-detector.mdx
@@ -198,7 +198,7 @@ A gesture object containing the configuration and callbacks. Can be any of the b
 userSelect: 'none' | 'auto' | 'text';
 ```
 
-This parameter allows to specify which `userSelect` property should be applied to underlying view. Default value is set to `"none"`.
+This parameter allows specifying which `userSelect` property should be applied to the underlying view. Default value is set to `"none"`.
 
 <HeaderWithBadges platforms={['web']}>
 ### touchAction
@@ -208,7 +208,7 @@ This parameter allows to specify which `userSelect` property should be applied t
 touchAction: TouchAction;
 ```
 
-This parameter allows to specify which `touchAction` property should be applied to underlying view. Supports all CSS [touch-action](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/touch-action) values. Default value is set to `"none"`.
+This parameter allows specifying which `touchAction` property should be applied to the underlying view. Supports all CSS [touch-action](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/touch-action) values. Default value is set to `"none"`.
 
 <HeaderWithBadges platforms={['web']}>
 ### enableContextMenu
@@ -218,4 +218,4 @@ This parameter allows to specify which `touchAction` property should be applied
 enableContextMenu: boolean;
 ```
 
-Specifies whether context menu should be enabled after clicking on underlying view with right mouse button. Default value is set to `false`.
+Specifies whether the context menu should be enabled after clicking on the underlying view with the right mouse button. Default value is set to `false`.
diff --git a/packages/docs-gesture-handler/docs/fundamentals/installation.mdx b/packages/docs-gesture-handler/docs/fundamentals/installation.mdx
index e57893ef5d..0c9881ac75 100644
--- a/packages/docs-gesture-handler/docs/fundamentals/installation.mdx
+++ b/packages/docs-gesture-handler/docs/fundamentals/installation.mdx
@@ -91,7 +91,7 @@ export function CustomModal({ children, ...rest }) {
 }
 ```
 
-Gesture Handler on Android is implemented in Kotlin. If you need to set a specific Kotlin version to be used by the library, set the `kotlinVersion` ext property in `android/build.gradle` file and RNGH will use that version:
+Gesture Handler on Android is implemented in Kotlin. If you need to set a specific Kotlin version to be used by the library, set the `kotlinVersion` ext property in the `android/build.gradle` file and RNGH will use that version:
 
 ```groovy
 buildscript {
diff --git a/packages/docs-gesture-handler/docs/fundamentals/introduction.md b/packages/docs-gesture-handler/docs/fundamentals/introduction.md
index 34f8707495..251b4fd7e2 100644
--- a/packages/docs-gesture-handler/docs/fundamentals/introduction.md
+++ b/packages/docs-gesture-handler/docs/fundamentals/introduction.md
@@ -6,7 +6,7 @@ sidebar_position: 1
 slug: /
 ---
 
-Gesture Handler provides a declarative API exposing the native platform's touch and gesture system to React Native. It's designed to be a replacement of React Native's built in touch system called [Gesture Responder System](http://reactnative.dev/docs/gesture-responder-system). Using native touch handling allows to address the performance limitations of React Native's Gesture Responder System. It also provides more control over the platform's native components that can handle gestures on their own. If you want to learn more, we recommend [this talk](https://www.youtube.com/watch?v=V8maYc4R2G0) by [Krzysztof Magiera](https://twitter.com/kzzzf) in which he explains issues with the responder system.
+Gesture Handler provides a declarative API exposing the native platform's touch and gesture system to React Native. It's designed to be a replacement of React Native's built in touch system called [Gesture Responder System](http://reactnative.dev/docs/gesture-responder-system). Using native touch handling allows addressing the performance limitations of React Native's Gesture Responder System. It also provides more control over the platform's native components that can handle gestures on their own. If you want to learn more, we recommend [this talk](https://www.youtube.com/watch?v=V8maYc4R2G0) by [Krzysztof Magiera](https://twitter.com/kzzzf) in which he explains issues with the responder system.
 
 The main benefits of using React Native Gesture Handler are:
 
@@ -18,7 +18,7 @@ The main benefits of using React Native Gesture Handler are:
 - Ability to include any native component into the Gesture Handler's touch system, making it work alongside your gestures.
 
 :::info
-We recommended to use Reanimated to implement gesture-driven animations with Gesture Handler. Its more advanced features rely heavily on worklets and the UI runtime provided by Reanimated.
+We recommend using Reanimated to implement gesture-driven animations with Gesture Handler. Its more advanced features rely heavily on worklets and the UI runtime provided by Reanimated.
 :::
 
 ## Learning resources
@@ -29,17 +29,17 @@ We recommended to use Reanimated to implement gesture-driven animations with Ges
 
 ### Talks and workshops
 
-[Declarative future of gestures and animations in React Native](https://www.youtube.com/watch?v=kdq4z2708VM) by [Krzysztof Magiera](https://twitter.com/kzzzf) - talk that explains motivation behind creating gesture handler library. It also presents [react-native-reanimated](https://github.com/software-mansion/react-native-reanimated) and how and when it can be used with gesture handler.
+[Declarative future of gestures and animations in React Native](https://www.youtube.com/watch?v=kdq4z2708VM) by [Krzysztof Magiera](https://twitter.com/kzzzf) - talk that explains the motivation behind creating the gesture handler library. It also presents [react-native-reanimated](https://github.com/software-mansion/react-native-reanimated) and how and when it can be used with gesture handler.
 
-[React Native workshop with Expo team @ReactEurope 2018](https://youtu.be/JSIoE_ReeDk?t=41m49s) by [Brent Vatne](https://twitter.com/notbrent) – great workshop explaining gesture handler in details and presenting a few exercises that will help get you started.
+[React Native workshop with Expo team @ReactEurope 2018](https://youtu.be/JSIoE_ReeDk?t=41m49s) by [Brent Vatne](https://twitter.com/notbrent) – great workshop explaining gesture handler in detail and presenting a few exercises that will help get you started.
 
-[Living in an async world of React Native](https://www.youtube.com/watch?v=-Izgons3mec) by [Krzysztof Magiera](https://twitter.com/kzzzf) – talk which highlights some issue with the React Native's touch system Gesture Handler aims to address. Also the motivation for building this library is explained.
+[Living in an async world of React Native](https://www.youtube.com/watch?v=-Izgons3mec) by [Krzysztof Magiera](https://twitter.com/kzzzf) – talk which highlights some issues with the React Native's touch system Gesture Handler aims to address. Also the motivation for building this library is explained.
 
-[React Native Touch & Gesture](https://www.youtube.com/watch?v=V8maYc4R2G0) by [Krzysztof Magiera](https://twitter.com/kzzzf) - talk explaining JS responder system limitations and points out some of the core features of Gesture Handler.
+[React Native Touch & Gesture](https://www.youtube.com/watch?v=V8maYc4R2G0) by [Krzysztof Magiera](https://twitter.com/kzzzf) - talk explaining JS responder system limitations and pointing out some of the core features of Gesture Handler.
 
 ## Contributing
 
-If you are interested in the project and want to contribute or support it in other ways don't hesitate to contact anyone from the team on Twitter or Bluesky (links below)!
+If you are interested in the project and want to contribute or support it in other ways, don't hesitate to contact anyone from the team on Twitter or Bluesky (links below)!
 
 All PRs are welcome, but talk to us before you start working on something big.
 
@@ -48,12 +48,12 @@ The easiest way to get started with contributing code is by:
 - Reviewing the list of [open issues](https://github.com/software-mansion/react-native-gesture-handler/issues) and trying to solve the one that seem approachable to you.
 - Updating the [documentation](https://github.com/software-mansion/react-native-gesture-handler/tree/main/packages/docs-gesture-handler) whenever you see some information is unclear, missing or out of date.
 
-Code is only one way how you can contribute. You may want to consider [replying on issues](https://github.com/software-mansion/react-native-gesture-handler/issues) if you know how to help.
+Code is only one way you can contribute. You may want to consider [replying on issues](https://github.com/software-mansion/react-native-gesture-handler/issues) if you know how to help.
 
 ## Community
 
-We are very proud of the community that has been build around this package. We really appreciate all your help regardless of it is a pull request, issue report, helping others by commenting on existing issues or posting some demo or video tutorial on social media.
-If you've build something with this library you'd like to share, please contact us as we'd love to help share it with others.
+We are very proud of the community that has been built around this package. We really appreciate all your help regardless of whether it is a pull request, issue report, helping others by commenting on existing issues or posting some demo or video tutorial on social media.
+If you've built something with this library you'd like to share, please contact us as we'd love to help share it with others.
 
 ### Gesture Handler Team 🚀
 
diff --git a/packages/docs-gesture-handler/docs/fundamentals/reanimated-interactions.mdx b/packages/docs-gesture-handler/docs/fundamentals/reanimated-interactions.mdx
index ff74d76c94..e1c8745adf 100644
--- a/packages/docs-gesture-handler/docs/fundamentals/reanimated-interactions.mdx
+++ b/packages/docs-gesture-handler/docs/fundamentals/reanimated-interactions.mdx
@@ -11,7 +11,7 @@ import CollapsibleCode from '@site/src/components/CollapsibleCode';
 
 ## Automatic [workletization](https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/glossary/#to-workletize) of gesture callbacks
 
-[Worklets' Babel plugin](https://docs.swmansion.com/react-native-worklets/docs/worklets-babel-plugin/about) is setup in a way that automatically marks callbacks passed to gestures in the configuration chain as worklets. This means that you don't need to add a `'worklet';` directive at the beginning of the functions. Here is an example that will be automatically workletized:
+[Worklets' Babel plugin](https://docs.swmansion.com/react-native-worklets/docs/worklets-babel-plugin/about) is set up in a way that automatically marks callbacks passed to gestures in the configuration chain as worklets. This means that you don't need to add a `'worklet';` directive at the beginning of the functions. Here is an example that will be automatically workletized:
 
 ```jsx
 const gesture = useTapGesture({
@@ -33,7 +33,7 @@ const gesture = useTapGesture({
 });
 ```
 
-It also won't work when wrapped with hooks like `useCallback` or `useMemo`, e.g:
+It also won't work when wrapped with hooks like `useCallback` or `useMemo`, e.g.:
 
 ```jsx
 const callback = useCallback(() => {
@@ -73,7 +73,7 @@ const gesture = useTapGesture({
 
 ## Using SharedValue in gesture config
 
-RNGH3 allows to pass [`SharedValue`](https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/glossary#shared-value) to gestures' configurations. This allows to react to configuration changes without unnecessary rerenders.
+RNGH3 allows passing [`SharedValue`](https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/glossary#shared-value) to gestures' configurations. This allows reacting to configuration changes without unnecessary rerenders.
 
 <CollapsibleCode 
 label="Show full example"
diff --git a/packages/docs-gesture-handler/docs/fundamentals/state-manager.mdx b/packages/docs-gesture-handler/docs/fundamentals/state-manager.mdx
index 605d9cd833..1f25954961 100644
--- a/packages/docs-gesture-handler/docs/fundamentals/state-manager.mdx
+++ b/packages/docs-gesture-handler/docs/fundamentals/state-manager.mdx
@@ -7,7 +7,7 @@ sidebar_position: 7
 
 import CollapsibleCode from '@site/src/components/CollapsibleCode';
 
-RNGH3 allows to manually control [gestures lifecycle](/docs/under-the-hood/state) by using [`GestureStateManager`](#gesturestatemanager).
+RNGH3 allows manually controlling the [gestures' lifecycle](/docs/under-the-hood/state) by using [`GestureStateManager`](#gesturestatemanager).
 
 ## State management
 
@@ -71,7 +71,7 @@ const styles = StyleSheet.create({
 If you want to control gesture lifecycle outside of it, you can use `handlerTag` from created gesture object.
 
 :::note 
-The gestures can only be activated after it has begun, that is, after it has received received touch events.
+The gestures can only be activated after they have begun, that is, after they have received touch events.
 :::
 
 <CollapsibleCode
@@ -189,7 +189,7 @@ const styles = {
 activate: (handlerTag: number) => void;
 ```
 
-Triggers [`onActivate`](/docs/fundamentals/callbacks-events#onactivate) callback on gesture with specified `handlerTag`.
+Triggers [`onActivate`](/docs/fundamentals/callbacks-events#onactivate) callback on the gesture with the specified `handlerTag`.
 
 ### deactivate
 
@@ -197,7 +197,7 @@ Triggers [`onActivate`](/docs/fundamentals/callbacks-events#onactivate) callback
 deactivate: (handlerTag: number) => void;
 ```
 
-If the gesture had activated, it triggers the [`onDeactivate`](/docs/fundamentals/callbacks-events#ondeactivate) callback. It also triggers the [`onFinalize`](/docs/fundamentals/callbacks-events#onfinalize) callback on gesture with the specified `handlerTag`.
+If the gesture had activated, it triggers the [`onDeactivate`](/docs/fundamentals/callbacks-events#ondeactivate) callback. It also triggers the [`onFinalize`](/docs/fundamentals/callbacks-events#onfinalize) callback on the gesture with the specified `handlerTag`.
 
 ### fail
 
@@ -205,4 +205,4 @@ If the gesture had activated, it triggers the [`onDeactivate`](/docs/fundamental
 fail: (handlerTag: number) => void;
 ```
 
-Triggers [`onFinalize`](/docs/fundamentals/callbacks-events#onfinalize) callback on gesture with specified `handlerTag`. If gesture had activated, it will also trigger [`onDeactivate`](/docs/fundamentals/callbacks-events#ondeactivate) callback.
+Triggers [`onFinalize`](/docs/fundamentals/callbacks-events#onfinalize) callback on the gesture with the specified `handlerTag`. If the gesture had activated, it will also trigger [`onDeactivate`](/docs/fundamentals/callbacks-events#ondeactivate) callback.
diff --git a/packages/docs-gesture-handler/docs/gestures/_shared/base-continuous-gesture-config.md b/packages/docs-gesture-handler/docs/gestures/_shared/base-continuous-gesture-config.md
index c3143093a3..6f93a00b11 100644
--- a/packages/docs-gesture-handler/docs/gestures/_shared/base-continuous-gesture-config.md
+++ b/packages/docs-gesture-handler/docs/gestures/_shared/base-continuous-gesture-config.md
@@ -4,4 +4,4 @@
 manualActivation: boolean | SharedValue<boolean>;
 ```
 
-When `true` the handler will not activate by itself even if its activation criteria are met. Instead you can manipulate its state using [`GestureStateManager`](/docs/fundamentals/state-manager). Example usage can be found [here](/docs/fundamentals/state-manager#manualactivation).
+When `true`, the handler will not activate by itself even if its activation criteria are met. Instead, you can manipulate its state using [`GestureStateManager`](/docs/fundamentals/state-manager). Example usage can be found [here](/docs/fundamentals/state-manager#manualactivation).
diff --git a/packages/docs-gesture-handler/docs/gestures/_shared/base-gesture-config.mdx b/packages/docs-gesture-handler/docs/gestures/_shared/base-gesture-config.mdx
index ae94d348e0..bcb03e4259 100644
--- a/packages/docs-gesture-handler/docs/gestures/_shared/base-gesture-config.mdx
+++ b/packages/docs-gesture-handler/docs/gestures/_shared/base-gesture-config.mdx
@@ -8,9 +8,9 @@ import HeaderWithBadges from '@site/src/components/HeaderWithBadges';
 enabled: boolean | SharedValue<boolean>;
 ```
 
-Indicates whether the given handler should be analyzing stream of touch events or not.
-When set to `false` we can be sure that the handler will **never** activate.
-If the value gets updated while the handler already started recognizing a gesture, then the handler will stop processing gestures immediately.
+Indicates whether the given handler should be analyzing the stream of touch events or not.
+When set to `false`, we can be sure that the handler will **never** activate.
+If the value gets updated while the handler has already started recognizing a gesture, then the handler will stop processing gestures immediately.
 Default value is `true`.
 
 ### shouldCancelWhenOutside
@@ -19,7 +19,7 @@ Default value is `true`.
 shouldCancelWhenOutside: boolean | SharedValue<boolean>;
 ```
 
-When `true` the handler will stop recognition whenever the finger leaves the area of the connected view.
+When `true`, the handler will stop recognition whenever the finger leaves the area of the connected view.
 Default value of this property is different depending on the handler type.
 Most handlers' `shouldCancelWhenOutside` property defaults to `false` except for the [`LongPressGesture`](/docs/gestures/use-long-press-gesture) and [`TapGesture`](/docs/gestures/use-tap-gesture) which default to `true`.
 
@@ -50,14 +50,14 @@ type HitSlop =
 `}/>
 
 This parameter enables control over what part of the connected view area can be used to begin recognizing the gesture.
-When a negative number is provided the bounds of the view will reduce the area by the given number of points in each of the sides evenly.
+When a negative number is provided, the bounds of the view will reduce the area by the given number of points in each of the sides evenly.
 
 Instead you can pass an object to specify how each boundary side should be reduced by providing different number of points for `left`, `right`, `top` or `bottom` sides.
 You can alternatively provide `horizontal` or `vertical` instead of specifying directly `left`, `right` or `top` and `bottom`.
 Finally, the object can also take `width` and `height` attributes.
-When `width` is set it is only allow to specify one of the sides `right` or `left`.
+When `width` is set it is only allowed to specify one of the sides `right` or `left`.
 Similarly when `height` is provided only `top` or `bottom` can be set.
-Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In which case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognize when started no more than 20 points from the left edge.
+Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In that case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognized when started no more than 20 points from the left edge.
 
 **IMPORTANT:** Note that this parameter is primarily designed to reduce the area where gesture can activate. Hence it is only supported for all the values (except `width` and `height`) to be non positive (0 or lower). Although on Android it is supported for the values to also be positive and therefore allow to expand beyond view bounds but not further than the parent view bounds. To achieve this effect on both platforms you can use React Native's View [hitSlop](https://reactnative.dev/docs/view.html#hitslop) property.
 
@@ -129,7 +129,7 @@ block: Gesture | Gesture[]
 
 Adds a relation that makes other gestures wait with activation until this gesture fails (or doesn't start at all).
 
-**IMPORTANT:** Note that this method only marks the relation between gestures, without [composing them](/docs/fundamentals/gesture-composition).[`GestureDetector`](/docs/fundamentals/gesture-detectors#gesture-detector) will not recognize other gestures and it needs to be added to another detector in order to be recognized.
+**IMPORTANT:** Note that this method only marks the relation between gestures, without [composing them](/docs/fundamentals/gesture-composition). [`GestureDetector`](/docs/fundamentals/gesture-detectors#gesture-detector) will not recognize other gestures and it needs to be added to another detector in order to be recognized.
 
 ### useAnimated
 
@@ -137,7 +137,7 @@ Adds a relation that makes other gestures wait with activation until this gestur
 useAnimated: boolean;
 ```
 
-Setting this property is set to `true` ensures that the [Animated API](/docs/fundamentals/animated-interactions) functions correctly when `useNativeDriver` is set to `false`. The default value is set to `false`.
+Setting this property to `true` ensures that the [Animated API](/docs/fundamentals/animated-interactions) functions correctly when `useNativeDriver` is set to `false`. The default value is set to `false`.
 
 <HeaderWithBadges platforms={['web']}>
 ### activeCursor
@@ -147,4 +147,4 @@ Setting this property is set to `true` ensures that the [Animated API](/docs/fun
 activeCursor: ActiveCursor | SharedValue<ActiveCursor>;
 ```
 
-This parameter allows to specify which cursor should be used when gesture activates. Supports all [CSS cursor values](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/cursor#keyword) (e.g. `"grab"`, `"zoom-in"`). Default value is set to `"auto"`.
+This parameter allows specifying which cursor should be used when the gesture activates. Supports all [CSS cursor values](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/cursor#keyword) (e.g. `"grab"`, `"zoom-in"`). Default value is set to `"auto"`.
diff --git a/packages/docs-gesture-handler/docs/gestures/use-fling-gesture.mdx b/packages/docs-gesture-handler/docs/gestures/use-fling-gesture.mdx
index a95b5edb1d..6e441dbebb 100644
--- a/packages/docs-gesture-handler/docs/gestures/use-fling-gesture.mdx
+++ b/packages/docs-gesture-handler/docs/gestures/use-fling-gesture.mdx
@@ -35,8 +35,8 @@ import BaseGestureCallbacks from './\_shared/base-gesture-callbacks.mdx';
 import SharedValueInfo from './\_shared/shared-value-info.md';
 
 The gesture that tracks quick, sufficiently long movement in specified [direction](#direction).
-When gesture gets activated it will end when finger is released.
-The gesture will fail if the finger is lifted before gesture could activate.
+When the gesture gets activated it will end when the finger is released.
+The gesture will fail if the finger is lifted before the gesture could activate.
 
   <div className={appearOnMobile} style={{ display: 'flex', justifyContent: 'center' }}>
     <video playsInline autoPlay muted loop style={{maxWidth: 360}}>
@@ -124,7 +124,7 @@ export const Directions = {
 } as const;
 `}/>
 
-Expressed allowed direction of movement. Expected values are exported as constants in the `Directions` object. It's possible to combine directions using `|` operator.
+Expresses the allowed direction of movement. Expected values are exported as constants in the `Directions` object. It's possible to combine directions using `|` operator.
 
 ```js
 import { Directions } from 'react-native-gesture-handler';
@@ -142,7 +142,7 @@ const fling = useFlingGesture({ direction: Directions.RIGHT | Directions.LEFT })
 numberOfPointers: number | SharedValue<number>;
 ```
 
-Determine exact number of points required to handle the fling gesture.
+Determines the exact number of pointers required to handle the fling gesture.
 
 <MouseButtonProp />
 
diff --git a/packages/docs-gesture-handler/docs/gestures/use-hover-gesture.mdx b/packages/docs-gesture-handler/docs/gestures/use-hover-gesture.mdx
index 37208c7c52..2834678c4e 100644
--- a/packages/docs-gesture-handler/docs/gestures/use-hover-gesture.mdx
+++ b/packages/docs-gesture-handler/docs/gestures/use-hover-gesture.mdx
@@ -112,7 +112,7 @@ enum HoverEffect {
 }
 `}/>
 
-Visual effect applied to the view while the view is hovered. Defaults to `HoverEffect.None`
+Visual effect applied to the view while the view is hovered. Defaults to `HoverEffect.None`.
 
 <BaseGestureConfig />
 
diff --git a/packages/docs-gesture-handler/docs/gestures/use-manual-gesture.mdx b/packages/docs-gesture-handler/docs/gestures/use-manual-gesture.mdx
index a13841c542..518e53e675 100644
--- a/packages/docs-gesture-handler/docs/gestures/use-manual-gesture.mdx
+++ b/packages/docs-gesture-handler/docs/gestures/use-manual-gesture.mdx
@@ -59,7 +59,7 @@ To demonstrate how to make a manual gesture we will make a simple one that track
 
 <Step title="Step 6">
     We also need to handle lifting fingers from the screen, which corresponds to [`onTouchesUp`](/docs/fundamentals/callbacks-events#ontouchesup). Here we will just hide the pointers that were lifted and end the gesture if there are no more pointers on the screen.
-    Note that we are not handling [`onTouchesCancel`](/docs/fundamentals/callbacks-events#ontouchescancel) as in this very basic case we don't expect it to happen, however you should clear data about cancelled pointers (most of the time all active ones) when it is called.
+    Note that we are not handling [`onTouchesCancel`](/docs/fundamentals/callbacks-events#ontouchescancel) as in this very basic case we don't expect it to happen; however, you should clear data about cancelled pointers (most of the time all active ones) when it is called.
     <Step6 />
 </Step>
 
@@ -200,7 +200,7 @@ const styles = StyleSheet.create({
 
 ## Modifying existing gestures
 
-While manual gestures open great possibilities we are aware that reimplementing pinch or rotation from scratch just because you need to activate in specific circumstances or require position of the fingers, would be a waste of time as those gestures are already available. Therefore, you can use touch events with every gesture to extract more detailed information about the gesture than what the basic events alone provide. We also added a [`manualActivation`](/docs/fundamentals/state-manager#manualactivation) modifier on all continuous gestures, which prevents the gesture it is applied to from activating automatically, giving you full control over its behavior.
+While manual gestures open great possibilities, we are aware that reimplementing pinch or rotation from scratch just because you need to activate in specific circumstances or require position of the fingers, would be a waste of time as those gestures are already available. Therefore, you can use touch events with every gesture to extract more detailed information about the gesture than what the basic events alone provide. We also added a [`manualActivation`](/docs/fundamentals/state-manager#manualactivation) modifier on all continuous gestures, which prevents the gesture it is applied to from activating automatically, giving you full control over its behavior.
 
 ## Config
 
diff --git a/packages/docs-gesture-handler/docs/gestures/use-native-gesture.mdx b/packages/docs-gesture-handler/docs/gestures/use-native-gesture.mdx
index 3562935da2..946d138e83 100644
--- a/packages/docs-gesture-handler/docs/gestures/use-native-gesture.mdx
+++ b/packages/docs-gesture-handler/docs/gestures/use-native-gesture.mdx
@@ -107,7 +107,7 @@ export default function App() {
 shouldActivateOnStart: boolean | SharedValue<boolean>;
 ```
 
-When `true`, underlying handler will activate unconditionally when it receives any touches.
+When `true`, the underlying handler will activate unconditionally when it receives any touches.
 
 ### disallowInterruption
 
@@ -115,7 +115,7 @@ When `true`, underlying handler will activate unconditionally when it receives a
 disallowInterruption: boolean | SharedValue<boolean>;
 ```
 
-When `true`, cancels all other gesture handlers when activates.
+When `true`, this handler cancels all other gesture handlers when it activates.
 
 <BaseGestureConfig />
 
@@ -131,6 +131,6 @@ When `true`, cancels all other gesture handlers when activates.
 pointerInside: boolean;
 ```
 
-`true` if gesture was performed inside of containing view, `false` otherwise.
+`true` if the gesture was performed inside the containing view, `false` otherwise.
 
 <BaseEventData />
diff --git a/packages/docs-gesture-handler/docs/gestures/use-pan-gesture.mdx b/packages/docs-gesture-handler/docs/gestures/use-pan-gesture.mdx
index 00f245479c..81d6304877 100644
--- a/packages/docs-gesture-handler/docs/gestures/use-pan-gesture.mdx
+++ b/packages/docs-gesture-handler/docs/gestures/use-pan-gesture.mdx
@@ -114,7 +114,7 @@ const styles = StyleSheet.create({
 
 ## Multi touch pan handling
 
-If your app relies on multi touch pan handling this section provides some information how the default behavior differs between the platform and how (if necessary) it can be unified.
+If your app relies on multi touch pan handling this section provides some information about how the default behavior differs between platforms and how (if necessary) it can be unified.
 
 The difference in multi touch pan handling lies in the way how translation properties during the event are being calculated.
 On iOS the default behavior when more than one finger is placed on the screen is to treat this situation as if only one pointer was placed in the center of mass (average position of all the pointers).
@@ -126,7 +126,7 @@ This behavior can be changed on Android using [`averageTouches`](#averagetouches
 
 Note that on both Android and iOS when the additional finger is placed on the screen that translation prop is not affected even though the position of the pointer being tracked might have changed.
 Therefore it is safe to rely on translation most of the time as it only reflects the movement that happens regardless of how many fingers are placed on the screen and if that number changes over time.
-If you wish to track the "center of mass" virtual pointer and account for its changes when the number of finger changes you can use relative or absolute position provided in the event ([`x`](#x) and [`y`](#y) or [`absoluteX`](#absolutex) and [`absoluteY`](#absolutey)).
+If you wish to track the "center of mass" virtual pointer and account for its changes when the number of fingers changes you can use relative or absolute position provided in the event ([`x`](#x) and [`y`](#y) or [`absoluteX`](#absolutex) and [`absoluteY`](#absolutey)).
 
 ## Config
 
@@ -138,7 +138,7 @@ If you wish to track the "center of mass" virtual pointer and account for its ch
 minDistance: number | SharedValue<number>;
 ```
 
-Minimum distance the finger (or multiple finger) need to travel before the gesture activates. Expressed in points.
+Minimum distance the finger (or multiple fingers) need to travel before the gesture activates. Expressed in points.
 
 ### minPointers
 
@@ -146,7 +146,7 @@ Minimum distance the finger (or multiple finger) need to travel before the gestu
 minPointers: number | SharedValue<number>;
 ```
 
-A number of fingers that is required to be placed before gesture can activate. Should be higher or equal to 0.
+A number of fingers that is required to be placed before the gesture can activate. Should be higher or equal to 0.
 
 ### maxPointers
 
@@ -154,7 +154,7 @@ A number of fingers that is required to be placed before gesture can activate. S
 maxPointers: number | SharedValue<number>;
 ```
 
-When the given number of fingers is placed on the screen and gesture hasn't yet activated it will fail recognizing the gesture. Should be higher or equal to 0.
+When the given number of fingers is placed on the screen and the gesture hasn't yet activated it will fail recognizing the gesture. Should be higher or equal to 0.
 
 ### activateAfterLongPress
 
@@ -172,8 +172,8 @@ activeOffsetX: number |
   [number | SharedValue<number>, number | SharedValue<number>];
 ```
 
-Range along X axis (in points) where fingers travels without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+Range along X axis (in points) where fingers travel without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### activeOffsetY
@@ -184,8 +184,8 @@ activeOffsetY: number |
   [number | SharedValue<number>, number | SharedValue<number>];
 ```
 
-Range along Y axis (in points) where fingers travels without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+Range along Y axis (in points) where fingers travel without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### failOffsetY
@@ -196,8 +196,8 @@ failOffsetY: number |
   [number | SharedValue<number>, number | SharedValue<number>];
 ```
 
-When the finger moves outside this range (in points) along Y axis and gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+When the finger moves outside this range (in points) along Y axis and the gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### failOffsetX
@@ -208,8 +208,8 @@ failOffsetX: number |
   [number | SharedValue<number>, number | SharedValue<number>];
 ```
 
-When the finger moves outside this range (in points) along X axis and gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+When the finger moves outside this range (in points) along X axis and the gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 <HeaderWithBadges platforms={['android']}>
diff --git a/packages/docs-gesture-handler/docs/gestures/use-pinch-gesture.mdx b/packages/docs-gesture-handler/docs/gestures/use-pinch-gesture.mdx
index 7e25ccad83..1f2d24f463 100644
--- a/packages/docs-gesture-handler/docs/gestures/use-pinch-gesture.mdx
+++ b/packages/docs-gesture-handler/docs/gestures/use-pinch-gesture.mdx
@@ -143,7 +143,7 @@ The incremental change in scale since the last event frame. This value represent
 velocity: number;
 ```
 
-Velocity of the pan gesture the current moment. The value is expressed in scale factor per second.
+Velocity of the pinch gesture at the current moment. The value is expressed in scale factor per second.
 
 ### focalX
 
@@ -151,7 +151,7 @@ Velocity of the pan gesture the current moment. The value is expressed in scale
 focalX: number;
 ```
 
-Position expressed in points along X axis of center anchor point of gesture
+Position expressed in points along X axis of center anchor point of gesture.
 
 ### focalY
 
@@ -159,6 +159,6 @@ Position expressed in points along X axis of center anchor point of gesture
 focalY: number;
 ```
 
-Position expressed in points along Y axis of center anchor point of gesture
+Position expressed in points along Y axis of center anchor point of gesture.
 
 <BaseEventData />
diff --git a/packages/docs-gesture-handler/docs/gestures/use-tap-gesture.mdx b/packages/docs-gesture-handler/docs/gestures/use-tap-gesture.mdx
index 0e97c90102..8047095f45 100644
--- a/packages/docs-gesture-handler/docs/gestures/use-tap-gesture.mdx
+++ b/packages/docs-gesture-handler/docs/gestures/use-tap-gesture.mdx
@@ -43,7 +43,7 @@ The pointers involved in these gestures must not move significantly from their i
 The required number of taps and allowed distance from initial position may be configured.
 For example, you might configure tap gesture recognizers to detect single taps, double taps, or triple taps.
 
-In order for a gesture to activate, specified gesture requirements such as [`minPointers`](#minpointers), [`numberOfTaps`](#numberoftaps), [`maxDistance`](#maxdistance), [`maxDuration`](#maxduration), and [`maxDelay`](#maxdelay) must be met.
+In order for a gesture to activate, the specified gesture requirements such as [`minPointers`](#minpointers), [`numberOfTaps`](#numberoftaps), [`maxDistance`](#maxdistance), [`maxDuration`](#maxduration), and [`maxDelay`](#maxdelay) must be met.
 
   <div className={appearOnMobile} style={{ display: 'flex', justifyContent: 'center' }}>
     <video playsInline autoPlay muted loop style={{maxWidth: 360}}>
diff --git a/packages/docs-gesture-handler/docs/guides/swipe-and-scroll.md b/packages/docs-gesture-handler/docs/guides/swipe-and-scroll.md
index 6f949dcd92..40ec5e8310 100644
--- a/packages/docs-gesture-handler/docs/guides/swipe-and-scroll.md
+++ b/packages/docs-gesture-handler/docs/guides/swipe-and-scroll.md
@@ -4,7 +4,7 @@ title: Custom swipeable components inside ScrollView (web)
 sidebar_position: 5
 ---
 
-While we recommend using our own [`ReanimatedSwipeable`](/docs/components/reanimated_swipeable) component, creating your own version of swipeable gives you more control over its behavior. Common issue here is that after creating your own swipeable component, scroll does not work. In that case, try adding [`touchAction`](/docs/fundamentals/gesture-detectors#touchaction-web-only) set to `"pan-y"`, like this:
+While we recommend using our own [`ReanimatedSwipeable`](/docs/components/reanimated_swipeable) component, creating your own version of swipeable gives you more control over its behavior. A common issue here is that after creating your own swipeable component, scroll does not work. In that case, try adding [`touchAction`](/docs/fundamentals/gesture-detectors#touchaction-web-only) set to `"pan-y"`, like this:
 
 ```jsx
 <GestureDetector gesture={...} ... touchAction="pan-y">
diff --git a/packages/docs-gesture-handler/docs/guides/testing.md b/packages/docs-gesture-handler/docs/guides/testing.md
index 96607b35e2..63eb7f525e 100644
--- a/packages/docs-gesture-handler/docs/guides/testing.md
+++ b/packages/docs-gesture-handler/docs/guides/testing.md
@@ -6,7 +6,7 @@ sidebar_position: 4
 
 ## Mocking native modules
 
-In order to load mocks provided by RNGH add following to your jest config in `package.json`:
+In order to load mocks provided by RNGH, add the following to your jest config in `package.json`:
 
 ```json
 "setupFiles": ["./node_modules/react-native-gesture-handler/jestSetup.js"]
diff --git a/packages/docs-gesture-handler/docs/guides/troubleshooting.mdx b/packages/docs-gesture-handler/docs/guides/troubleshooting.mdx
index 5540dd2588..e7738c31b2 100644
--- a/packages/docs-gesture-handler/docs/guides/troubleshooting.mdx
+++ b/packages/docs-gesture-handler/docs/guides/troubleshooting.mdx
@@ -12,17 +12,17 @@ import TabItem from '@theme/TabItem';
 Thanks for giving this library a try! We are sorry that you might have encountered issues though. Here is how you can seek help:
 
 1. Search over the [issues on Github](https://github.com/software-mansion/react-native-gesture-handler/issues). There is a chance someone had this problem in the past and it has been resolved!
-2. When sure your problem hasn't been reported or was reported but the proposed solution doesn't work for you please follow [our issue reporting guidelines](#reporting-issues).
+2. When you are sure your problem hasn't been reported or was reported but the proposed solution doesn't work for you please follow [our issue reporting guidelines](#reporting-issues).
 3. You can try seeking help on [Software Mansion Discord](https://discord.com/invite/VemJ4df8Yr).
 4. If you feel like reading the source code we highly recommend it, as this is by far the best resource and gives you the most up to date insights into how the library works and what might be causing the bug.
-5. If you managed to find the solution consider [contributing](/docs/#contributing) a fix or update our documentation to make this information easier to find for the others in the future.
+5. If you managed to find the solution consider [contributing](/docs/#contributing) a fix or update our documentation to make this information easier to find for others in the future.
 
 ## Reporting issues
 
 This library is maintained by a very small team. Please keep this in mind when reporting issues, as we may not be able to respond as quickly as you might expect. We strive to address all problems as soon as possible, but our time is often constrained by other issues, features, or projects. To help us understand and address your issue more promptly, you can assist by:
 
-- Making sure the issue description is complete. Please include all the details about your environment (library version, RN version, device OS etc).
-- It is the best to provide an example app that reproduces the issue you are having. Put it up on [gist](https://gist.github.com/), [snack](https://snack.expo.io) or create a repo on Github – it doesn't matter as long as we can easily pull it in, run and see the issue.
+- Making sure the issue description is complete. Please include all the details about your environment (library version, RN version, device OS, etc.).
+- It is best to provide an example app that reproduces the issue you are having. Put it up on [gist](https://gist.github.com/), [snack](https://snack.expo.io) or create a repo on Github – it doesn't matter as long as we can easily pull it in, run and see the issue.
 - Explain how you run your repro app and what steps to take to reproduce the issue.
 - Isolate your issue from other dependencies you might be using and make the repro app as minimal as possible.
 - If you have spent some time figuring out the root cause of the problem you can leave a note about your findings so far.
@@ -30,14 +30,14 @@ This library is maintained by a very small team. Please keep this in mind when r
 
 ## It's not a bug, it's a feature
 
-- Changing `enabled` prop during a gesture has no effect, only when a gesture starts (that is a finger touches the screen) the `enabled` prop is taken into consideration to decide whether to extract (or not) the gesture and provide it with stream of events to analyze.
+- Changing `enabled` prop during a gesture has no effect, only when a gesture starts (that is, a finger touches the screen) the `enabled` prop is taken into consideration to decide whether to extract (or not) the gesture and provide it with stream of events to analyze.
 - `Native` gesture may not conform to the standard state flow due to platform specific workarounds to incorporate native views into RNGH.
 - Keep in mind that [`Touchables`](/docs/components/touchables) from RNGH are rendering two additional views that may need to be styled separately to achieve desired effect (`style` and `containerStyle` props).
 - In order for the [gesture composition](/docs/fundamentals/gesture-composition) to work, all composed gestures must be attached to the same [`GestureHandlerRootView`](/docs/fundamentals/root-view).
 
 ## Multiple instances of Gesture Handler were detected
 
-This error usually happens when in your project there exists more than one instance of Gesture Handler. It can occur when some of your dependencies have installed Gesture Handler inside their own `node_modules` instead of using it as a peer dependency. In this case two different versions of Gesture Handler JS module try to install the same Native Module.
+This error usually happens when in your project there exists more than one instance of Gesture Handler. It can occur when some of your dependencies have installed Gesture Handler inside their own `node_modules` instead of using it as a peer dependency. In this case, two different versions of the Gesture Handler JS module try to install the same Native Module.
 
 You can resolve this problem manually by modifying your `package.json` file. This will depend on the package manager you are using.
 
diff --git a/packages/docs-gesture-handler/docs/guides/upgrading-to-3.mdx b/packages/docs-gesture-handler/docs/guides/upgrading-to-3.mdx
index e5b0812531..7e83c0eee8 100644
--- a/packages/docs-gesture-handler/docs/guides/upgrading-to-3.mdx
+++ b/packages/docs-gesture-handler/docs/guides/upgrading-to-3.mdx
@@ -8,7 +8,7 @@ title: Upgrading to the new API introduced in Gesture Handler 3
 
 import CodeComparison from '@site/src/components/CodeComparison';
 
-The most important change brought by the Gesture Handler 3 is the new hook API. Migration is pretty straightforward. Instead of calling builder methods, everything is passed as a configuration object.
+The most important change brought by Gesture Handler 3 is the new hook API. Migration is pretty straightforward. Instead of calling builder methods, everything is passed as a configuration object.
 
 <CodeComparison
 label1={"RNGH 2"}
@@ -60,7 +60,7 @@ In Gesture Handler 3 some of the callbacks were renamed, namely:
 | `onEnd`   | `onDeactivate` |
 | `onTouchesCancelled`   | `onTouchesCancel` |
 
-Here is comparison of the two APIs:
+Here is a comparison of the two APIs:
 
 <CodeComparison
 label1={"RNGH 2"}
@@ -215,7 +215,7 @@ Certain components, such as `SVG`, depend on the view hierarchy to function corr
 
 ### Migrating SVG
 
-In Gesture Handler 2 it was possible to use `GestureDetector` directly on `SVG`. In Gesture Handler 3, the correct way to interact with `SVG` is to use `InterceptingGestureDetector` and `VirtualGestureDetector`.
+In Gesture Handler 2, it was possible to use `GestureDetector` directly on `SVG`. In Gesture Handler 3, the correct way to interact with `SVG` is to use `InterceptingGestureDetector` and `VirtualGestureDetector`.
 
 <CodeComparison
 label1={"RNGH 2"}
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/_shared/base-continuous-gesture-config.md b/packages/docs-gesture-handler/docs/legacy-gestures/_shared/base-continuous-gesture-config.md
index f829d626e9..17a4de8527 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/_shared/base-continuous-gesture-config.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/_shared/base-continuous-gesture-config.md
@@ -2,4 +2,4 @@
 
 ### `manualActivation(value: boolean)`
 
-When `true` the handler will not activate by itself even if its activation criteria are met. Instead you can manipulate its state using [state manager](/docs/2.x/gestures/state-manager/).
+When `true`, the handler will not activate by itself even if its activation criteria are met. Instead, you can manipulate its state using [state manager](/docs/2.x/gestures/state-manager/).
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/_shared/base-gesture-config.md b/packages/docs-gesture-handler/docs/legacy-gestures/_shared/base-gesture-config.md
index 6a39d4cb75..16774a8eef 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/_shared/base-gesture-config.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/_shared/base-gesture-config.md
@@ -2,28 +2,28 @@
 
 ### `enabled(value: boolean)`
 
-Indicates whether the given handler should be analyzing stream of touch events or not.
-When set to `false` we can be sure that the handler's state will **never** become [`ACTIVE`](/docs/2.x/fundamentals/states-events#active).
-If the value gets updated while the handler already started recognizing a gesture, then the handler's state it will immediately change to [`FAILED`](/docs/2.x/fundamentals/states-events#failed) or [`CANCELLED`](/docs/2.x/fundamentals/states-events#cancelled) (depending on its current state).
+Indicates whether the given handler should be analyzing the stream of touch events or not.
+When set to `false`, we can be sure that the handler's state will **never** become [`ACTIVE`](/docs/2.x/fundamentals/states-events#active).
+If the value gets updated while the handler has already started recognizing a gesture, then the handler's state will immediately change to [`FAILED`](/docs/2.x/fundamentals/states-events#failed) or [`CANCELLED`](/docs/2.x/fundamentals/states-events#cancelled) (depending on its current state).
 Default value is `true`.
 
 ### `shouldCancelWhenOutside(value: boolean)`
 
-When `true` the handler will [cancel](/docs/2.x/fundamentals/states-events#cancelled) or [fail](/docs/2.x/fundamentals/states-events#failed) recognition (depending on its current state) whenever the finger leaves the area of the connected view.
+When `true`, the handler will [cancel](/docs/2.x/fundamentals/states-events#cancelled) or [fail](/docs/2.x/fundamentals/states-events#failed) recognition (depending on its current state) whenever the finger leaves the area of the connected view.
 Default value of this property is different depending on the handler type.
 Most handlers' `shouldCancelWhenOutside` property defaults to `false` except for the [`LongPressGesture`](/docs/2.x/gestures/long-press-gesture) and [`TapGesture`](/docs/2.x/gestures/tap-gesture) which default to `true`.
 
 ### `hitSlop(settings)`
 
 This parameter enables control over what part of the connected view area can be used to [begin](/docs/2.x/fundamentals/states-events#began) recognizing the gesture.
-When a negative number is provided the bounds of the view will reduce the area by the given number of points in each of the sides evenly.
+When a negative number is provided, the bounds of the view will reduce the area by the given number of points in each of the sides evenly.
 
 Instead you can pass an object to specify how each boundary side should be reduced by providing different number of points for `left`, `right`, `top` or `bottom` sides.
 You can alternatively provide `horizontal` or `vertical` instead of specifying directly `left`, `right` or `top` and `bottom`.
 Finally, the object can also take `width` and `height` attributes.
-When `width` is set it is only allow to specify one of the sides `right` or `left`.
+When `width` is set it is only allowed to specify one of the sides `right` or `left`.
 Similarly when `height` is provided only `top` or `bottom` can be set.
-Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In which case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognize when started no more than 20 points from the left edge.
+Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In which case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognized when started no more than 20 points from the left edge.
 
 **IMPORTANT:** Note that this parameter is primarily designed to reduce the area where gesture can activate. Hence it is only supported for all the values (except `width` and `height`) to be non positive (0 or lower). Although on Android it is supported for the values to also be positive and therefore allow to expand beyond view bounds but not further than the parent view bounds. To achieve this effect on both platforms you can use React Native's View [hitSlop](https://reactnative.dev/docs/view.html#hitslop) property.
 
@@ -61,8 +61,8 @@ Adds a relation requiring another gesture to fail, before this one can activate.
 
 Adds a relation that makes other gestures wait with activation until this gesture fails (or doesn't start at all).
 
-**IMPORTANT:** Note that this method only marks the relation between gestures, without [composing them](/docs/2.x/fundamentals/gesture-composition).[`GestureDetector`](/docs/2.x/gestures/gesture-detector) will not recognize the `otherGestures` and it needs to be added to another detector in order to be recognized.
+**IMPORTANT:** Note that this method only marks the relation between gestures, without [composing them](/docs/2.x/fundamentals/gesture-composition). [`GestureDetector`](/docs/2.x/gestures/gesture-detector) will not recognize the `otherGestures` and it needs to be added to another detector in order to be recognized.
 
 ### `activeCursor(value)` (Web only)
 
-This parameter allows to specify which cursor should be used when gesture activates. Supports all CSS cursor values (e.g. `"grab"`, `"zoom-in"`). Default value is set to `"auto"`.
+This parameter allows specifying which cursor should be used when the gesture activates. Supports all CSS cursor values (e.g. `"grab"`, `"zoom-in"`). Default value is set to `"auto"`.
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/fling-gesture.md b/packages/docs-gesture-handler/docs/legacy-gestures/fling-gesture.md
index 7a3ec0c304..faa2bffdb6 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/fling-gesture.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/fling-gesture.md
@@ -34,8 +34,8 @@ import BaseEventConfig from './\_shared/base-gesture-config.md';
 import BaseEventCallbacks from './\_shared/base-gesture-callbacks.md';
 
 A discrete gesture that activates when the movement is sufficiently long and fast.
-Gesture gets [ACTIVE](/docs/2.x/fundamentals/states-events#active) when movement is sufficiently long and it does not take too much time.
-When gesture gets activated it will turn into [END](/docs/2.x/fundamentals/states-events#end) state when finger is released.
+The gesture gets [ACTIVE](/docs/2.x/fundamentals/states-events#active) when movement is sufficiently long and it does not take too much time.
+When the gesture gets activated it will turn into [END](/docs/2.x/fundamentals/states-events#end) state when the finger is released.
 The gesture will fail to recognize if the finger is lifted before being activated.
 
   <div className={appearOnMobile} style={{ display: 'flex', justifyContent: 'center' }}>
@@ -98,7 +98,7 @@ const styles = StyleSheet.create({
 
 ### `direction(value: Directions)`
 
-Expressed allowed direction of movement. Expected values are exported as constants in the `Directions` object. It's possible to pass one or many directions in one parameter:
+Expresses the allowed direction of movement. Expected values are exported as constants in the `Directions` object. It's possible to pass one or many directions in one parameter:
 
 ```js
 import { Directions } from 'react-native-gesture-handler';
@@ -113,7 +113,7 @@ fling.direction(Directions.DOWN);
 
 ### `numberOfPointers(value: number)`
 
-Determine exact number of points required to handle the fling gesture.
+Determines the exact number of pointers required to handle the fling gesture.
 
 ### `mouseButton(value: MouseButton)` (Web & Android only)
 
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/force-touch-gesture.md b/packages/docs-gesture-handler/docs/legacy-gestures/force-touch-gesture.md
index be8eba81b6..d5a93c4d38 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/force-touch-gesture.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/force-touch-gesture.md
@@ -51,11 +51,11 @@ function App() {
 
 ### `minForce(value: number)`
 
-A minimal pressure that is required before gesture can [activate](/docs/2.x/fundamentals/states-events#active). Should be a value from range `[0.0, 1.0]`. Default is `0.2`.
+A minimal pressure that is required before the gesture can [activate](/docs/2.x/fundamentals/states-events#active). Should be a value from range `[0.0, 1.0]`. Default is `0.2`.
 
 ### `maxForce(value: number)`
 
-A maximal pressure that could be applied for gesture. If the pressure is greater, gesture [fails](/docs/2.x/fundamentals/states-events#failed). Should be a value from range `[0.0, 1.0]`.
+A maximal pressure that could be applied for the gesture. If the pressure is greater, the gesture [fails](/docs/2.x/fundamentals/states-events#failed). Should be a value from range `[0.0, 1.0]`.
 
 ### `feedbackOnActivation(value: boolean)`
 
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/gesture-composition.md b/packages/docs-gesture-handler/docs/legacy-gestures/gesture-composition.md
index 4bbdac55c7..c14255b8eb 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/gesture-composition.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/gesture-composition.md
@@ -16,7 +16,7 @@ Composing gestures is much simpler in RNGH2, you don't need to create a ref for
 Only one of the provided gestures can become active at the same time. The first gesture to become active will cancel the rest of the gestures. It accepts variable number of arguments.
 It is the equivalent to having more than one gesture handler without defining `simultaneousHandlers` and `waitFor` props.
 
-For example, lets say that you have a component that you want to make draggable but you also want to show additional options on long press. Presumably you would not want the component to move after the long press activates. You can accomplish this using `Race`:
+For example, let's say that you have a component that you want to make draggable but you also want to show additional options on long press. Presumably you would not want the component to move after the long press activates. You can accomplish this using `Race`:
 
 > Note: the `useSharedValue` and `useAnimatedStyle` are part of [`react-native-reanimated`](https://docs.swmansion.com/react-native-reanimated/).
 
@@ -93,7 +93,7 @@ function App() {
 All of the provided gestures can activate at the same time. Activation of one will not cancel the other.
 It is the equivalent to having some gesture handlers, each with `simultaneousHandlers` prop set to the other handlers.
 
-For example, if you want to make a gallery app, you might want user to be able to zoom, rotate and pan around photos. You can do it with `Simultaneous`:
+For example, if you want to make a gallery app, you might want the user to be able to zoom, rotate and pan around photos. You can do it with `Simultaneous`:
 
 > Note: the `useSharedValue` and `useAnimatedStyle` are part of [`react-native-reanimated`](https://docs.swmansion.com/react-native-reanimated/).
 
@@ -210,7 +210,7 @@ You may have noticed that gesture composition described above requires you to mo
 
 ## requireExternalGestureToFail
 
-`requireExternalGestureToFail` allows to delay activation of the handler until all handlers passed as arguments to this method fail (or don't begin at all).
+`requireExternalGestureToFail` allows delaying activation of the handler until all handlers passed as arguments to this method fail (or don't begin at all).
 
 For example, you may want to have two nested components, both of them can be tapped by the user to trigger different actions: outer view requires one tap, but the inner one requires 2 taps. If you don't want the first tap on the inner view to activate the outer handler, you must make the outer gesture wait until the inner one fails:
 
@@ -271,7 +271,7 @@ const styles = StyleSheet.create({
 
 ## blocksExternalGesture
 
-`blocksExternalGesture` works similarly to `requireExternalGestureToFail` but the direction of the relation is reversed - instead of being one-to-many relation, it's many-to-one. It's especially useful for making lists where the `ScrollView` component needs to wait for every gesture underneath it. All that's required to do is to pass a ref, for example:
+`blocksExternalGesture` works similarly to `requireExternalGestureToFail` but the direction of the relation is reversed - instead of being a one-to-many relation, it's many-to-one. It's especially useful for making lists where the `ScrollView` component needs to wait for every gesture underneath it. All that's required to do is to pass a ref, for example:
 
 ```jsx
 import React, { useRef } from 'react';
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/gesture-detector.md b/packages/docs-gesture-handler/docs/legacy-gestures/gesture-detector.md
index e1708d63d0..0df75af89b 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/gesture-detector.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/gesture-detector.md
@@ -11,7 +11,7 @@ import OldAPIInfo from './\_shared/v2-info.md'
 
 import FunctionalComponents from './\_shared/gesture-detector-functional1.md';
 
-`GestureDetector` is the main component of the RNGH2. It is responsible for creating and updating native gesture handlers based on the config of provided gesture. The most significant difference between it and old gesture handlers is that the `GestureDetector` can recognize more than one gesture at the time thanks to gesture composition. Keep in mind that `GestureDetector` is not compatible with the [Animated API](https://reactnative.dev/docs/animated), nor with [Reanimated 1](https://docs.swmansion.com/react-native-reanimated/docs/1.x/).
+`GestureDetector` is the main component of the RNGH2. It is responsible for creating and updating native gesture handlers based on the config of provided gesture. The most significant difference between it and old gesture handlers is that the `GestureDetector` can recognize more than one gesture at a time thanks to gesture composition. Keep in mind that `GestureDetector` is not compatible with the [Animated API](https://reactnative.dev/docs/animated), nor with [Reanimated 1](https://docs.swmansion.com/react-native-reanimated/docs/1.x/).
 
 ## Reference
 
@@ -37,18 +37,18 @@ function App() {
 A gesture object containing the configuration and callbacks. Can be any of the base gestures (`Tap`, `Pan`, `LongPress`, `Fling`, `Pinch`, `Rotation`, `ForceTouch`) or any [`ComposedGesture`](./composed-gestures.md) (`Race`, `Simultaneous`, `Exclusive`).
 
 :::info
-GestureDetector will decide whether to use Reanimated to process provided gestures based on callbacks they have. If any of the callbacks is a worklet, tools provided by the Reanimated will be utilized bringing ability to handle gestures synchronously.
+GestureDetector will decide whether to use Reanimated to process provided gestures based on callbacks they have. If any of the callbacks is a worklet, tools provided by the Reanimated will be utilized bringing the ability to handle gestures synchronously.
 
 Starting with Reanimated 2.3.0 Gesture Handler will provide a [StateManager](/docs/2.x/gestures/state-manager) in the [touch events](/docs/2.x/gestures/touch-events) that allows for managing the state of the gesture.
 :::
 
 ### `userSelect` (Web only)
 
-This parameter allows to specify which `userSelect` property should be applied to underlying view. Possible values are `"none" | "auto" | "text"`. Default value is set to `"none"`.
+This parameter allows specifying which `userSelect` property should be applied to the underlying view. Possible values are `"none" | "auto" | "text"`. Default value is set to `"none"`.
 
 ### `touchAction` (Web only)
 
-This parameter allows to specify which `touchAction` property should be applied to underlying view. Supports all CSS `touch-action` values (e.g. `"none"`, `"pan-y"`). Default value is set to `"none"`.
+This parameter allows specifying which `touchAction` property should be applied to the underlying view. Supports all CSS `touch-action` values (e.g. `"none"`, `"pan-y"`). Default value is set to `"none"`.
 
 ### `enableContextMenu(value: boolean)` (Web only)
 
@@ -82,4 +82,4 @@ Specifies whether context menu should be enabled after clicking on underlying vi
   }
   ```
 
-  This example will throw an error, becuse we try to use the same instance of `Pan` in two different Gesture Detectors.
+  This example will throw an error, because we try to use the same instance of `Pan` in two different Gesture Detectors.
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/native-gesture.md b/packages/docs-gesture-handler/docs/legacy-gestures/native-gesture.md
index 9764127837..038b9d65e8 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/native-gesture.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/native-gesture.md
@@ -80,7 +80,7 @@ Do not use `Native` gesture with components exported by React Native Gesture Han
 
 ### `shouldActivateOnStart(value: boolean)` (**Android only**)
 
-When `true`, underlying handler will activate unconditionally when it receives any touches in [`BEGAN`](/docs/2.x/fundamentals/states-events#began) or [`UNDETERMINED`](/docs/2.x/fundamentals/states-events#undetermined) state.
+When `true`, the underlying handler will activate unconditionally when it receives any touches in [`BEGAN`](/docs/2.x/fundamentals/states-events#began) or [`UNDETERMINED`](/docs/2.x/fundamentals/states-events#undetermined) state.
 
 ### `disallowInterruption(value: boolean)`
 
@@ -98,6 +98,6 @@ When `true`, cancels all other gesture handlers when this `NativeViewGestureHand
 
 ### `pointerInside`
 
-True if gesture was performed inside of containing view, false otherwise.
+True if the gesture was performed inside the containing view, false otherwise.
 
 <BaseEventData />
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/pan-gesture.md b/packages/docs-gesture-handler/docs/legacy-gestures/pan-gesture.md
index 8cee2377c2..082432d047 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/pan-gesture.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/pan-gesture.md
@@ -112,7 +112,7 @@ const styles = StyleSheet.create({
 
 ## Multi touch pan handling
 
-If your app relies on multi touch pan handling this section provides some information how the default behavior differs between the platform and how (if necessary) it can be unified.
+If your app relies on multi touch pan handling this section provides some information about how the default behavior differs between platforms and how (if necessary) it can be unified.
 
 The difference in multi touch pan handling lies in the way how translation properties during the event are being calculated.
 On iOS the default behavior when more than one finger is placed on the screen is to treat this situation as if only one pointer was placed in the center of mass (average position of all the pointers).
@@ -124,7 +124,7 @@ This behavior can be changed on Android using [`averageTouches`](#averagetouches
 
 Note that on both Android and iOS when the additional finger is placed on the screen that translation prop is not affected even though the position of the pointer being tracked might have changed.
 Therefore it is safe to rely on translation most of the time as it only reflects the movement that happens regardless of how many fingers are placed on the screen and if that number changes over time.
-If you wish to track the "center of mass" virtual pointer and account for its changes when the number of finger changes you can use relative or absolute position provided in the event ([`x`](#x) and [`y`](#y) or [`absoluteX`](#absolutex) and [`absoluteY`](#absolutey)).
+If you wish to track the "center of mass" virtual pointer and account for its changes when the number of fingers changes you can use relative or absolute position provided in the event ([`x`](#x) and [`y`](#y) or [`absoluteX`](#absolutex) and [`absoluteY`](#absolutey)).
 
 ## Config
 
@@ -132,15 +132,15 @@ If you wish to track the "center of mass" virtual pointer and account for its ch
 
 ### `minDistance(value: number)`
 
-Minimum distance the finger (or multiple finger) need to travel before the gesture [activates](/docs/2.x/fundamentals/states-events#active). Expressed in points.
+Minimum distance the finger (or multiple fingers) need to travel before the gesture [activates](/docs/2.x/fundamentals/states-events#active). Expressed in points.
 
 ### `minPointers(value: number)`
 
-A number of fingers that is required to be placed before gesture can [activate](/docs/2.x/fundamentals/states-events#active). Should be a higher or equal to 0 integer.
+A number of fingers that is required to be placed before the gesture can [activate](/docs/2.x/fundamentals/states-events#active). Should be a higher or equal to 0 integer.
 
 ### `maxPointers(value: number)`
 
-When the given number of fingers is placed on the screen and gesture hasn't yet [activated](/docs/2.x/fundamentals/states-events#active) it will fail recognizing the gesture. Should be a higher or equal to 0 integer.
+When the given number of fingers is placed on the screen and the gesture hasn't yet [activated](/docs/2.x/fundamentals/states-events#active) it will fail recognizing the gesture. Should be a higher or equal to 0 integer.
 
 ### `activateAfterLongPress(duration: number)`
 
@@ -148,26 +148,26 @@ Duration in milliseconds of the `LongPress` gesture before `Pan` is allowed to [
 
 ### `activeOffsetX(value: number | number[])`
 
-Range along X axis (in points) where fingers travels without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+Range along X axis (in points) where fingers travel without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `activeOffsetY(value: number | number[])`
 
-Range along Y axis (in points) where fingers travels without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+Range along Y axis (in points) where fingers travel without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `failOffsetY(value: number | number[])`
 
-When the finger moves outside this range (in points) along Y axis and gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+When the finger moves outside this range (in points) along Y axis and the gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `failOffsetX(value: number | number[])`
 
-When the finger moves outside this range (in points) along X axis and gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+When the finger moves outside this range (in points) along X axis and the gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `averageTouches(value: boolean)` (Android only)
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/pinch-gesture.md b/packages/docs-gesture-handler/docs/legacy-gestures/pinch-gesture.md
index 1010a2a4ec..8adf6fccc3 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/pinch-gesture.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/pinch-gesture.md
@@ -35,7 +35,7 @@ import BaseContinuousEventConfig from './\_shared/base-continuous-gesture-config
 import BaseEventCallbacks from './\_shared/base-gesture-callbacks.md';
 import BaseContinuousEventCallbacks from './\_shared/base-continuous-gesture-callbacks.md';
 
-A continuous gesture that recognizes pinch gesture. It allows for tracking the distance between two fingers and use that information to scale or zoom your content.
+A continuous gesture that recognizes a pinch gesture. It allows for tracking the distance between two fingers and using that information to scale or zoom your content.
 The gesture [activates](/docs/2.x/fundamentals/states-events#active) when fingers are placed on the screen and change their position.
 Gesture callback can be used for continuous tracking of the pinch gesture. It provides information about velocity, anchor (focal) point of gesture and scale.
 
@@ -121,14 +121,14 @@ The scale factor relative to the points of the two touches in screen coordinates
 
 ### `velocity`
 
-Velocity of the pan gesture the current moment. The value is expressed in scale factor per second.
+Velocity of the pinch gesture at the current moment. The value is expressed in scale factor per second.
 
 ### `focalX`
 
-Position expressed in points along X axis of center anchor point of gesture
+Position expressed in points along the X axis of the center anchor point of the gesture.
 
 ### `focalY`
 
-Position expressed in points along Y axis of center anchor point of gesture
+Position expressed in points along the Y axis of the center anchor point of the gesture.
 
 <BaseEventData />
diff --git a/packages/docs-gesture-handler/docs/legacy-gestures/state-manager.md b/packages/docs-gesture-handler/docs/legacy-gestures/state-manager.md
index 7494cb8c25..0e85a03a68 100644
--- a/packages/docs-gesture-handler/docs/legacy-gestures/state-manager.md
+++ b/packages/docs-gesture-handler/docs/legacy-gestures/state-manager.md
@@ -9,7 +9,7 @@ import OldAPIInfo from './\_shared/v2-info.md'
 
 <OldAPIInfo />
 
-`GestureStateManager` allows to manually control the state of the gestures. Please note that `react-native-reanimated` is required to use it, since it allows for synchronously executing methods in worklets.
+`GestureStateManager` allows manually controlling the state of the gestures. Please note that `react-native-reanimated` is required to use it, since it allows for synchronously executing methods in worklets.
 
 ## Methods
 
diff --git a/packages/docs-gesture-handler/docs/under-the-hood/how-does-it-work.md b/packages/docs-gesture-handler/docs/under-the-hood/how-does-it-work.md
index 135cc59043..8d54274abb 100644
--- a/packages/docs-gesture-handler/docs/under-the-hood/how-does-it-work.md
+++ b/packages/docs-gesture-handler/docs/under-the-hood/how-does-it-work.md
@@ -7,16 +7,16 @@ sidebar_label: How does it work?
 ### Units
 
 All handler component properties and event attributes that represent onscreen dimensions are expressed in screen density independent units we refer to as "points".
-These are the units commonly used in React Native ecosystem (e.g. in the [layout system](http://reactnative.dev/docs/flexbox.html)).
+These are the units commonly used in the React Native ecosystem (e.g. in the [layout system](http://reactnative.dev/docs/flexbox.html)).
 They do not map directly to physical pixels but instead to [iOS's points](https://developer.apple.com/library/content/documentation/2DDrawing/Conceptual/DrawingPrintingiOS/GraphicsDrawingOverview/GraphicsDrawingOverview.html#//apple_ref/doc/uid/TP40010156-CH14-SW7) and to [dp](https://developer.android.com/guide/topics/resources/more-resources#Dimension) units on Android.
 
 ## iOS
 
-All gestures are implemented using [UIGestureRecognizers](https://developer.apple.com/documentation/uikit/uigesturerecognizer?language=objc). Some of them have been slightly modified to allow for more customization and to conform to the [state flow](/docs/fundamentals/callbacks-events) of RNGH. When you assign a gesture configuration to the [`GestureDetector`](/docs/fundamentals/gesture-detectors), it creates all the required recognizers and assigns them to the child view of the detector. From this point most of the heavy lifting is handled by the [UIKit](https://developer.apple.com/documentation/uikit?language=objc) (with our help to correctly implement interactions between gestures).
+All gestures are implemented using [UIGestureRecognizers](https://developer.apple.com/documentation/uikit/uigesturerecognizer?language=objc). Some of them have been slightly modified to allow for more customization and to conform to the [state flow](/docs/fundamentals/callbacks-events) of RNGH. When you assign a gesture configuration to the [`GestureDetector`](/docs/fundamentals/gesture-detectors), it creates all the required recognizers and assigns them to the child view of the detector. From this point, most of the heavy lifting is handled by the [UIKit](https://developer.apple.com/documentation/uikit?language=objc) (with our help to correctly implement interactions between gestures).
 
 ## Android
 
-Unfortunately, Android doesn't provide an easy way of handling gestures hence most of them were implemented from scratch, including a system for managing how the gestures should interact with each other. Here's a quick overview of how it works:
-When you wrap a component with [`GestureHandlerRootView`](/docs/fundamentals/root-view) it allows for the RNGH to intercept all touch events on that component and process them, deciding whether they should be handled by one of the gesture handlers or passed to the underlying view. Gesture handlers are created right at the moment you declare them in order to initialize all of the necessary handlers natively. Every `GestureHandlerRootView` also has a specific handler to decide whether to pass the touch events or to consume them. It can never activate, only begin, end or be cancelled. When this handler is in the `UNDETERMINED` [state](/docs/under-the-hood/state) it means that there is no touch in progress, however when the touch starts it transitions to the `BEGAN` state. As long as it stays in that state, no touch event is consumed, but as soon as it gets cancelled (meaning that some handler has activated) all incoming touch events get consumed, preventing underlying view from receiving them.
+Unfortunately, Android doesn't provide an easy way of handling gestures, hence most of them were implemented from scratch, including a system for managing how the gestures should interact with each other. Here's a quick overview of how it works:
+When you wrap a component with [`GestureHandlerRootView`](/docs/fundamentals/root-view), it allows for the RNGH to intercept all touch events on that component and process them, deciding whether they should be handled by one of the gesture handlers or passed to the underlying view. Gesture handlers are created right at the moment you declare them in order to initialize all of the necessary handlers natively. Every `GestureHandlerRootView` also has a specific handler to decide whether to pass the touch events or to consume them. It can never activate, only begin, end or be cancelled. When this handler is in the `UNDETERMINED` [state](/docs/under-the-hood/state), it means that there is no touch in progress; however, when the touch starts it transitions to the `BEGAN` state. As long as it stays in that state, no touch event is consumed, but as soon as it gets cancelled (meaning that some handler has activated) all incoming touch events get consumed, preventing the underlying view from receiving them.
 
-When a pointer touches the screen the view tree is traversed in order to extract all handlers attached to the views below the finger (including the one attached to the `GestureHandlerRootView`) and all extracted handlers transition to the `BEGAN` state, signalling that the gesture may have began. The touch events continue to be delivered to all extracted handlers until one of them recognizes the gesture and tries to activate. At this point the orchestrator checks whether this gesture should wait for any other of the extracted gestures to fail. If it does, it's put to the waiting list, if it doesn't, it gets activated and all other gestures (that are not simultaneous with it) get cancelled. When a gesture handlers transitions to a finished state (the gesture recognized by it stops, fails or gets cancelled) the orchestrator checks the waiting handlers. Every one of them that waited for the gesture that just failed tries to activate again (and again the orchestrator checks if it should wait for any of the extracted gestures...).
+When a pointer touches the screen, the view tree is traversed in order to extract all handlers attached to the views below the finger (including the one attached to the `GestureHandlerRootView`) and all extracted handlers transition to the `BEGAN` state, signalling that the gesture may have begun. The touch events continue to be delivered to all extracted handlers until one of them recognizes the gesture and tries to activate. At this point, the orchestrator checks whether this gesture should wait for any other of the extracted gestures to fail. If it does, it's put to the waiting list, if it doesn't, it gets activated and all other gestures (that are not simultaneous with it) get cancelled. When a gesture handler transitions to a finished state (the gesture recognized by it stops, fails or gets cancelled) the orchestrator checks the waiting handlers. Every one of them that waited for the gesture that just failed tries to activate again (and again the orchestrator checks if it should wait for any of the extracted gestures...).
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/about-handlers.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/about-handlers.md
index 2865b8ff61..ba9c515446 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/about-handlers.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/about-handlers.md
@@ -5,18 +5,18 @@ sidebar_label: About Gesture Handlers
 ---
 
 Gesture handlers are the core building blocks of this library.
-We use this term to describe elements of the native touch system that the library allows us to instantiate and control from Javascript using [React's Component](https://reactjs.org/docs/react-component.html) interface.
+We use this term to describe elements of the native touch system that the library allows us to instantiate and control from JavaScript using [React's Component](https://reactjs.org/docs/react-component.html) interface.
 
 Each handler type is capable of recognizing one type of gesture (pan, pinch, etc.) and provides gesture-specific information via events (translation, scale, etc.).
 
-Handlers analyze touch stream synchronously in the UI thread. This allows for uninterrupted interactions even when the Javascript thread is blocked.
+Handlers analyze touch stream synchronously in the UI thread. This allows for uninterrupted interactions even when the JavaScript thread is blocked.
 
 Each handler works as an isolated state machine. It takes touch stream as an input and based on it, it can flip between [states](state.md).
 When a gesture starts, based on the position where the finger was placed, a set of handlers that may be interested in recognizing the gesture is selected.
 All the touch events (touch down, move, up, or when other fingers are placed or lifted) are delivered to all of the handlers selected initially.
 When one gesture becomes [active](state.md#active), it cancels all the other gestures (read more about how to influence this process in ["Cross handler interactions"](interactions.md) section).
 
-Gesture handler components do not instantiate a native view in the view hierarchy. Instead, they are kept in library's own registry and are only connected to native views. When using any of the gesture handler components, it is important for it to have a native view rendered as a child.
+Gesture handler components do not instantiate a native view in the view hierarchy. Instead, they are kept in the library's own registry and are only connected to native views. When using any of the gesture handler components, it is important for it to have a native view rendered as a child.
 Since handler components don't have corresponding views in the hierarchy, the events registered with them are actually hooked into the underlying view.
 
 ### Available gesture handlers
@@ -81,7 +81,7 @@ Here is a list of exposed components:
 - `TextInput`
 - `DrawerLayoutAndroid` (**Android only**)
 
-If you want to use other handlers or [buttons](api/components/buttons.mdx) nested in a `ScrollView`, use the [`waitFor`](api/gesture-handlers/common-gh#waitfor) property to define interaction between a handler and `ScrollView`
+If you want to use other handlers or [buttons](api/components/buttons.mdx) nested in a `ScrollView`, use the [`waitFor`](api/gesture-handlers/common-gh#waitfor) property to define the interaction between a handler and `ScrollView`.
 
 ### Events with `useNativeDriver`
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/buttons.mdx b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/buttons.mdx
index ac8657a5eb..7f7c2dbcb8 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/buttons.mdx
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/buttons.mdx
@@ -63,7 +63,7 @@ defines color of native [ripple](https://developer.android.com/reference/android
 
 ### `exclusive`
 
-defines if more than one button could be pressed simultaneously. By default set `true`.
+defines if more than one button could be pressed simultaneously. By default set to `true`.
 
 ## `RectButton`
 
@@ -95,7 +95,7 @@ opacity applied to the button when it is in an active state.
 
 ## Design patterns
 
-Components listed here were not designed to behave and look in the same way on both platforms but rather to be used for handling similar behaviour on iOS and Android taking into consideration their's design concepts.
+Components listed here were not designed to behave and look in the same way on both platforms but rather to be used for handling similar behaviour on iOS and Android taking into consideration their design concepts.
 
 If you wish to get specific information about platforms design patterns, visit [official Apple docs](https://developer.apple.com/design/human-interface-guidelines/components/menus-and-actions/buttons) and [Material.io guideline](https://material.io/components/buttons#text-button), which widely describe how to implement coherent design.
 
@@ -133,8 +133,8 @@ It should be used if you wish to handle non-crucial actions and supportive behav
 
 ### `PureNativeButton`
 
-Use a `PureNativeButton` for accessing the native Component used for build more complex buttons listed above.
-It's normally is not recommended to use, but it might be useful if we want to wrap it using Animated or Reanimated.
+Use a `PureNativeButton` for accessing the native Component used to build the more complex buttons listed above.
+It is normally not recommended to use, but it might be useful if you want to wrap it using Animated or Reanimated.
 
 ```javascript
 import {
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/drawer-layout.mdx b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/drawer-layout.mdx
index c1a426222c..d6d0dbe63a 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/drawer-layout.mdx
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/drawer-layout.mdx
@@ -61,7 +61,7 @@ color (default to `"black"`) of a semi-transparent overlay to be displayed on to
 
 ### `renderNavigationView`
 
-function. This attribute is present in the standard implementation already and is one of the required params. Gesture handler version of DrawerLayout make it possible for the function passed as `renderNavigationView` to take an Animated value as a parameter that indicates the progress of drawer opening/closing animation (progress value is 0 when closed and 1 when opened). This can be used by the drawer component to animated its children while the drawer is opening or closing.
+function. This attribute is present in the standard implementation already and is one of the required params. The gesture handler version of DrawerLayout makes it possible for the function passed as `renderNavigationView` to take an Animated value as a parameter that indicates the progress of the drawer opening/closing animation (progress value is 0 when closed and 1 when opened). This can be used by the drawer component to animated its children while the drawer is opening or closing.
 
 ### `onDrawerClose`
 
@@ -85,7 +85,7 @@ Enables two-finger gestures on supported devices, for example iPads with trackpa
 
 ### `children`
 
-component or function. Children is a component which is rendered by default and is wrapped by drawer. However, it could be also a render function which takes an Animated value as a parameter that indicates the progress of drawer opening/closing animation (progress value is 0 when closed and 1 when opened) is the same way like `renderNavigationView` prop.
+component or function. Children is a component which is rendered by default and is wrapped by drawer. However, it could also be a render function which takes an Animated value as a parameter that indicates the progress of the drawer opening/closing animation (progress value is 0 when closed and 1 when opened) in the same way as the `renderNavigationView` prop.
 
 ## Methods
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/swipeable.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/swipeable.md
index 1777a82daf..aa4ae52414 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/swipeable.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/swipeable.md
@@ -11,7 +11,7 @@ import GifGallery from '@site/components/GifGallery'
   <img src={useBaseUrl("gifs/sampleswipeable.gif")} height="120" />
 </GifGallery>
 
-This component allows for implementing swipeable rows or similar interaction. It renders its children within a panable container allows for horizontal swiping left and right. While swiping one of two "action" containers can be shown depends on whether user swipes left or right (containers can be rendered by `renderLeftActions` or `renderRightActions` props).
+This component allows for implementing swipeable rows or similar interaction. It renders its children within a pannable container that allows for horizontal swiping left and right. While swiping, one of two "action" containers can be shown depending on whether the user swipes left or right (containers can be rendered by `renderLeftActions` or `renderRightActions` props).
 
 ### Usage:
 
@@ -45,7 +45,7 @@ a boolean value indicating if the swipeable panel can be pulled further than the
 
 ### `overshootFriction`
 
-a number that specifies how much the visual interaction will be delayed compared to the gesture distance at overshoot. Default value is 1, it mean no friction, for a native feel, try 8 or above.
+a number that specifies how much the visual interaction will be delayed compared to the gesture distance at overshoot. Default value is 1, which means no friction; for a native feel, try 8 or above.
 
 ### `onSwipeableLeftOpen`
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/touchables.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/touchables.md
index 107b89695c..98883b6783 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/touchables.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/components/touchables.md
@@ -4,7 +4,7 @@ title: Touchables
 sidebar_label: Touchables
 ---
 
-Gesture Handler library provides an implementation of RN's touchable components that are based on [native buttons](buttons.mdx) and does not rely on JS responder system utilized by RN. Our touchable implementation follows the same API and aims to be a drop-in replacement for touchables available in React Native.
+Gesture Handler library provides an implementation of RN's touchable components that are based on [native buttons](buttons.mdx) and do not rely on the JS responder system utilized by RN. Our touchable implementation follows the same API and aims to be a drop-in replacement for touchables available in React Native.
 
 React Native's touchables API can be found here:
 
@@ -20,8 +20,7 @@ These touchables and their feedback behavior are deeply integrated with native
 gesture ecosystem and could be connected with other native components (e.g. `ScrollView`) and Gesture Handlers easily and in a more predictable way, which
 follows native apps' behavior.
 
-Our intention was to make switch for these touchables as simple as possible. In order to use RNGH's touchables the only thing you need to do is to change library from which you import touchable components.
-need only to change imports of touchables.
+Our intention was to make the switch for these touchables as simple as possible. In order to use RNGH's touchables, the only thing you need to do is change the library from which you import touchable components.
 
 ### Example:
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/common-gh.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/common-gh.md
index 74eb5b52d1..d96d93ab2b 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/common-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/common-gh.md
@@ -21,7 +21,7 @@ This section describes properties that can be used with all gesture handler comp
 Accepts a boolean value.
 Indicates whether the given handler should be analyzing stream of touch events or not.
 When set to `false` we can be sure that the handler's state will **never** become [`ACTIVE`](/docs/1.x/state#active).
-If the value gets updated while the handler already started recognizing a gesture, then the handler's state it will immediately change to [`FAILED`](/docs/1.x/state#failed) or [`CANCELLED`](/docs/1.x/state#cancelled) (depending on its current state).
+If the value gets updated while the handler has already started recognizing a gesture, then the handler's state will immediately change to [`FAILED`](/docs/1.x/state#failed) or [`CANCELLED`](/docs/1.x/state#cancelled) (depending on its current state).
 Default value is `true`.
 
 ### `shouldCancelWhenOutside`
@@ -47,9 +47,9 @@ When a negative number is provided the bounds of the view will reduce the area b
 Instead you can pass an object to specify how each boundary side should be reduced by providing different number of points for `left`, `right`, `top` or `bottom` sides.
 You can alternatively provide `horizontal` or `vertical` instead of specifying directly `left`, `right` or `top` and `bottom`.
 Finally, the object can also take `width` and `height` attributes.
-When `width` is set it is only allow to specify one of the sides `right` or `left`.
+When `width` is set it is only allowed to specify one of the sides `right` or `left`.
 Similarly when `height` is provided only `top` or `bottom` can be set.
-Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In which case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognize when started no more than 20 points from the left edge.
+Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In which case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognized when started no more than 20 points from the left edge.
 
 **IMPORTANT:** Note that this parameter is primarily designed to reduce the area where gesture can activate. Hence it is only supported for all the values (except `width` and `height`) to be non positive (0 or lower). Although on Android it is supported for the values to also be positive and therefore allow to expand beyond view bounds but not further than the parent view bounds. To achieve this effect on both platforms you can use React Native's View [hitSlop](https://reactnative.dev/docs/view.html#hitslop) property.
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/fling-gh.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/fling-gh.md
index 7dc4732bad..ba3ee4ac05 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/fling-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/fling-gh.md
@@ -16,7 +16,7 @@ See [set of properties inherited from base handler class](common-gh#properties).
 
 ### `direction`
 
-Expressed allowed direction of movement. It's possible to pass one or many directions in one parameter:
+Expresses the allowed direction of movement. It's possible to pass one or many directions in one parameter:
 
 ```js
 direction={Directions.RIGHT | Directions.LEFT}
@@ -30,7 +30,7 @@ direction={Directions.DOWN}
 
 ### `numberOfPointers`
 
-Determine exact number of points required to handle the fling gesture.
+Determines the exact number of pointers required to handle the fling gesture.
 
 ## Event data
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/force-gh.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/force-gh.md
index d83a38f9b2..434db4669b 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/force-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/force-gh.md
@@ -5,13 +5,13 @@ sidebar_label: Force touch
 ---
 
 A continuous gesture handler that recognizes force of a touch. It allows for tracking pressure of touch on some iOS devices.
-The handler [activates](/docs/1.x/state#active) when pressure of touch if greater or equal than `minForce`. It fails if pressure is greater than `maxForce`
+The handler [activates](/docs/1.x/state#active) when the pressure of a touch is greater than or equal to `minForce`. It fails if the pressure is greater than `maxForce`.
 Gesture callback can be used for continuous tracking of the touch pressure. It provides information for one finger (the first one).
 
 At the beginning of the gesture, the pressure factor is 0.0. As the pressure increases, the pressure factor increases proportionally. The maximum pressure is 1.0.
 
-The handler is implemented using custom [UIGestureRecognizer](https://developer.apple.com/documentation/uikit/uigesturerecognizer) on iOS. There's no implementation provided on Android and it simply render children without any wrappers.
-Since this behaviour is only provided on some iOS devices, this handler should not be used for defining any crucial behaviors. Use it only as an additional improvement and make all features to be accessed without this handler as well.
+The handler is implemented using custom [UIGestureRecognizer](https://developer.apple.com/documentation/uikit/uigesturerecognizer) on iOS. There's no implementation provided on Android and it simply renders children without any wrappers.
+Since this behaviour is only provided on some iOS devices, this handler should not be used for defining any crucial behaviors. Use it only as an additional improvement and make all features accessible without this handler as well.
 
 # Properties
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/pan-gh.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/pan-gh.md
index 3cb640b7bd..58c2b48567 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/pan-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/pan-gh.md
@@ -25,11 +25,11 @@ In such a case, if we move a finger along the X-axis by 20 points and along the
 
 ## Multi touch pan handling
 
-If your app relies on multi touch pan handling this section provides some information how the default behavior differs between the platform and how (if necessary) it can be unified.
+If your app relies on multi touch pan handling, this section provides some information about how the default behavior differs between the platforms and how (if necessary) it can be unified.
 
-The difference in multi touch pan handling lies in the way how translation properties during the event are being calculated.
+The difference in multi touch pan handling lies in the way translation properties during the event are calculated.
 On iOS the default behavior when more than one finger is placed on the screen is to treat this situation as if only one pointer was placed in the center of mass (average position of all the pointers).
-This applies also to many platform native components that handle touch even if not primarily interested in multi touch interactions like for example UIScrollView component.
+This applies also to many platform native components that handle touch even if not primarily interested in multi touch interactions, like for example the UIScrollView component.
 
 The default behavior for native components like scroll view, pager views or drawers is different and hence gesture handler defaults to that when it comes to pan handling.
 The difference is that instead of treating the center of mass of all the fingers placed as a leading pointer it takes the latest placed finger as such.
@@ -45,38 +45,38 @@ See [set of properties inherited from base handler class](common-gh#properties).
 
 ### `minDist`
 
-Minimum distance the finger (or multiple finger) need to travel before the handler [activates](/docs/1.x/state#active). Expressed in points.
+Minimum distance the finger (or multiple fingers) needs to travel before the handler [activates](/docs/1.x/state#active). Expressed in points.
 
 ### `minPointers`
 
-A number of fingers that is required to be placed before handler can [activate](/docs/1.x/state#active). Should be a higher or equal to 0 integer.
+The number of fingers that is required to be placed before the handler can [activate](/docs/1.x/state#active). Should be an integer greater than or equal to 0.
 
 ### `maxPointers`
 
-When the given number of fingers is placed on the screen and handler hasn't yet [activated](/docs/1.x/state#active) it will fail recognizing the gesture. Should be a higher or equal to 0 integer.
+When the given number of fingers is placed on the screen and the handler hasn't yet [activated](/docs/1.x/state#active) it will fail recognizing the gesture. Should be an integer greater than or equal to 0.
 
 ### `activeOffsetX`
 
-Range along X axis (in points) where fingers travels without activation of handler. Moving outside of this range implies activation of handler. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+Range along the X axis (in points) where fingers travel without activation of the handler. Moving outside of this range implies activation of the handler. Range can be given as an array or a single number.
+If the range is set as an array, the first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `activeOffsetY`
 
-Range along Y axis (in points) where fingers travels without activation of handler. Moving outside of this range implies activation of handler. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+Range along the Y axis (in points) where fingers travel without activation of the handler. Moving outside of this range implies activation of the handler. Range can be given as an array or a single number.
+If the range is set as an array, the first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `failOffsetY`
 
-When the finger moves outside this range (in points) along Y axis and handler hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+When the finger moves outside this range (in points) along the Y axis and the handler hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
+If the range is set as an array, the first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `failOffsetX`
 
-When the finger moves outside this range (in points) along X axis and handler hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+When the finger moves outside this range (in points) along the X axis and the handler hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
+If the range is set as an array, the first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `avgTouches` (Android only)
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/pinch-gh.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/pinch-gh.md
index 53c0de7063..466daa2452 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/pinch-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/api/gesture-handlers/pinch-gh.md
@@ -4,7 +4,7 @@ title: PinchGestureHandler
 sidebar_label: Pinch
 ---
 
-A continuous gesture handler that recognizes pinch gesture. It allows for tracking the distance between two fingers and use that information to scale or zoom your content.
+A continuous gesture handler that recognizes a pinch gesture. It allows for tracking the distance between two fingers and using that information to scale or zoom your content.
 The handler [activates](/docs/1.x/state#active) when fingers are placed on the screen and change their position.
 Gesture callback can be used for continuous tracking of the pinch gesture. It provides information about velocity, anchor (focal) point of gesture and scale.
 
@@ -17,7 +17,7 @@ The handler is implemented using [UIPinchGestureRecognizer](https://developer.ap
 
 ## Properties
 
-Properties provided to `PinchGestureHandler` do not extend [common set of properties from base handler class](common-gh#properties).
+Properties provided to `PinchGestureHandler` do not extend the [common set of properties from base handler class](common-gh#properties).
 
 ## Event data
 
@@ -29,15 +29,15 @@ The scale factor relative to the points of the two touches in screen coordinates
 
 ### `velocity`
 
-Velocity of the pan gesture the current moment. The value is expressed in point units per second.
+Velocity of the pinch gesture at the current moment. The value is expressed in point units per second.
 
 ### `focalX`
 
-Position expressed in points along X axis of center anchor point of gesture
+Position expressed in points along the X axis of the center anchor point of the gesture.
 
 ### `focalY`
 
-Position expressed in points along Y axis of center anchor point of gesture
+Position expressed in points along the Y axis of the center anchor point of the gesture.
 
 ## Example
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/contributing.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/contributing.md
index c3b9ab2a33..2859da7f07 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/contributing.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/contributing.md
@@ -8,7 +8,7 @@ If you are interested in the project and want to contribute or support it in oth
 All PRs are welcome, but talk to us before you start working on something big.
 
 The easiest way to get started with contributing code is by:
- - Reviewing the list of [open issues](https://github.com/software-mansion/react-native-gesture-handler/issues) and trying to solve the one that seem approachable to you.
+ - Reviewing the list of [open issues](https://github.com/software-mansion/react-native-gesture-handler/issues) and trying to solve the ones that seem approachable to you.
  - Updating the [documentation](https://github.com/software-mansion/react-native-gesture-handler/blob/main/docs) whenever you see some information is unclear, missing or out of date.
 
-Code is only one way how you can contribute. You may want to consider [replying on issues](https://github.com/software-mansion/react-native-gesture-handler/issues) if you know how to help.
+Code is only one way you can contribute. You may want to consider [replying on issues](https://github.com/software-mansion/react-native-gesture-handler/issues) if you know how to help.
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/credits.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/credits.md
index 479430f3c9..633887b056 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/credits.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/credits.md
@@ -3,7 +3,7 @@ id: credits
 title: Credits
 ---
 
-This project is supported by amazing people from [Expo.io](https://expo.io) and [Software Mansion](https://swmansion.com)
+This project is supported by amazing people from [Expo.io](https://expo.io) and [Software Mansion](https://swmansion.com).
 
 [![expo](https://avatars2.githubusercontent.com/u/12504344?v=3&s=100 "Expo.io")](https://expo.io)
 [![swm](https://avatars0.githubusercontent.com/u/56880679?v=3&s=100 "Software Mansion")](https://swmansion.com)
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/example.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/example.md
index 0c5e3b2634..80ccffaeec 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/example.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/example.md
@@ -8,7 +8,7 @@ import GifGallery from '@site/components/GifGallery'
 
 Example app code is located under [`Example/`](https://github.com/software-mansion/react-native-gesture-handler/tree/main/examples/Example) folder in the repo.
 It showcases the majority of the Gesture Handler library features.
-The app consist of the list of single screen examples presenting the capabilities of the library.
+The app consists of the list of single screen examples presenting the capabilities of the library.
 Each example is located under a separate folder under [`Example/`](https://github.com/software-mansion/react-native-gesture-handler/tree/main/examples/Example).
 
 <GifGallery>
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/getting-started.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/getting-started.md
index 8c871ae119..39248e7bbe 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/getting-started.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/getting-started.md
@@ -30,7 +30,7 @@ In a nutshell, the library provides:
 It may be possible to use newer versions of react-native-gesture-handler on React Native with version &lt;= 0.59 by reverse Jetifying.
 Read more on that here https://github.com/mikehardy/jetifier#to-reverse-jetify--convert-node_modules-dependencies-to-support-libraries
 
-Note that if you wish to use [`React.createRef()`](https://reactjs.org/docs/refs-and-the-dom.html) support for [interactions](interactions.md) you need to use v16.3 of [React](https://reactjs.org/)
+Note that if you wish to use [`React.createRef()`](https://reactjs.org/docs/refs-and-the-dom.html) support for [interactions](interactions.md) you need to use v16.3 of [React](https://reactjs.org/).
 
 ### Expo
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/interactions.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/interactions.md
index 5648e12d8e..dcfb8755dc 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/interactions.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/interactions.md
@@ -8,7 +8,7 @@ Gesture handlers can "communicate" with each other to support complex gestures a
 
 There are two means of achieving that described in the sections below.
 In each case, it is necessary to provide a reference of one handler as a property to the other.
-Gesture handler relies on ref objects created using [`React.createRef()`](https://reactjs.org/docs/refs-and-the-dom.html) and introduced in [React 16.3](https://reactjs.org/blog/2018/03/29/react-v-16-3.html#createref-api).
+Gesture handler relies on ref objects created using [`React.createRef()`](https://reactjs.org/docs/refs-and-the-dom.html), introduced in [React 16.3](https://reactjs.org/blog/2018/03/29/react-v-16-3.html#createref-api).
 
 ## Simultaneous recognition
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/state.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/state.md
index c8abeb0f47..80ce22c041 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/state.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/state.md
@@ -68,7 +68,7 @@ This is the initial state of each handler and it goes into this state after it's
 
 ### FAILED
 
-A handler received some touches but for some reason didn't recognize them. For example, if a finger travels more distance than a defined `maxDist` property allows, then the handler won't become active but will fail instead. Afterwards, it's state will be reset to `UNDETERMINED`.
+A handler received some touches but for some reason didn't recognize them. For example, if a finger travels more distance than a defined `maxDist` property allows, then the handler won't become active but will fail instead. Afterwards, its state will be reset to `UNDETERMINED`.
 
 ### BEGAN
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-1.x/troubleshooting.md b/packages/docs-gesture-handler/versioned_docs/version-1.x/troubleshooting.md
index 6d3496f132..cde902b422 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-1.x/troubleshooting.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-1.x/troubleshooting.md
@@ -20,8 +20,8 @@ Thanks for giving this library a try! We are sorry that you might have encounter
 ## Reporting issues
 
 This library is maintained by a very small team.
-Please be mindful of that when reporting issue and when it happens that we can't get back to you as soon as you might expect.
-We would love to fix all the problems as soon as possible, but often our time is constraint with other issues/features or projects.
+Please be mindful of that when reporting an issue and when it happens that we can't get back to you as soon as you might expect.
+We would love to fix all the problems as soon as possible, but often our time is constrained by other issues/features or projects.
 To make it easier for us to understand your issue and to be able to approach it sooner you can help by:
  - Making sure the issue description is complete. Please include all the details about your environment (library version, RN version, device OS etc).
  - It is the best to provide an example app that reproduces the issue you are having. Put it up on [gist](https://gist.github.com/), [snack](https://snack.expo.io) or create a repo on Github – it doesn't matter as long as we can easily pull it in, run and see the issue.
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/components/buttons.mdx b/packages/docs-gesture-handler/versioned_docs/version-2.x/components/buttons.mdx
index cde390a556..dc7784686a 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/components/buttons.mdx
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/components/buttons.mdx
@@ -103,7 +103,7 @@ opacity applied to the button when it is in an active state.
 
 ## Design patterns
 
-Components listed here were not designed to behave and look in the same way on both platforms but rather to be used for handling similar behaviour on iOS and Android taking into consideration their's design concepts.
+Components listed here were not designed to behave and look in the same way on both platforms but rather to be used for handling similar behaviour on iOS and Android taking into consideration their design concepts.
 
 If you wish to get specific information about platforms design patterns, visit [official Apple docs](https://developer.apple.com/design/human-interface-guidelines/components/menus-and-actions/buttons) and [Material.io guideline](https://material.io/components/buttons#text-button), which widely describe how to implement coherent design.
 
@@ -141,8 +141,8 @@ It should be used if you wish to handle non-crucial actions and supportive behav
 
 ### `PureNativeButton`
 
-Use a `PureNativeButton` for accessing the native Component used for build more complex buttons listed above.
-It's normally is not recommended to use, but it might be useful if we want to wrap it using Animated or Reanimated.
+Use a `PureNativeButton` for accessing the native Component used for building more complex buttons listed above.
+It is normally not recommended to use, but it might be useful if we want to wrap it using Animated or Reanimated.
 
 ```javascript
 import {
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/components/reanimated_swipeable.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/components/reanimated_swipeable.md
index bbf58d07fc..cdc0b3b908 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/components/reanimated_swipeable.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/components/reanimated_swipeable.md
@@ -15,7 +15,7 @@ import GifGallery from '@site/components/GifGallery'
 This component is a drop-in replacement for the `Swipeable` component, rewritten using `Reanimated`.
 :::
 
-Reanimated `Swipeable` allows for implementing swipeable rows or similar interaction. It renders its children within a panable container allows for horizontal swiping left and right. While swiping one of two "action" containers can be shown depends on whether user swipes left or right (containers can be rendered by `renderLeftActions` or `renderRightActions` props).
+Reanimated `Swipeable` allows for implementing swipeable rows or similar interaction. It renders its children within a pannable container and allows for horizontal swiping left and right. While swiping, one of two "action" containers can be shown depending on whether the user swipes left or right (containers can be rendered by `renderLeftActions` or `renderRightActions` props).
 
 ### Usage:
 
@@ -58,7 +58,7 @@ a boolean value indicating if the swipeable panel can be pulled further than the
 
 ### `overshootFriction`
 
-a number that specifies how much the visual interaction will be delayed compared to the gesture distance at overshoot. Default value is `1`, it mean no friction, for a native feel, try `8` or above.
+a number that specifies how much the visual interaction will be delayed compared to the gesture distance at overshoot. Default value is `1`, it means no friction, for a native feel, try `8` or above.
 
 ### `onSwipeableOpen`
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/components/touchables.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/components/touchables.md
index 6d1f19107f..33cb26d037 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/components/touchables.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/components/touchables.md
@@ -24,8 +24,7 @@ These touchables and their feedback behavior are deeply integrated with native
 gesture ecosystem and could be connected with other native components (e.g. `ScrollView`) and Gesture Handlers easily and in a more predictable way, which
 follows native apps' behavior.
 
-Our intention was to make switch for these touchables as simple as possible. In order to use RNGH's touchables the only thing you need to do is to change library from which you import touchable components.
-need only to change imports of touchables.
+Our intention was to make switch for these touchables as simple as possible. In order to use RNGH's touchables the only thing you need to do is to change the library from which you import touchable components.
 
 :::info
 Gesture Handler's TouchableOpacity uses native driver for animations by default. If this causes problems for you, you can set `useNativeAnimations` prop to false.
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/gesture-composition.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/gesture-composition.md
index 31657f617c..6ef1b852de 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/gesture-composition.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/gesture-composition.md
@@ -12,7 +12,7 @@ Composing gestures is much simpler in RNGH2, you don't need to create a ref for
 Only one of the provided gestures can become active at the same time. The first gesture to become active will cancel the rest of the gestures. It accepts variable number of arguments.
 It is the equivalent to having more than one gesture handler without defining `simultaneousHandlers` and `waitFor` props.
 
-For example, lets say that you have a component that you want to make draggable but you also want to show additional options on long press. Presumably you would not want the component to move after the long press activates. You can accomplish this using `Race`:
+For example, let's say that you have a component that you want to make draggable but you also want to show additional options on long press. Presumably you would not want the component to move after the long press activates. You can accomplish this using `Race`:
 
 > Note: the `useSharedValue` and `useAnimatedStyle` are part of [`react-native-reanimated`](https://docs.swmansion.com/react-native-reanimated/).
 
@@ -206,7 +206,7 @@ You may have noticed that gesture composition described above requires you to mo
 
 ## requireExternalGestureToFail
 
-`requireExternalGestureToFail` allows to delay activation of the handler until all handlers passed as arguments to this method fail (or don't begin at all).
+`requireExternalGestureToFail` allows delaying activation of the handler until all handlers passed as arguments to this method fail (or don't begin at all).
 
 For example, you may want to have two nested components, both of them can be tapped by the user to trigger different actions: outer view requires one tap, but the inner one requires 2 taps. If you don't want the first tap on the inner view to activate the outer handler, you must make the outer gesture wait until the inner one fails:
 
@@ -267,7 +267,7 @@ const styles = StyleSheet.create({
 
 ## blocksExternalGesture
 
-`blocksExternalGesture` works similarly to `requireExternalGestureToFail` but the direction of the relation is reversed - instead of being one-to-many relation, it's many-to-one. It's especially useful for making lists where the `ScrollView` component needs to wait for every gesture underneath it. All that's required to do is to pass a ref, for example:
+`blocksExternalGesture` works similarly to `requireExternalGestureToFail` but the direction of the relation is reversed - instead of being a one-to-many relation, it's many-to-one. It's especially useful for making lists where the `ScrollView` component needs to wait for every gesture underneath it. All that is required to do is to pass a ref, for example:
 
 ```jsx
 import React, { useRef } from 'react';
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/introduction.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/introduction.md
index f7dc0376d9..56f37197b2 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/introduction.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/introduction.md
@@ -18,7 +18,7 @@ The main benefits of using React Native Gesture Handler are:
 - Ability to include any native component into the Gesture Handler's touch system, making it work alongside your gestures.
 
 :::info
-We recommended to use Reanimated to implement gesture-driven animations with Gesture Handler. Its more advanced features rely heavily on worklets and the UI runtime provided by Reanimated.
+We recommend using Reanimated to implement gesture-driven animations with Gesture Handler. Its more advanced features rely heavily on worklets and the UI runtime provided by Reanimated.
 :::
 
 ## Learning resources
@@ -52,7 +52,7 @@ Code is only one way how you can contribute. You may want to consider [replying
 
 ## Community
 
-We are very proud of the community that has been build around this package. We really appreciate all your help regardless of it is a pull request, issue report, helping others by commenting on existing issues or posting some demo or video tutorial on social media.
+We are very proud of the community that has been build around this package. We really appreciate all your help regardless of whether it is a pull request, issue report, helping others by commenting on existing issues or posting some demo or video tutorial on social media.
 If you've build something with this library you'd like to share, please contact us as we'd love to help share it with others.
 
 ### Gesture Handler Team 🚀
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/states-events.mdx b/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/states-events.mdx
index 26df3bcd92..55d4214610 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/states-events.mdx
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/fundamentals/states-events.mdx
@@ -16,7 +16,7 @@ A gesture can be in one of the six possible states:
 
 - #### FAILED
 
-  A gesture recognizer received some touches but for some reason didn't recognize them. For example, if a finger travels more distance than a defined `maxDist` property allows, then the gesture won't become active but will fail instead. Afterwards, it's state will be reset to `UNDETERMINED`.
+  A gesture recognizer received some touches but for some reason didn't recognize them. For example, if a finger travels more distance than a defined `maxDist` property allows, then the gesture won't become active but will fail instead. Afterwards, its state will be reset to `UNDETERMINED`.
 
 - #### BEGAN
 
@@ -50,7 +50,7 @@ import GestureStateFlowExample from '@site/src/examples/GestureStateFlowExample'
 
 ## Events
 
-There are three types of events in RNGH2: `StateChangeEvent`, `GestureEvent` and `PointerEvent`. The `StateChangeEvent` is send every time a gesture moves to a different state, while `GestureEvent` is send every time a gesture is updated. The first two carry a gesture-specific data and a `state` property, indicating the current state of the gesture. `StateChangeEvent` also carries a `oldState` property indicating the previous state of the gesture. `PointerEvent` carries information about raw touch events, like touching the screen or moving the finger. These events are handled internally before they are passed along to the correct callbacks:
+There are three types of events in RNGH2: `StateChangeEvent`, `GestureEvent` and `PointerEvent`. The `StateChangeEvent` is sent every time a gesture moves to a different state, while `GestureEvent` is sent every time a gesture is updated. The first two carry a gesture-specific data and a `state` property, indicating the current state of the gesture. `StateChangeEvent` also carries a `oldState` property indicating the previous state of the gesture. `PointerEvent` carries information about raw touch events, like touching the screen or moving the finger. These events are handled internally before they are passed along to the correct callbacks:
 
 ### `onBegin`
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/about-handlers.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/about-handlers.md
index 6565c773a2..8398611ca8 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/about-handlers.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/about-handlers.md
@@ -10,18 +10,18 @@ The old API will be removed in the future version of Gesture Handler. Please mig
 :::
 
 Gesture handlers are the core building blocks of this library.
-We use this term to describe elements of the native touch system that the library allows us to instantiate and control from Javascript using [React's Component](https://reactjs.org/docs/react-component.html) interface.
+We use this term to describe elements of the native touch system that the library allows us to instantiate and control from JavaScript using [React's Component](https://reactjs.org/docs/react-component.html) interface.
 
 Each handler type is capable of recognizing one type of gesture (pan, pinch, etc.) and provides gesture-specific information via events (translation, scale, etc.).
 
-Handlers analyze touch stream synchronously in the UI thread. This allows for uninterrupted interactions even when the Javascript thread is blocked.
+Handlers analyze the touch stream synchronously in the UI thread. This allows for uninterrupted interactions even when the JavaScript thread is blocked.
 
-Each handler works as an isolated state machine. It takes touch stream as an input and based on it, it can flip between [states](/docs/2.x/under-the-hood/state).
+Each handler works as an isolated state machine. It takes a touch stream as an input and based on it, it can flip between [states](/docs/2.x/under-the-hood/state).
 When a gesture starts, based on the position where the finger was placed, a set of handlers that may be interested in recognizing the gesture is selected.
 All the touch events (touch down, move, up, or when other fingers are placed or lifted) are delivered to all of the handlers selected initially.
 When one gesture becomes [active](/docs/2.x/under-the-hood/state#active), it cancels all the other gestures (read more about how to influence this process in ["Cross handler interactions"](/docs/2.x/gesture-handlers/interactions) section).
 
-Gesture handler components do not instantiate a native view in the view hierarchy. Instead, they are kept in library's own registry and are only connected to native views. When using any of the gesture handler components, it is important for it to have a native view rendered as a child.
+Gesture handler components do not instantiate a native view in the view hierarchy. Instead, they are kept in the library's own registry and are only connected to native views. When using any of the gesture handler components, it is important for it to have a native view rendered as a child.
 Since handler components don't have corresponding views in the hierarchy, the events registered with them are actually hooked into the underlying view.
 
 ### Available gesture handlers
@@ -46,11 +46,11 @@ An example of a continuous handler is [`PanGestureHandler`](/docs/2.x/gesture-ha
 On the other hand, discrete gesture handlers once [activated](/docs/2.x/under-the-hood/state#active) will not stay in the active state but will [end](/docs/2.x/under-the-hood/state#ended) immediately.
 [`LongPressGestureHandler`](/docs/2.x/gesture-handlers/longpress-gh) is a discrete handler, as it only detects if the finger is placed for a sufficiently long period of time, it does not track finger movements (as that's the responsibility of [`PanGestureHandler`](/docs/2.x/gesture-handlers/pan-gh)).
 
-Keep in mind that `onGestureEvent` is only generated in continuous gesture handlers and shouldn't be used in the `TapGestureHandler` and other discrete handlers.
+Keep in mind that `onGestureEvent` is only generated by continuous gesture handlers and shouldn't be used in the `TapGestureHandler` and other discrete handlers.
 
 ### Nesting handlers
 
-Handler components can be nested. In any case it is recommended that the innermost handler renders a native view component. There are some limitations that apply when [using `useNativeDriver` flag](#events-with-usenativedriver). An example of nested handlers:
+Handler components can be nested. In any case, it is recommended that the innermost handler renders a native view component. There are some limitations that apply when [using `useNativeDriver` flag](#events-with-usenativedriver). An example of nested handlers:
 
 ```js
 class Multitap extends Component {
@@ -86,7 +86,7 @@ Here is a list of exposed components:
 - `TextInput`
 - `DrawerLayoutAndroid` (**Android only**)
 
-If you want to use other handlers or [buttons](/docs/2.x/components/buttons) nested in a `ScrollView`, use the [`waitFor`](/docs/2.x/gesture-handlers/common-gh#waitfor) property to define interaction between a handler and `ScrollView`
+If you want to use other handlers or [buttons](/docs/2.x/components/buttons) nested in a `ScrollView`, use the [`waitFor`](/docs/2.x/gesture-handlers/common-gh#waitfor) property to define interaction between a handler and `ScrollView`.
 
 ### Events with `useNativeDriver`
 
@@ -119,7 +119,7 @@ const PanAndRotate = () => (
 );
 ```
 
-Another consequence of handlers depending on their native child components is that when using a `useNativeDriver` flag with an `Animated.event`, the child component must be wrapped by an `Animated.API` e.g. `<Animated.View>` instead of just a `<View>`:
+Another consequence of handlers depending on their native child components is that when using a `useNativeDriver` flag with an `Animated.event`, the child component must be wrapped by an `Animated.API`, e.g. `<Animated.View>` instead of just a `<View>`:
 
 ```js
 class Draggable extends Component {
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/common-gh.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/common-gh.md
index 0133c4e096..3847b6eff5 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/common-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/common-gh.md
@@ -26,7 +26,7 @@ This section describes properties that can be used with all gesture handler comp
 Accepts a boolean value.
 Indicates whether the given handler should be analyzing stream of touch events or not.
 When set to `false` we can be sure that the handler's state will **never** become [`ACTIVE`](/docs/2.x/under-the-hood/state#active).
-If the value gets updated while the handler already started recognizing a gesture, then the handler's state it will immediately change to [`FAILED`](/docs/2.x/under-the-hood/state#failed) or [`CANCELLED`](/docs/2.x/under-the-hood/state#cancelled) (depending on its current state).
+If the value gets updated while the handler has already started recognizing a gesture, then the handler's state will immediately change to [`FAILED`](/docs/2.x/under-the-hood/state#failed) or [`CANCELLED`](/docs/2.x/under-the-hood/state#cancelled) (depending on its current state).
 Default value is `true`.
 
 ### `shouldCancelWhenOutside`
@@ -48,19 +48,19 @@ Accepts a react ref object or an array of refs to other handler components (refs
 
 ### `waitFor`
 
-Accepts a react ref object or an array of refs to other handler components (refs should be created using [`React.createRef()`](https://reactjs.org/docs/refs-and-the-dom.html)). When set the handler will not [activate](/docs/2.x/under-the-hood/state#active) as long as the handlers provided by their refs are in the [`BEGAN`](/docs/2.x/under-the-hood/state#began) state. Read more in the [cross handler interaction](/docs/2.x/gesture-handlers/interactions#awaiting-other-handlers) section.
+Accepts a react ref object or an array of refs to other handler components (refs should be created using [`React.createRef()`](https://reactjs.org/docs/refs-and-the-dom.html)). When set, the handler will not [activate](/docs/2.x/under-the-hood/state#active) as long as the handlers provided by their refs are in the [`BEGAN`](/docs/2.x/under-the-hood/state#began) state. Read more in the [cross handler interaction](/docs/2.x/gesture-handlers/interactions#awaiting-other-handlers) section.
 
 ### `hitSlop`
 
 This parameter enables control over what part of the connected view area can be used to [begin](/docs/2.x/under-the-hood/state#began) recognizing the gesture.
 When a negative number is provided the bounds of the view will reduce the area by the given number of points in each of the sides evenly.
 
-Instead you can pass an object to specify how each boundary side should be reduced by providing different number of points for `left`, `right`, `top` or `bottom` sides.
+Instead, you can pass an object to specify how each boundary side should be reduced by providing a different number of points for `left`, `right`, `top` or `bottom` sides.
 You can alternatively provide `horizontal` or `vertical` instead of specifying directly `left`, `right` or `top` and `bottom`.
 Finally, the object can also take `width` and `height` attributes.
-When `width` is set it is only allow to specify one of the sides `right` or `left`.
+When `width` is set it is only allowed to specify one of the sides `right` or `left`.
 Similarly when `height` is provided only `top` or `bottom` can be set.
-Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In which case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognize when started no more than 20 points from the left edge.
+Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In which case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognized when started no more than 20 points from the left edge.
 
 **IMPORTANT:** Note that this parameter is primarily designed to reduce the area where gesture can activate. Hence it is only supported for all the values (except `width` and `height`) to be non positive (0 or lower). Although on Android it is supported for the values to also be positive and therefore allow to expand beyond view bounds but not further than the parent view bounds. To achieve this effect on both platforms you can use React Native's View [hitSlop](https://reactnative.dev/docs/view.html#props) property.
 
@@ -74,7 +74,7 @@ This parameter allows to specify which cursor should be used when gesture activa
 
 ### `onGestureEvent`
 
-Takes a callback that is going to be triggered for each subsequent touch event while the handler is in an [ACTIVE](/docs/2.x/under-the-hood/state#active) state. Event payload depends on the particular handler type. Common set of event data attributes is documented [below](#event-data) and handler specific attributes are documented on the corresponding handler pages. E.g. event payload for [`PinchGestureHandler`](/docs/2.x/gesture-handlers/rotation-gh#event-data) contains `scale` attribute that represents how the distance between fingers changed since when the gesture started.
+Takes a callback that is going to be triggered for each subsequent touch event while the handler is in an [ACTIVE](/docs/2.x/under-the-hood/state#active) state. Event payload depends on the particular handler type. Common set of event data attributes is documented [below](#event-data) and handler specific attributes are documented on the corresponding handler pages. E.g. event payload for [`PinchGestureHandler`](/docs/2.x/gesture-handlers/rotation-gh#event-data) contains a `scale` attribute that represents how the distance between fingers changed since the gesture started.
 
 Instead of a callback [`Animated.event`](https://reactnative.dev/docs/animated.html#event) object can be used. Also Animated events with `useNativeDriver` flag enabled **are fully supported**.
 
@@ -82,7 +82,7 @@ Instead of a callback [`Animated.event`](https://reactnative.dev/docs/animated.h
 
 Takes a callback that is going to be triggered when [state](/docs/2.x/under-the-hood/state) of the given handler changes.
 
-The event payload contains the same payload as in case of [`onGestureEvent`](#ongestureevent) including handler specific event attributes some handlers may provide.
+The event payload contains the same payload as in the case of [`onGestureEvent`](#ongestureevent) including handler specific event attributes some handlers may provide.
 
 In addition `onHandlerStateChange` event payload contains `oldState` attribute which represents the [state](/docs/2.x/under-the-hood/state) of the handler right before the change.
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/fling-gh.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/fling-gh.md
index 171f43087d..4b332e0bf8 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/fling-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/fling-gh.md
@@ -21,7 +21,7 @@ See [set of properties inherited from base handler class](/docs/2.x/gesture-hand
 
 ### `direction`
 
-Expressed allowed direction of movement. It's possible to pass one or many directions in one parameter:
+Expresses the allowed direction of movement. It's possible to pass one or many directions in one parameter:
 
 ```js
 direction={Directions.RIGHT | Directions.LEFT}
@@ -35,7 +35,7 @@ direction={Directions.DOWN}
 
 ### `numberOfPointers`
 
-Determine exact number of points required to handle the fling gesture.
+Determines the exact number of pointers required to handle the fling gesture.
 
 ## Event data
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/force-gh.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/force-gh.md
index 110ca1780d..20bea950a9 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/force-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/force-gh.md
@@ -10,12 +10,12 @@ The old API will be removed in the future version of Gesture Handler. Please mig
 :::
 
 A continuous gesture handler that recognizes force of a touch. It allows for tracking pressure of touch on some iOS devices.
-The handler [activates](/docs/2.x/under-the-hood/state#active) when pressure of touch if greater or equal than `minForce`. It fails if pressure is greater than `maxForce`
+The handler [activates](/docs/2.x/under-the-hood/state#active) when pressure of touch is greater or equal to `minForce`. It fails if pressure is greater than `maxForce`.
 Gesture callback can be used for continuous tracking of the touch pressure. It provides information for one finger (the first one).
 
 At the beginning of the gesture, the pressure factor is 0.0. As the pressure increases, the pressure factor increases proportionally. The maximum pressure is 1.0.
 
-The handler is implemented using custom [UIGestureRecognizer](https://developer.apple.com/documentation/uikit/uigesturerecognizer) on iOS. There's no implementation provided on Android and it simply render children without any wrappers.
+The handler is implemented using custom [UIGestureRecognizer](https://developer.apple.com/documentation/uikit/uigesturerecognizer) on iOS. There's no implementation provided on Android and it simply renders children without any wrappers.
 Since this behaviour is only provided on some iOS devices, this handler should not be used for defining any crucial behaviors. Use it only as an additional improvement and make all features to be accessed without this handler as well.
 
 # Properties
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/interactions.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/interactions.md
index e225e0e2b0..83d2eb4db9 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/interactions.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/interactions.md
@@ -13,7 +13,7 @@ Gesture handlers can "communicate" with each other to support complex gestures a
 
 There are two means of achieving that described in the sections below.
 In each case, it is necessary to provide a reference of one handler as a property to the other.
-Gesture handler relies on ref objects created using [`React.createRef()`](https://reactjs.org/docs/refs-and-the-dom.html) and introduced in [React 16.3](https://reactjs.org/blog/2018/03/29/react-v-16-3.html#createref-api).
+Gesture handler relies on ref objects created using [`React.createRef()`](https://reactjs.org/docs/refs-and-the-dom.html), introduced in [React 16.3](https://reactjs.org/blog/2018/03/29/react-v-16-3.html#createref-api).
 
 ## Simultaneous recognition
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/pan-gh.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/pan-gh.md
index 3cf8218652..de3bbfeb1e 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/pan-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/pan-gh.md
@@ -30,11 +30,11 @@ In such a case, if we move a finger along the X-axis by 20 points and along the
 
 ## Multi touch pan handling
 
-If your app relies on multi touch pan handling this section provides some information how the default behavior differs between the platform and how (if necessary) it can be unified.
+If your app relies on multi touch pan handling this section provides some information about how the default behavior differs between platforms and how (if necessary) it can be unified.
 
-The difference in multi touch pan handling lies in the way how translation properties during the event are being calculated.
+The difference in multi touch pan handling lies in the way translation properties during the event are being calculated.
 On iOS the default behavior when more than one finger is placed on the screen is to treat this situation as if only one pointer was placed in the center of mass (average position of all the pointers).
-This applies also to many platform native components that handle touch even if not primarily interested in multi touch interactions like for example UIScrollView component.
+This applies also to many platform native components that handle touch even if not primarily interested in multi touch interactions, like for example the UIScrollView component.
 
 The default behavior for native components like scroll view, pager views or drawers is different and hence gesture handler defaults to that when it comes to pan handling.
 The difference is that instead of treating the center of mass of all the fingers placed as a leading pointer it takes the latest placed finger as such.
@@ -54,34 +54,34 @@ Minimum distance the finger (or multiple finger) need to travel before the handl
 
 ### `minPointers`
 
-A number of fingers that is required to be placed before handler can [activate](/docs/2.x/under-the-hood/state#active). Should be a higher or equal to 0 integer.
+A number of fingers that is required to be placed before the handler can [activate](/docs/2.x/under-the-hood/state#active). Should be a higher or equal to 0 integer.
 
 ### `maxPointers`
 
-When the given number of fingers is placed on the screen and handler hasn't yet [activated](/docs/2.x/under-the-hood/state#active) it will fail recognizing the gesture. Should be a higher or equal to 0 integer.
+When the given number of fingers is placed on the screen and the handler hasn't yet [activated](/docs/2.x/under-the-hood/state#active) it will fail recognizing the gesture. Should be a higher or equal to 0 integer.
 
 ### `activeOffsetX`
 
 Range along X axis (in points) where fingers travels without activation of handler. Moving outside of this range implies activation of handler. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `activeOffsetY`
 
 Range along Y axis (in points) where fingers travels without activation of handler. Moving outside of this range implies activation of handler. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `failOffsetY`
 
 When the finger moves outside this range (in points) along Y axis and handler hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `failOffsetX`
 
 When the finger moves outside this range (in points) along X axis and handler hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+If range is set as an array, first value must be lower or equal to 0, and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `maxDeltaX`
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/pinch-gh.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/pinch-gh.md
index c1b52f36d8..3b7f8ec65b 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/pinch-gh.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gesture-handlers/pinch-gh.md
@@ -34,15 +34,15 @@ The scale factor relative to the points of the two touches in screen coordinates
 
 ### `velocity`
 
-Velocity of the pan gesture the current moment. The value is expressed in scale factor per second.
+Velocity of the pinch gesture at the current moment. The value is expressed in scale factor per second.
 
 ### `focalX`
 
-Position expressed in points along X axis of center anchor point of gesture
+Position expressed in points along X axis of center anchor point of the gesture.
 
 ### `focalY`
 
-Position expressed in points along Y axis of center anchor point of gesture
+Position expressed in points along Y axis of center anchor point of the gesture.
 
 ## Example
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-callbacks.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-callbacks.md
index dff985b307..a898f7b85e 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-callbacks.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-callbacks.md
@@ -2,7 +2,7 @@
 
 ### `onBegin(callback)`
 
-Set the callback that is being called when given gesture handler starts receiving touches. At the moment of this callback the handler is not yet in an active state and we don't know yet if it will recognize the gesture at all.
+Set the callback that is being called when the given gesture handler starts receiving touches. At the moment of this callback the handler is not yet in an active state and we don't know yet if it will recognize the gesture at all.
 
 ### `onStart(callback)`
 
@@ -14,7 +14,7 @@ Set the callback that is being called when the gesture that was recognized by th
 
 ### `onFinalize(callback)`
 
-Set the callback that is being called when the handler finalizes handling gesture - the gesture was recognized and has finished or it failed to recognize.
+Set the callback that is being called when the handler finalizes handling the gesture - the gesture was recognized and has finished or it failed to recognize.
 
 ### `onTouchesDown(callback)`
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-config.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-config.md
index 6a39d4cb75..b91cbb4f6a 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-config.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-config.md
@@ -4,7 +4,7 @@
 
 Indicates whether the given handler should be analyzing stream of touch events or not.
 When set to `false` we can be sure that the handler's state will **never** become [`ACTIVE`](/docs/2.x/fundamentals/states-events#active).
-If the value gets updated while the handler already started recognizing a gesture, then the handler's state it will immediately change to [`FAILED`](/docs/2.x/fundamentals/states-events#failed) or [`CANCELLED`](/docs/2.x/fundamentals/states-events#cancelled) (depending on its current state).
+If the value gets updated while the handler already started recognizing a gesture, then the handler's state will immediately change to [`FAILED`](/docs/2.x/fundamentals/states-events#failed) or [`CANCELLED`](/docs/2.x/fundamentals/states-events#cancelled) (depending on its current state).
 Default value is `true`.
 
 ### `shouldCancelWhenOutside(value: boolean)`
@@ -21,9 +21,9 @@ When a negative number is provided the bounds of the view will reduce the area b
 Instead you can pass an object to specify how each boundary side should be reduced by providing different number of points for `left`, `right`, `top` or `bottom` sides.
 You can alternatively provide `horizontal` or `vertical` instead of specifying directly `left`, `right` or `top` and `bottom`.
 Finally, the object can also take `width` and `height` attributes.
-When `width` is set it is only allow to specify one of the sides `right` or `left`.
+When `width` is set it is only allowed to specify one of the sides `right` or `left`.
 Similarly when `height` is provided only `top` or `bottom` can be set.
-Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In which case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognize when started no more than 20 points from the left edge.
+Specifying `width` or `height` is useful if we only want the gesture to activate on the edge of the view. In which case for example we can set `left: 0` and `width: 20` which would make it possible for the gesture to be recognized when started no more than 20 points from the left edge.
 
 **IMPORTANT:** Note that this parameter is primarily designed to reduce the area where gesture can activate. Hence it is only supported for all the values (except `width` and `height`) to be non positive (0 or lower). Although on Android it is supported for the values to also be positive and therefore allow to expand beyond view bounds but not further than the parent view bounds. To achieve this effect on both platforms you can use React Native's View [hitSlop](https://reactnative.dev/docs/view.html#hitslop) property.
 
@@ -61,7 +61,7 @@ Adds a relation requiring another gesture to fail, before this one can activate.
 
 Adds a relation that makes other gestures wait with activation until this gesture fails (or doesn't start at all).
 
-**IMPORTANT:** Note that this method only marks the relation between gestures, without [composing them](/docs/2.x/fundamentals/gesture-composition).[`GestureDetector`](/docs/2.x/gestures/gesture-detector) will not recognize the `otherGestures` and it needs to be added to another detector in order to be recognized.
+**IMPORTANT:** Note that this method only marks the relation between gestures, without [composing them](/docs/2.x/fundamentals/gesture-composition). [`GestureDetector`](/docs/2.x/gestures/gesture-detector) will not recognize the `otherGestures` and it needs to be added to another detector in order to be recognized.
 
 ### `activeCursor(value)` (Web only)
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-event-data.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-event-data.md
index 674f2fb478..21da18e191 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-event-data.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/_shared/base-gesture-event-data.md
@@ -12,8 +12,8 @@ Represents the number of pointers (fingers) currently placed on the screen.
 
 Indicates the type of pointer device in use. This value is represented by the `PointerType` enum, which includes the following fields:
 
-- `TOUCH` - represents finger
-- `STYLUS` - represents stylus or digital pen
-- `MOUSE` - represents computer mouse
-- `KEY` - represents keyboard
-- `OTHER` - represents unknown device type that is not relevant
+- `TOUCH` - represents a finger
+- `STYLUS` - represents a stylus or digital pen
+- `MOUSE` - represents a computer mouse
+- `KEY` - represents a keyboard
+- `OTHER` - represents an unknown device type that is not relevant
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/fling-gesture.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/fling-gesture.md
index 58a6812429..0be6223d9c 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/fling-gesture.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/fling-gesture.md
@@ -94,7 +94,7 @@ const styles = StyleSheet.create({
 
 ### `direction(value: Directions)`
 
-Expressed allowed direction of movement. Expected values are exported as constants in the `Directions` object. It's possible to pass one or many directions in one parameter:
+Expresses the allowed direction of movement. Expected values are exported as constants in the `Directions` object. It's possible to pass one or many directions in one parameter:
 
 ```js
 import { Directions } from 'react-native-gesture-handler';
@@ -109,7 +109,7 @@ fling.direction(Directions.DOWN);
 
 ### `numberOfPointers(value: number)`
 
-Determine exact number of points required to handle the fling gesture.
+Determines the exact number of pointers required to handle the fling gesture.
 
 ### `mouseButton(value: MouseButton)` (Web & Android only)
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/force-touch-gesture.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/force-touch-gesture.md
index 8227c7dea2..debe180df8 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/force-touch-gesture.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/force-touch-gesture.md
@@ -22,7 +22,7 @@ Gesture callback can be used for continuous tracking of the touch pressure. It p
 At the beginning of the gesture, the pressure factor is 0.0. As the pressure increases, the pressure factor increases proportionally. The maximum pressure is 1.0.
 
 There's no implementation provided on Android and it simply renders children without any wrappers.
-Since this behaviour is only provided on some iOS devices, this gesture should not be used for defining any crucial behaviors. Use it only as an additional improvement and make all features to be accessed without this gesture as well.
+Since this behavior is only provided on some iOS devices, this gesture should not be used for defining any crucial behaviors. Use it only as an additional improvement and make all features accessible without this gesture as well.
 
 ## Reference
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/gesture-detector.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/gesture-detector.md
index a4184af36b..2d5e16d716 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/gesture-detector.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/gesture-detector.md
@@ -7,7 +7,7 @@ sidebar_position: 1
 
 import FunctionalComponents from './\_shared/gesture-detector-functional1.md';
 
-`GestureDetector` is the main component of the RNGH2. It is responsible for creating and updating native gesture handlers based on the config of provided gesture. The most significant difference between it and old gesture handlers is that the `GestureDetector` can recognize more than one gesture at the time thanks to gesture composition. Keep in mind that `GestureDetector` is not compatible with the [Animated API](https://reactnative.dev/docs/animated), nor with [Reanimated 1](https://docs.swmansion.com/react-native-reanimated/docs/1.x/).
+`GestureDetector` is the main component of the RNGH2. It is responsible for creating and updating native gesture handlers based on the config of the provided gesture. The most significant difference between it and old gesture handlers is that the `GestureDetector` can recognize more than one gesture at a time thanks to gesture composition. Keep in mind that `GestureDetector` is not compatible with the [Animated API](https://reactnative.dev/docs/animated), nor with [Reanimated 1](https://docs.swmansion.com/react-native-reanimated/docs/1.x/).
 
 ## Reference
 
@@ -33,7 +33,7 @@ function App() {
 A gesture object containing the configuration and callbacks. Can be any of the base gestures (`Tap`, `Pan`, `LongPress`, `Fling`, `Pinch`, `Rotation`, `ForceTouch`) or any [`ComposedGesture`](./composed-gestures.md) (`Race`, `Simultaneous`, `Exclusive`).
 
 :::info
-GestureDetector will decide whether to use Reanimated to process provided gestures based on callbacks they have. If any of the callbacks is a worklet, tools provided by the Reanimated will be utilized bringing ability to handle gestures synchronously.
+GestureDetector will decide whether to use Reanimated to process provided gestures based on callbacks they have. If any of the callbacks is a worklet, tools provided by Reanimated will be utilized, bringing the ability to handle gestures synchronously.
 
 Starting with Reanimated 2.3.0 Gesture Handler will provide a [StateManager](/docs/2.x/gestures/state-manager) in the [touch events](/docs/2.x/gestures/touch-events) that allows for managing the state of the gesture.
 :::
@@ -78,4 +78,4 @@ Specifies whether context menu should be enabled after clicking on underlying vi
   }
   ```
 
-  This example will throw an error, becuse we try to use the same instance of `Pan` in two different Gesture Detectors.
+  This example will throw an error, because we try to use the same instance of `Pan` in two different Gesture Detectors.
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/pan-gesture.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/pan-gesture.md
index 89241a91ad..e816b6e5f8 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/pan-gesture.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/pan-gesture.md
@@ -108,9 +108,9 @@ const styles = StyleSheet.create({
 
 ## Multi touch pan handling
 
-If your app relies on multi touch pan handling this section provides some information how the default behavior differs between the platform and how (if necessary) it can be unified.
+If your app relies on multi touch pan handling this section provides some information on how the default behavior differs between platforms and how (if necessary) it can be unified.
 
-The difference in multi touch pan handling lies in the way how translation properties during the event are being calculated.
+The difference in multi touch pan handling lies in the way translation properties during the event are being calculated.
 On iOS the default behavior when more than one finger is placed on the screen is to treat this situation as if only one pointer was placed in the center of mass (average position of all the pointers).
 This applies also to many platform native components that handle touch even if not primarily interested in multi touch interactions like for example UIScrollView component.
 
@@ -128,7 +128,7 @@ If you wish to track the "center of mass" virtual pointer and account for its ch
 
 ### `minDistance(value: number)`
 
-Minimum distance the finger (or multiple finger) need to travel before the gesture [activates](/docs/2.x/fundamentals/states-events#active). Expressed in points.
+Minimum distance the finger (or multiple fingers) need to travel before the gesture [activates](/docs/2.x/fundamentals/states-events#active). Expressed in points.
 
 ### `minPointers(value: number)`
 
@@ -144,26 +144,26 @@ Duration in milliseconds of the `LongPress` gesture before `Pan` is allowed to [
 
 ### `activeOffsetX(value: number | number[])`
 
-Range along X axis (in points) where fingers travels without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+Range along X axis (in points) where fingers travel without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
+If range is set as an array, the first value must be lower or equal to 0 and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `activeOffsetY(value: number | number[])`
 
-Range along Y axis (in points) where fingers travels without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+Range along Y axis (in points) where fingers travel without activation of gesture. Moving outside of this range implies activation of gesture. Range can be given as an array or a single number.
+If range is set as an array, the first value must be lower or equal to 0 and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `failOffsetY(value: number | number[])`
 
 When the finger moves outside this range (in points) along Y axis and gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+If range is set as an array, the first value must be lower or equal to 0 and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `failOffsetX(value: number | number[])`
 
 When the finger moves outside this range (in points) along X axis and gesture hasn't yet activated it will fail recognizing the gesture. Range can be given as an array or a single number.
-If range is set as an array, first value must be lower or equal to 0, a the second one higher or equal to 0.
+If range is set as an array, the first value must be lower or equal to 0 and the second one higher or equal to 0.
 If only one number `p` is given a range of `(-inf, p)` will be used if `p` is higher or equal to 0 and `(-p, inf)` otherwise.
 
 ### `averageTouches(value: boolean)` (Android only)
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/pinch-gesture.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/pinch-gesture.md
index 8953efb562..7917cdfff1 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/pinch-gesture.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/pinch-gesture.md
@@ -31,7 +31,7 @@ import BaseContinuousEventConfig from './\_shared/base-continuous-gesture-config
 import BaseEventCallbacks from './\_shared/base-gesture-callbacks.md';
 import BaseContinuousEventCallbacks from './\_shared/base-continuous-gesture-callbacks.md';
 
-A continuous gesture that recognizes pinch gesture. It allows for tracking the distance between two fingers and use that information to scale or zoom your content.
+A continuous gesture that recognizes a pinch gesture. It allows for tracking the distance between two fingers and using that information to scale or zoom your content.
 The gesture [activates](/docs/2.x/fundamentals/states-events#active) when fingers are placed on the screen and change their position.
 Gesture callback can be used for continuous tracking of the pinch gesture. It provides information about velocity, anchor (focal) point of gesture and scale.
 
@@ -117,14 +117,14 @@ The scale factor relative to the points of the two touches in screen coordinates
 
 ### `velocity`
 
-Velocity of the pan gesture the current moment. The value is expressed in scale factor per second.
+Velocity of the pinch gesture at the current moment. The value is expressed in scale factor per second.
 
 ### `focalX`
 
-Position expressed in points along X axis of center anchor point of gesture
+Position expressed in points along the X axis of the center anchor point of the gesture.
 
 ### `focalY`
 
-Position expressed in points along Y axis of center anchor point of gesture
+Position expressed in points along the Y axis of the center anchor point of the gesture.
 
 <BaseEventData />
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/state-manager.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/state-manager.md
index f4c39cdfdc..46ea8980fc 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/state-manager.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/state-manager.md
@@ -5,7 +5,7 @@ sidebar_label: Gesture state manager
 sidebar_position: 15
 ---
 
-`GestureStateManager` allows to manually control the state of the gestures. Please note that `react-native-reanimated` is required to use it, since it allows for synchronously executing methods in worklets.
+`GestureStateManager` allows you to manually control the state of the gestures. Please note that `react-native-reanimated` is required to use it, since it allows for synchronously executing methods in worklets.
 
 ## Methods
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/touch-events.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/touch-events.md
index c2244830ee..5daa8f2108 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/touch-events.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/gestures/touch-events.md
@@ -31,7 +31,7 @@ Don't rely on the order of items in the `touches` as it may change during the ge
 
 ### `id`
 
-A number representing id of the touch. It may be used to track the touch between events as the id will not change while it is being tracked.
+A number representing the id of the touch. It may be used to track the touch between events as the id will not change while it is being tracked.
 
 ### `x`
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/manual-gestures/index.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/manual-gestures/index.md
index 6d17988d18..f314d22685 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/manual-gestures/index.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/manual-gestures/index.md
@@ -28,12 +28,12 @@ RNGH2 finally brings one of the most requested features: manual gestures and tou
 </Step>
 
 <Step title="Step 3">
-    Now we have to make a component that will handle the gesture and draw all the pointer indicators. We will store data about pointers in an array of size 12 as that is the maximum number of touches that RNGH will track, and render them inside an Animated.View.
+    Now we have to make a component that will handle the gesture and draw all the pointer indicators. We will store data about pointers in an array of size 12, as that is the maximum number of touches that RNGH will track, and render them inside an Animated.View.
     <Step3 />
 </Step>
 
 <Step title="Step 4">
-    We have our components set up and we can finally get to making the gesture! We will start with onTouchesDown where we need to set position of the pointers and make them visible. We can get this information from the touches property of the event. In this case we will also check how many pointers are on the screen and activate the gesture if there are at least two.
+    We have our components set up and we can finally get to making the gesture! We will start with onTouchesDown where we need to set the position of the pointers and make them visible. We can get this information from the touches property of the event. In this case we will also check how many pointers are on the screen and activate the gesture if there are at least two.
     <Step4 />
 </Step>
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/quickstart/index.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/quickstart/index.md
index d602b1f5bc..542325c2cc 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/quickstart/index.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/quickstart/index.md
@@ -12,7 +12,7 @@ import Step3 from './\_steps/step3.md';
 import Step4 from './\_steps/step4.md';
 import Step5 from './\_steps/step5.md';
 
-RNGH2 provides much simpler way to add gestures to your app. All you need to do is wrap the view that you want your gesture to work on with [`GestureDetector`](/docs/2.x/gestures/gesture-detector), define the gesture and pass it to detector. That's all!
+RNGH2 provides a much simpler way to add gestures to your app. All you need to do is wrap the view that you want your gesture to work on with [`GestureDetector`](/docs/2.x/gestures/gesture-detector), define the gesture and pass it to detector. That's all!
 
 To demonstrate how you would use the new API, let's make a simple app where you can drag a ball around. You will need to add `react-native-gesture-handler` (for gestures) and `react-native-reanimated` (for animations) modules.
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/swipe-and-scroll.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/swipe-and-scroll.md
index b6d2f79bd7..c4916aa76b 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/swipe-and-scroll.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/swipe-and-scroll.md
@@ -4,7 +4,7 @@ title: Custom swipeable components inside ScrollView (web)
 sidebar_position: 5
 ---
 
-While we recommend using our own [`ReanimatedSwipeable`](../components/reanimated_swipeable.md) component, creating your own version of swipeable gives you more control over its behavior. Common issue here is that after creating your own swipeable component, scroll does not work. In that case, try adding [`touchAction`](../gestures/gesture-detector.md#touchaction-web-only) set to `"pan-y"`, like this:
+While we recommend using our own [`ReanimatedSwipeable`](../components/reanimated_swipeable.md) component, creating your own version of swipeable gives you more control over its behavior. A common issue here is that after creating your own swipeable component, scroll does not work. In that case, try adding [`touchAction`](../gestures/gesture-detector.md#touchaction-web-only) set to `"pan-y"`, like this:
 
 ```jsx
 <GestureDetector gesture={...} ... touchAction="pan-y">
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/testing.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/testing.md
index 71b4a43070..f6dd37dd7e 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/testing.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/testing.md
@@ -6,7 +6,7 @@ sidebar_position: 4
 
 ## Mocking native modules
 
-In order to load mocks provided by RNGH add following to your jest config in `package.json`:
+In order to load mocks provided by RNGH add the following to your jest config in `package.json`:
 
 ```json
 "setupFiles": ["./node_modules/react-native-gesture-handler/jestSetup.js"]
@@ -54,7 +54,7 @@ data is missing using these rules:
    defaults.
 4. Missing `BEGIN` and `END` events are added with data copied from first and last
    passed event, respectively.
-5. If first event don't have `state` field, the `ACTIVE` state is assumed.
+5. If the first event doesn't have a `state` field, the `ACTIVE` state is assumed.
 
 Some examples:
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/troubleshooting.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/troubleshooting.md
index 6bc41d1f0e..96e8a6d7aa 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/troubleshooting.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/troubleshooting.md
@@ -17,8 +17,8 @@ Thanks for giving this library a try! We are sorry that you might have encounter
 ## Reporting issues
 
 This library is maintained by a very small team.
-Please be mindful of that when reporting issue and when it happens that we can't get back to you as soon as you might expect.
-We would love to fix all the problems as soon as possible, but often our time is constraint with other issues/features or projects.
+Please be mindful of that when reporting an issue and when it happens that we can't get back to you as soon as you might expect.
+We would love to fix all the problems as soon as possible, but often our time is constrained by other issues/features or projects.
 To make it easier for us to understand your issue and to be able to approach it sooner you can help by:
 
 - Making sure the issue description is complete. Please include all the details about your environment (library version, RN version, device OS etc).
@@ -62,7 +62,7 @@ If you use `npm` you should add [`overrides` property](https://docs.npmjs.com/cl
 }
 ```
 
-After that you need to run your package manager again
+After that you need to run your package manager again.
 
 ```bash
 yarn
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/upgrading-to-2.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/upgrading-to-2.md
index 8bc4f1916c..ccec7070df 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/upgrading-to-2.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/guides/upgrading-to-2.md
@@ -5,11 +5,11 @@ title: Upgrading to the new API introduced in Gesture Handler 2
 
 ## Make sure to migrate off the `RNGestureHandlerEnabledRootView` (Android only)
 
-Gesture Handler 1 required you to override `createRootView` to return an instance of `RNGestureHandlerEnabledRootView`. This class has been the cause of many hard to debug and fix crashed and was deprecated in version 2.0, and subsequently removed in version 2.4. If you are still using it, check out [migrating off RNGHEnabledRootView guide](/docs/2.x/guides/migrating-off-rnghenabledroot).
+Gesture Handler 1 required you to override `createRootView` to return an instance of `RNGestureHandlerEnabledRootView`. This class has been the cause of many hard-to-debug and hard-to-fix crashes and was deprecated in version 2.0, and subsequently removed in version 2.4. If you are still using it, check out [migrating off RNGHEnabledRootView guide](/docs/2.x/guides/migrating-off-rnghenabledroot).
 
 ## Upgrading to the new API
 
-The most important change brought by the Gesture Handler 2 is the new Gesture API, along with the `GestureDetector` component. It makes declaring gesture easier, as it handles much of the work under the hood and reduces the amount of necessary boilerplate code. Instead of a separate component for every type of gesture, the `GestureDetector` component is used to attach gestures to the underlying view based on the configuration object passed to it. The configuration objects are created using the `Gesture` object, here is a simple example:
+The most important change brought by the Gesture Handler 2 is the new Gesture API, along with the `GestureDetector` component. It makes declaring gestures easier, as it handles much of the work under the hood and reduces the amount of necessary boilerplate code. Instead of a separate component for every type of gesture, the `GestureDetector` component is used to attach gestures to the underlying view based on the configuration object passed to it. The configuration objects are created using the `Gesture` object, here is a simple example:
 
 ```jsx
 const tapGesture = Gesture.Tap().onStart(() => {
@@ -30,7 +30,7 @@ As you can see, there are no `onGestureEvent` and `onHandlerStateChange` callbac
 - `onUpdate` - replaces `onGestureEvent`, called every time the gesture sends a new event while it's in the `ACTIVE` state
 - `onChange` - if defined, called just after `onUpdate`, the events passed to it are the same as the ones passed to `onUpdate` but they also contain `change` values which hold the change in value they represent since the last event (i.e. in case of the `Pan` gesture, the event will also contain `changeX` and `changeY` properties)
 - `onEnd` - called when the gesture transitions from the `ACTIVE` state to either of `END`, `FAILED` or `CANCELLED` - you can tell whether the gesture finished due to user interaction or because of other reason (like getting cancelled by the system, or failure criteria) using the second value passed to the `onEnd` callback alongside the event
-- `onFinalize` called when the gesture transitions into either of `END`, `FAILED` or `CANCELLED` state, if the gesture was `ACTIVE`, `onEnd` will be called first (similarly to `onEnd` you can determine the reason for finishing using the second argument)
+- `onFinalize` - called when the gesture transitions into either of `END`, `FAILED` or `CANCELLED` state, if the gesture was `ACTIVE`, `onEnd` will be called first (similarly to `onEnd` you can determine the reason for finishing using the second argument)
 
 The difference between `onEnd` and `onFinalize` is that the `onEnd` will be called only if the gesture was `ACTIVE`, while `onFinalize` will be called if the gesture has `BEGAN`. This means that you can use `onEnd` to clean up after `onStart`, and `onFinalize` to clean up after `onBegin` (or both `onBegin` and `onStart`).
 
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/under-the-hood/how-does-it-work.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/under-the-hood/how-does-it-work.md
index 4d613d4879..e58f1d69ac 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/under-the-hood/how-does-it-work.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/under-the-hood/how-does-it-work.md
@@ -19,4 +19,4 @@ All gestures are implemented using [UIGestureRecognizers](https://developer.appl
 Unfortunately, Android doesn't provide an easy way of handling gestures hence most of them were implemented from scratch, including a system for managing how the gestures should interact with each other. Here's a quick overview of how it works:
 When you wrap a component with `GestureHandlerRootView` it allows for the RNGH to intercept all touch events on that component and process them, deciding whether they should be handled by one of the gesture handlers or passed to the underlying view. Gesture handlers are created when you assign a gesture configuration to the `GestureDetector`, it initializes all of the necessary handlers natively. Every `GestureHandlerRootView` also has a specific handler to decide whether to pass the touch events or to consume them. It can never activate, only begin, end or be cancelled. When this handler is in the `UNDETERMINED` state it means that there is no touch in progress, however when the touch starts it transitions to the `BEGAN` state. As long as it stays in that state, no touch event is consumed, but as soon as it gets cancelled (meaning that some handler has activated) all incoming touch events get consumed, preventing underlying view from receiving them.
 
-When a pointer touches the screen the view tree is traversed in order to extract all handlers attached to the views below the finger (including the one attached to the `GestureHandlerRootView`) and all extracted handlers transition to the `BEGAN` state, signalling that the gesture may have began. The touch events continue to be delivered to all extracted handlers until one of them recognizes the gesture and tries to activate. At this point the orchestrator checks whether this gesture should wait for any other of the extracted gestures to fail. If it does, it's put to the waiting list, if it doesn't, it gets activated and all other gestures (that are not simultaneous with it) get cancelled. When a gesture handlers transitions to a finished state (the gesture recognized by it stops, it fails or gets cancelled) the orchestrator check the waiting handlers. Every one of them that waited for the gesture that just failed tries to activate again (and again the orchestrator checks if it should wait for any of the extracted gestures...).
+When a pointer touches the screen the view tree is traversed in order to extract all handlers attached to the views below the finger (including the one attached to the `GestureHandlerRootView`) and all extracted handlers transition to the `BEGAN` state, signalling that the gesture may have begun. The touch events continue to be delivered to all extracted handlers until one of them recognizes the gesture and tries to activate. At this point the orchestrator checks whether this gesture should wait for any other of the extracted gestures to fail. If it does, it's put to the waiting list, if it doesn't, it gets activated and all other gestures (that are not simultaneous with it) get cancelled. When a gesture handler transitions to a finished state (the gesture recognized by it stops, it fails or gets cancelled) the orchestrator checks the waiting handlers. Every one of them that waited for the gesture that just failed tries to activate again (and again the orchestrator checks if it should wait for any of the extracted gestures...).
diff --git a/packages/docs-gesture-handler/versioned_docs/version-2.x/under-the-hood/state.md b/packages/docs-gesture-handler/versioned_docs/version-2.x/under-the-hood/state.md
index 1a267ac59d..1e37fb0b53 100644
--- a/packages/docs-gesture-handler/versioned_docs/version-2.x/under-the-hood/state.md
+++ b/packages/docs-gesture-handler/versioned_docs/version-2.x/under-the-hood/state.md
@@ -71,7 +71,7 @@ This is the initial state of each handler and it goes into this state after it's
 
 ### FAILED
 
-A handler received some touches but for some reason didn't recognize them. For example, if a finger travels more distance than a defined `maxDist` property allows, then the handler won't become active but will fail instead. Afterwards, it's state will be reset to `UNDETERMINED`.
+A handler received some touches but for some reason didn't recognize them. For example, if a finger travels more distance than a defined `maxDist` property allows, then the handler won't become active but will fail instead. Afterwards, its state will be reset to `UNDETERMINED`.
 
 ### BEGAN