Merge pull request #417 from itsdouges/main

Fix handle package being named handles

Author: bbohlender

docs/getting-started/faq.md

@@ -23,7 +23,7 @@ In contrast to non-immersive 3D applications, the camera transformation in MR/VR
 Check if you have OrbitControls, CameraControls from `@react-three/drei`, or other controls in your scene and make sure to place an `<IfInSessionMode deny={['immersive-ar', 'immersive-vr']}>` guard around them when in XR or replace them with `OrbitHandles` or `MapHandles` from `@react-three/handle`. This prevents overwriting the camera transformation which is controlled through WebXR when inside an immersive session and allows to access the correct transformation.
 
 ```tsx
-import { OrbitHandles } from '@react-three/handles'
+import { OrbitHandles } from '@react-three/handle'
 import { noEvents, PointerEvents } from '@react-three/xr'
 
 <Canvas events={noEvents}>

docs/handles/prebuild-handles.md

@@ -9,7 +9,7 @@ The `Handle` component allows for the orchestration of multiple handles together
 Using the `TransformHandles` and `PivotHandles` in React Three Fiber requires disabling the built-in event system and adding the event system of `@react-three/xr`.
 
 ```tsx
-import { TransformHandles } from '@react-three/handles'
+import { TransformHandles } from '@react-three/handle'
 import { noEvents, PointerEvents } from '@react-three/xr'
 
 <Canvas events={noEvents}>

docs/handles/screen-handle-components.md

@@ -9,7 +9,7 @@ Screen handles are available for screen-based devices like smartphones and PCs a
 Using the `OrbitHandles` and `MapHandles` in React Three Fiber requires disabling the built-in event system and adding the event system of `@react-three/xr`.
 
 ```tsx
-import { OrbitHandles } from '@react-three/handles'
+import { OrbitHandles } from '@react-three/handle'
 import { noEvents, PointerEvents } from '@react-three/xr'
 
 <Canvas events={noEvents}>