[docs] Update docs

packages/docs-gesture-handler/docs/fundamentals/callbacks-events.mdx

@@ -8,9 +8,9 @@ sidebar_position: 7
 import { GestureEventFlowChart, TouchEventFlowChart } from '@site/src/examples/CallbacksFlowCharts'
 import CollapsibleCode from '@site/src/components/CollapsibleCode';
 
-At any given time, each handler instance has an assigned [state](/docs/under-the-hood/state) that can change when new touch events occur or can be forced to change by the touch system in certain circumstances. You can hook into state transitions using specific [gesture callbacks](#callbacks).
+At any given time, each handler instance has an assigned [state](/docs/under-the-hood/state) that can change when new touch events occur or can be forced to change by the touch system under certain circumstances. You can hook into state transitions using specific [gesture callbacks](#callbacks).
 
-When `Reanimated` is installed, all callbacks are automatically workletized. For more details, refer to the [Integration with Reanimated](/docs/fundamentals/reanimated-interactions#automatic-workletization-of-gesture-callbacks) section.
+When Reanimated is installed, all callbacks are automatically workletized. For more details, refer to the [Integration with Reanimated](/docs/fundamentals/reanimated-interactions#automatic-workletization-of-gesture-callbacks) section.
 
 ## Callbacks flow
 

packages/docs-gesture-handler/docs/fundamentals/state-manager.mdx

@@ -7,7 +7,7 @@ sidebar_position: 6
 
 import CollapsibleCode from '@site/src/components/CollapsibleCode';
 
-RNGH3 allows to manually control gestures lifecycle by using `GestureStateManager`.
+RNGH3 allows to manually control [gestures lifecycle](/docs/under-the-hood/state) by using `GestureStateManager`.
 
 ## State management
 

packages/docs-gesture-handler/docs/guides/quickstart/index.md

@@ -23,7 +23,7 @@ To see the new API in action, let's build a simple app where you can drag a ball
 
 <Step title="Step 2">
   <div>
-    Next, define the <a href="https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/glossary#shared-value">`SharedValues`</a> to track the ball's position and create the animated styles required to position the ball on the screen:
+    Next, define the <a href="https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/glossary#shared-value" target="_blank">`SharedValues`</a> to track the ball's position and create the animated styles required to position the ball on the screen:
   </div>
   <Step2 />
 </Step>

packages/docs-gesture-handler/docs/guides/testing.md

@@ -23,40 +23,31 @@ Example:
 
 ## Testing Gestures' and Gesture handlers' callbacks
 
-RNGH provides an API for triggering selected handlers:
+RNGH provides APIs, specifically [`fireGestureHandler`](#firegesturehandler) and [`getByGestureTestId`](#getbygesturetestid), to trigger selected handlers.
 
-- [`fireGestureHandler(gestureOrHandler, eventList)`](/docs/guides/testing#firegesturehandlergestureorhandler-eventlist)
-- [`getByGestureTestId(testID)`](/docs/guides/testing#getbygesturetestidtestid)
+### fireGestureHandler
 
-## fireGestureHandler(gestureOrHandler, eventList)
+```ts
+fireGestureHandler: (componentOrGesture, eventList) => void;
+```
 
 Simulates one event stream (i.e. event sequence starting with `BEGIN` state and ending
 with one of `END`/`FAIL`/`CANCEL` states), calling appropriate callbacks associated with given gesture handler.
 
-### Arguments
-
-#### `gestureOrHandler`
-
-Represents either:
-
-1. Gesture handler component found by Jest queries (e.g. `getByTestId`)
-2. Gesture found by [`getByGestureTestId()`](/docs/guides/testing#getbygesturetestidtestid)
-
-#### `eventList`
+- `componentOrGesture` - Either Gesture Handler component found by `Jest` queries (e.g. `getByTestId`) or Gesture found by [`getByGestureTestId()`](#getbygesturetestidtestid)
 
-Event data passed to appropriate callback. RNGH fills event list if required
-data is missing using these rules:
+- `eventList` - Event data passed to appropriate callback. RNGH fills event list if required
+  data is missing using these rules:
+  - `oldState` is filled using state of the previous event. `BEGIN` events use
+    `UNDETERMINED` value as previous event.
+  - Events after first `ACTIVE` state can omit `state` field.
+  - Handler specific data is filled (e.g. `numberOfTouches`, `x` fields) with
+    defaults.
+  - Missing `BEGIN` and `END` events are added with data copied from first and last
+    passed event, respectively.
+  - If first event don't have `state` field, the `ACTIVE` state is assumed.
 
-1. `oldState` is filled using state of the previous event. `BEGIN` events use
-   `UNDETERMINED` value as previous event.
-2. Events after first `ACTIVE` state can omit `state` field.
-3. Handler specific data is filled (e.g. `numberOfTouches`, `x` fields) with
-   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.
-
-Some examples:
+Some `eventList` examples:
 
 ```jsx
 const oldStateFilled = [
@@ -86,44 +77,46 @@ const implicitBeginAndEnd = [
 const allImplicits = []; // 3 events, one BEGIN, one ACTIVE, one END with defaults.
 ```
 
-### Example
-
-Extracted from RNGH tests, check `Events.test.tsx` for full implementation.
+### getByGestureTestId
 
 ```tsx
-it('sends events with additional data to handlers', () => {
-  const panHandlers = mockedEventHandlers();
-  render(<SingleHandler handlers={panHandlers} treatStartAsUpdate />);
-  fireGestureHandler<PanGesture>(getByGestureTestId('pan'), [
-    { state: State.BEGAN, translationX: 0 },
-    { state: State.ACTIVE, translationX: 10 },
-    { translationX: 20 },
-    { translationX: 20 },
-    { state: State.END, translationX: 30 },
-  ]);
-
-  expect(panHandlers.active).toHaveBeenCalledTimes(3);
-  expect(panHandlers.active).toHaveBeenLastCalledWith(
-    expect.objectContaining({ translationX: 20 })
-  );
-});
+getByGestureTestId: (testID: string) => Gesture;
 ```
 
-## getByGestureTestId(testID)
-
-Returns opaque data type associated with gesture. Gesture is found via `testID` attribute in rendered
-components (see [`testID`](/docs/gestures/use-pan-gesture#testid)).
-
-### Arguments
+Returns opaque data type associated with gesture. Gesture is found via [`testID`](/docs/gestures/use-pan-gesture#testid) attribute in rendered
+components.
 
-#### `testID`
+- `testID` - String identifying gesture.
 
-String identifying gesture.
+:::warning
+`testID` must be unique among components rendered in test.
+:::
 
-### Notes
+## Example
 
-`testID` must be unique among components rendered in test.
+Extracted from RNGH tests, check [`api_v3.test.tsx`](https://github.com/software-mansion/react-native-gesture-handler/blob/main/packages/react-native-gesture-handler/src/__tests__/api_v3.test.tsx) for full implementation.
 
-### Example
+```tsx
+test('Pan gesture', () => {
+  const onBegin = jest.fn();
+  const onStart = jest.fn();
+
+  const panGesture = renderHook(() =>
+    usePanGesture({
+      disableReanimated: true,
+      onBegin: (e) => onBegin(e),
+      onActivate: (e) => onStart(e),
+    })
+  ).result.current;
+
+  fireGestureHandler(panGesture, [
+    { oldState: State.UNDETERMINED, state: State.BEGAN },
+    { oldState: State.BEGAN, state: State.ACTIVE },
+    { oldState: State.ACTIVE, state: State.ACTIVE },
+    { oldState: State.ACTIVE, state: State.END },
+  ]);
 
-See above example for `fireGestureHandler`.
+  expect(onBegin).toHaveBeenCalledTimes(1);
+  expect(onStart).toHaveBeenCalledTimes(1);
+});
+```

packages/docs-gesture-handler/docs/guides/troubleshooting.md → packages/docs-gesture-handler/docs/guides/troubleshooting.mdx

@@ -4,22 +4,22 @@ title: Troubleshooting
 sidebar_position: 3
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 ## Troubleshooting
 
 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).
 3. You can try seeking help on [Software Mansion Discord](https://discord.com/invite/VemJ4df8Yr).
-4. If you feel like reading the source code I 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.
+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.
 
 ## 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.
-To make it easier for us to understand your issue and to be able to approach it sooner you can help by:
+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.
@@ -32,44 +32,57 @@ To make it easier for us to understand your issue and to be able to approach it
 
 - 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` 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 to work, all composed gestures must be attached to the same `GestureHandlerRootView`.
+- 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`.
+
+## 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.
 
-### Multiple instances of Gesture Handler were detected
+You can resolve this problem manually by modifying your `package.json` file. This will depend on the package manager you are using.
 
-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. You can resolve this problem manually by modifying your `package.json` file.
 
-You can check which libraries are using Gesture Handler, for example, with the command:
+<Tabs groupId="package-managers">
+  <TabItem value="npm" label="NPM">
+    You can check which libraries are using Gesture Handler with the command:
+
+    ```bash
+    npm ls react-native-gesture-handler
+    ```
 
-```bash
-npm ls react-native-gesture-handler
-yarn why react-native-gesture-handler
-```
+    Add [`overrides`](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides) property.
 
-If you use `yarn` you should add [`resolution` property](https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/).
+    ```json
+    "overrides": {
+      "react-native-gesture-handler": <Gesture Handler version>
+    }
+    ```
 
-```json
-"resolutions": {
-  "react-native-gesture-handler": <Gesture Handler version>
-}
-```
+    After that you need to run your package manager again:
 
-If you use `npm` you should add [`overrides` property](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides).
+      ```bash
+    npm install
+    ```
+  </TabItem>
+  <TabItem value="yarn" label="YARN">
+    You can check which libraries are using Gesture Handler with the command:
 
-```json
-"overrides": {
-  "react-native-gesture-handler": <Gesture Handler version>
-}
-```
+    ```bash
+    yarn why react-native-gesture-handler
+    ```
 
-After that you need to run your package manager again
+    Add [`resolutions`](https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/) property.
 
-```bash
-yarn
-```
+    ```json
+    "resolutions": {
+      "react-native-gesture-handler": <Gesture Handler version>
+    }
+    ```
 
-or
+    After that you need to run your package manager again:
 
-```bash
-npm install
-```
+    ```bash
+    yarn
+    ```
+  </TabItem>
+</Tabs>