Update changelog to match new connected and reconnected terms

Author: n-lark

src/changelog/2026/09/client-presence-events.md

@@ -16,14 +16,14 @@ Every client now carries a stable `clientId` on `msg._client`. The old `socketId
 
 The `ui-control` node can now emit presence events keyed on that id. Set its **Output** to **Client Presence Events Only** and it sends:
 
-- `client-connect` when a new client first connects
-- `client-reconnect` when a client returns after a brief drop
+- `client-connected` when a new client first connects
+- `client-reconnected` when a client returns after a brief drop
 - `client-gone` when a client leaves and does not come back
 
-A grace window means a quick refresh or network blip does not fire `client-gone`. A client that returns within 20 seconds is reported as `client-reconnect` instead, so you only hear about genuine departures. Use these to keep an accurate map of who is currently viewing your dashboard: add on connect, keep on reconnect, remove on gone.
+A grace window means a quick refresh or network blip does not fire `client-gone`. A client that returns within 20 seconds is reported as `client-reconnected` instead, so you only hear about genuine departures. Use these to keep an accurate map of who is currently viewing your dashboard: add on connect, keep on reconnect, remove on gone.
 
-![A ui-control node set to Client Presence Events Only, with a debug node showing a client-connect message](./images/client-presence-events.gif)
-*Reopening the same browser produces `client-reconnect` rather than a second `client-connect`, so the client keeps its place in your map. The recording uses a shortened grace window so the events fit on screen; the real window is 20 seconds.*
+![A ui-control node set to Client Presence Events Only, with a debug node showing a client-connected message](./images/client-presence-events.gif)
+*Reopening the same browser produces `client-reconnected` rather than a second `client-connected`, so the client keeps its place in your map. The recording uses a shortened grace window so the events fit on screen; the real window is 20 seconds.*
 
 **Note:** if you have `ui-control` nodes set to **All Events**, they will now also emit the `client-*` presence messages. The `client-` prefix keeps them distinct from the existing `connect` / `lost` events, so flows that switch on `msg.payload` are unaffected, but a flow that reacts to *every* message from that node will see the new ones.