docs: credit eaburns's devdraw/acme as the source of the Wayland warp technique

Reword from 'following'/'taken from' to 'sourced from' — the pointer-constraints
warp technique was drawn from eaburns's Wayland devdraw/acme, not tracked or
lifted wholesale.

README.md

@@ -216,7 +216,7 @@ through a list.
   or focus-move), the pointer is warped to the centre of the new pane so the
   mouse stays where your attention is — the same cursor-follows-focus feel as
   acme. On X11 this is a direct `QCursor::setPos`; on Wayland (which forbids
-  that) it uses the pointer-constraints protocol, following
+  that) it uses the pointer-constraints protocol, a technique sourced from
   [eaburns's Wayland devdraw/acme](https://github.com/eaburns/plan9port/tree/wayland).
 - **Configure:** drop a `radials.json` at `~/.config/deft/radials.json` to
   replace the built-in tree; when it is absent, empty, or invalid, the built-in

src/radial/waylandcursorwarp.h

@@ -9,8 +9,8 @@
  * sanctioned way to reposition the cursor is zwp_pointer_constraints_v1: lock
  * the pointer to the surface it is already over, set a surface-local position
  * hint, then release the lock — the compositor warps the pointer to the hint on
- * unlock (this is how eaburns's Wayland implementation of devdraw/acme moves
- * the cursor: https://github.com/eaburns/plan9port/tree/wayland).
+ * unlock (technique sourced from eaburns's Wayland implementation of
+ * devdraw/acme: https://github.com/eaburns/plan9port/tree/wayland).
  *
  * Kate's split panes are child widgets of a single top-level window, i.e. one
  * wl_surface, so moving the pointer between panes is a warp *within* that