While reading the docs I hit three example snippets that don't match the actual API. Each fix below is checked against the source of truth in the repo.

1. startRecording example is a SyntaxError (docs/content/docs/recorder.mdx)

The "Starting a Recording" snippet passes the callbacks inside an object literal:

await recorder.startRecording({
  (path, reason) => ...,
  (error) => ...,
})

Bare arrow functions as object members aren't valid JS, so this throws SyntaxError: Unexpected token '('. startRecording actually takes positional arguments: startRecording(onRecordingFinished, onRecordingError, onRecordingPaused?, onRecordingResumed?) (see Recorder.nitro.ts). The positional form is already used correctly in video-output.mdx, so this just makes recorder.mdx consistent with it.

2. Wrong default JPEG quality (docs/content/docs/photo-quality.mdx)

The page says the default compression is 0.95 (95% quality). The real default is 0.9: usePhotoOutput destructures quality = 0.9 (src/hooks/usePhotoOutput.ts), and the Nitro spec documents @default 0.9 (CameraPhotoOutput.nitro.ts). Updated 0.95 to 0.9 and 95% to 90%.

3. getCameraDevice @example uses the wrong call shape (src/devices/getCameraDevice.ts)

The DeviceFilter.physicalDevices JSDoc @example calls getCameraDevice({ physicalDevices: [...] }) (a single object), but the function signature is getCameraDevice(devices, position, filter). The function-level @example in the same file already shows the correct 3-argument form, so I updated the two physicalDevices example lines to match: getCameraDevice(devices, 'back', { physicalDevices: [...] }).

Docs-only change, no runtime code touched.