fix: [docs] scope the change callback notes to the changed callbacks

Author: rohanchkrabrty

.agents/skills/apsara/references/composition.md

@@ -65,7 +65,7 @@ const [open, setOpen] = useState(false);
 </Dialog>
 ```
 
-Change callbacks (`onValueChange`, `onOpenChange`, `onInputValueChange`, and the like) take the new value first and a details object second: Base UI's `eventDetails` on components that wrap Base UI, or `details` with the same `reason` and `event` on components that own their state. Component data is a field of that object, for example `details.mode` on `ColorPicker` and `details.operation` on `FilterChip`.
+Most change callbacks (`onValueChange`, `onOpenChange`, `onInputValueChange`, and the like) take the new value first and a details object second. Components that wrap Base UI pass Base UI's `eventDetails`. Other components pass their own `details`, for example `details.mode` on `ColorPicker` and `details.operation` on `FilterChip`. A few callbacks take only the value, for example CodeBlock `onValueChange` and ColorPicker `onModeChange`. Check the props table for the exact signature.
 
 Several overlay roots (`Dialog`, `Menu`, `Popover`, `Tooltip`) also expose `createHandle` for advanced imperative open/close from outside the subtree — use only when a trigger can't live in the same tree.
 

apps/www/src/content/docs/(overview)/upgrading.mdx

@@ -9,7 +9,7 @@ on [GitHub releases](https://github.com/raystack/apsara/releases).
 
 ## Unreleased: change callbacks get a details object
 
-Every change callback now passes a second argument after the value. A
+The change callbacks below pass a second argument after the value. A
 component that wraps Base UI passes Base UI's `eventDetails`. A component that
 keeps its own state passes a `details` object with the same `reason` and
 `event` fields, plus any field of its own.