gh-127859: Fixed documentation for call_later and call_at regarding early wakeup.

Doc/library/asyncio-eventloop.rst

@@ -304,6 +304,12 @@ clocks to track time.
    custom :class:`contextvars.Context` for the *callback* to run in.
    The current context is used when no *context* is provided.
 
+   .. note::
+
+      For performance, callbacks scheduled with :meth:`loop.call_later`
+      may run up to one clock-resolution early (see
+      ``time.get_clock_info('monotonic').resolution``).
+
    .. versionchanged:: 3.7
       The *context* keyword-only parameter was added. See :pep:`567`
       for more details.
@@ -324,6 +330,12 @@ clocks to track time.
    An instance of :class:`asyncio.TimerHandle` is returned which can
    be used to cancel the callback.
 
+   .. note::
+
+      For performance, callbacks scheduled with :meth:`loop.call_at`
+      may run up to one clock-resolution early (see
+      ``time.get_clock_info('monotonic').resolution``).
+
    .. versionchanged:: 3.7
       The *context* keyword-only parameter was added. See :pep:`567`
       for more details.

Misc/NEWS.d/next/Documentation/2025-08-16-15-36-30.gh-issue-127859.CdXB5S.rst

@@ -0,0 +1,2 @@
+:meth:`asyncio.loop.call_at` and :meth:`asyncio.loop.call_later` now
+correctly state that they may wake up early. Patch by Bar Harel.