Apply suggestion from @graingert

Author: graingert

Misc/NEWS.d/next/Library/2026-09-01-00-00-00.gh-issue-156784.8gvtt4.rst

@@ -4,7 +4,7 @@ same socket was previously used to send to an address that isn't
 listening) is surfaced as a :exc:`ConnectionResetError` instead of
 being silently swallowed. Datagram transports now deliver it to the
 protocol via :meth:`~asyncio.DatagramProtocol.error_received` and
-re-arm the read loop, and :meth:`~asyncio.loop.sock_recvfrom` /
+re-schedule the read loop, and :meth:`~asyncio.loop.sock_recvfrom` /
 :meth:`~asyncio.loop.sock_recvfrom_into` now raise it, matching the
 behaviour :class:`asyncio.SelectorEventLoop` already had. This
 corrects the fix applied in gh-91227, which papered over the issue by