Other renames

Author: m-bert

packages/docs-gesture-handler/docs/components/buttons.mdx

@@ -10,7 +10,7 @@ import GifGallery from '@site/components/GifGallery';
 import HeaderWithBadges from '@site/src/components/HeaderWithBadges';
 
 :::danger
-Button components described in this section are deprecated and will be removed in the future. Please use [`Clickable`](/docs/components/clickable) instead.
+Button components described in this section are deprecated and will be removed in the future. Please use [`Touchable`](/docs/components/touchable) instead.
 :::
 
 <GifGallery>
@@ -198,7 +198,7 @@ If you wish to get specific information about platforms design patterns, visit [
 
 This library allows the use of native components with native feedback in adequate situations.
 
-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.
+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 React Native `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.
 

packages/docs-gesture-handler/docs/components/touchable.mdx

@@ -42,7 +42,7 @@ Replacing `BorderlessButton` with `Touchable` is as easy as replacing `RectButto
 
 ## Replacing deprecated Touchables
 
-If you were using the deprecated [`Touchables`](/docs/components/touchables), you can replace them with new `Touchable` as well.
+If you were using the deprecated [`Touchables`](/docs/components/legacy-touchables), you can replace them with new `Touchable` as well.
 
 ### TouchableOpacity
 

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

@@ -32,7 +32,7 @@ This library is maintained by a very small team. Please keep this in mind when r
 
 - 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).
+- Keep in mind that [Legacy `Touchables`](/docs/components/legacy-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

packages/docs-gesture-handler/docs/guides/upgrading-to-3.mdx

@@ -246,14 +246,13 @@ code2={
 
 ### Buttons
 
-RNGH3 introduces the [`Clickable`](/docs/components/clickable) component — a flexible, unified replacement for all previous button types. While `Clickable` shares the same logic as our standard buttons, it offers a more customizable API.
+RNGH3 introduces the [`Touchable`](/docs/components/touchable) component — a flexible, unified replacement for all previous button types. While `Touchable` shares the same logic as our standard buttons, it offers a more customizable API.
 
 To help you migrate, here is the current state of our button components:
 
-- [`Clickable`](/docs/components/clickable) - The recommended component. Can be used to replicate both `RectButton` and `BorderlessButton` effects by adjusting the `activeOpacity` and `activeUnderlayOpacity` props.
+- [`Touchable`](/docs/components/touchable) - The recommended component. Can be used to replicate both `RectButton` and `BorderlessButton` effects by adjusting the `activeOpacity` and `activeUnderlayOpacity` props.
   - To replace `RectButton`, add `activeUnderlayOpacity={0.105}`.
   - To replace `BorderlessButton`, add `activeOpacity={0.3}`.
-  
 
 - Standard Buttons (Deprecated) - `BaseButton`, `RectButton` and `BorderlessButton` are still available but are now deprecated. They have been internally rewritten using the new Hooks API to resolve long-standing issues.