@@ -25,17 +25,15 @@ are available, however.
 
 .. c:var:: PyObject* Py_False
 
-   The Python ``False`` object.  This object has no methods and is
-   :term:`immortal`.
+   The Python ``False`` object.  This object is :term:`immortal`.
 
    .. versionchanged:: 3.12
       :c:data:`Py_False` is :term:`immortal`.
 
 
 .. c:var:: PyObject* Py_True
 
-   The Python ``True`` object.  This object has no methods and is
-   :term:`immortal`.
+   The Python ``True`` object.  This object is :term:`immortal`.
 
    .. versionchanged:: 3.12
       :c:data:`Py_True` is :term:`immortal`.
 
@@ -22,7 +22,7 @@ to simplify async code usage for common wide-spread scenarios.
 Running an asyncio Program
 ==========================
 
-.. function:: run(coro, *, debug=None, loop_factory=None)
+.. function:: run(coro, *, debug=None, loop_factory=None, eager_tasks=False)
 
    Execute *coro* in an asyncio event loop and return the result.
 
@@ -45,10 +45,18 @@ Running an asyncio Program
    and should ideally only be called once. It is recommended to use
    *loop_factory* to configure the event loop.
 
+   If *eager_tasks* is ``True``, the created loop is configured to use
+   :ref:`eager-task-factory` by default.
+
    The executor is given a timeout duration of 5 minutes to shutdown.
    If the executor hasn't finished within that duration, a warning is
    emitted and the executor is closed.
 
+   .. note::
+
+      Users concerned about performance are encouraged to experiment with
+      ``eager_tasks=True`` in their code.
+
    Example::
 
        async def main():
@@ -74,11 +82,15 @@ Running an asyncio Program
 
       *coro* can be any awaitable object.
 
+   .. versionchanged:: 3.16
+
+      Added *eager_tasks* parameter.
+
 
 Runner context manager
 ======================
 
-.. class:: Runner(*, debug=None, loop_factory=None)
+.. class:: Runner(*, debug=None, loop_factory=None, eager_tasks=False)
 
    A context manager that simplifies *multiple* async function calls in the same
    context.
@@ -95,6 +107,9 @@ Runner context manager
    current one. By default :func:`asyncio.new_event_loop` is used and set as
    current event loop with :func:`asyncio.set_event_loop` if *loop_factory* is ``None``.
 
+   If *eager_tasks* is ``True``, the created loop is configured to use
+   :ref:`eager-task-factory` by default.
+
    Basically, :func:`asyncio.run` example can be rewritten with the runner usage::
 
         async def main():
@@ -104,8 +119,17 @@ Runner context manager
         with asyncio.Runner() as runner:
             runner.run(main())
 
+   .. note::
+
+      Users concerned about performance are encouraged to experiment with
+      ``eager_tasks=True`` in their code.
+
    .. versionadded:: 3.11
 
+   .. versionchanged:: 3.16
+
+      Added *eager_tasks* parameter.
+
    .. method:: run(coro, *, context=None)
 
       Execute *coro* in the embedded event loop.
 
@@ -432,7 +432,8 @@ For simple text calendars this module provides the following functions.
 
 .. function:: prcal(theyear, w=0, l=0, c=6, m=3)
 
-   Prints the calendar for an entire year as returned by  :func:`calendar`.
+   Prints the calendar for an entire year as returned by
+   :func:`~calendar.calendar`.
 
 
 .. function:: calendar(theyear, w=2, l=1, c=6, m=3)
 
@@ -3758,9 +3758,9 @@ fields, or any other data types containing pointer type fields.
 .. class:: CFieldInfo(anonymous=False, bit_width=None)
    :module: ctypes.util
 
-   Information regarding a structure field defined by the :func:`struct`
-   decorator. This should be used in the second argument of a
-   :class:`typing.Annotated` wrapping a ctypes type.
+   Information regarding a structure field defined by the
+   :func:`~ctypes.util.struct` decorator. This should be used in the second
+   argument of a :class:`typing.Annotated` wrapping a ctypes type.
 
    *anonymous* specifies whether the field will be present in the
    :attr:`~ctypes.Structure._anonymous_` attribute of the generated class.
 
@@ -1386,9 +1386,9 @@ Instance methods:
    hour=self.hour, minute=self.minute, second=self.second, microsecond=self.microsecond, \
    tzinfo=self.tzinfo, *, fold=0)
 
-   Return a new :class:`datetime` object with the same attributes, but with
-   specified parameters updated. Note that ``tzinfo=None`` can be specified to
-   create a naive datetime from an aware datetime with no conversion of date
+   Return a new :class:`~datetime.datetime` object with the same attributes, but
+   with specified parameters updated. Note that ``tzinfo=None`` can be specified
+   to create a naive datetime from an aware datetime with no conversion of date
    and time data.
 
    :class:`.datetime` objects are also supported by generic function
 
@@ -395,9 +395,9 @@ operation is being performed, so the intermediate analysis object isn't useful:
    source line information (if any) is taken directly from the disassembled code
    object.
 
-   The *adaptive* parameter works as it does in :func:`dis`.
+   The *adaptive* parameter works as it does in :func:`~dis.dis`.
 
-   The *show_jit* parameter works as it does in :func:`dis`.
+   The *show_jit* parameter works as it does in :func:`~dis.dis`.
 
    .. versionadded:: 3.4
 
 
@@ -53,7 +53,8 @@ a :class:`!str` filename, and vice-versa.
 
 Finally, note that :deco:`functools.lru_cache` with a *maxsize* of 32768
 is used to cache the (typed) compiled regex patterns in the following
-functions: :func:`fnmatch`, :func:`fnmatchcase`, :func:`.filter`, :func:`.filterfalse`.
+functions: :func:`~fnmatch.fnmatch`, :func:`fnmatchcase`, :func:`.filter`,
+:func:`.filterfalse`.
 
 
 .. function:: fnmatch(name, pat)
 
@@ -80,10 +80,10 @@ exception:
 
 .. function:: gnu_getopt(args, shortopts, longopts=[])
 
-   This function works like :func:`getopt`, except that GNU style scanning mode is
-   used by default. This means that option and non-option arguments may be
-   intermixed. The :func:`getopt` function stops processing options as soon as a
-   non-option argument is encountered.
+   This function works like :func:`~getopt.getopt`, except that GNU style
+   scanning mode is used by default. This means that option and non-option
+   arguments may be intermixed. The :func:`~getopt.getopt` function stops
+   processing options as soon as a non-option argument is encountered.
 
    If the first character of the option string is ``'+'``, or if the environment
    variable :envvar:`!POSIXLY_CORRECT` is set, then option processing stops as
 
@@ -27,13 +27,14 @@ The :mod:`!getpass` module provides two functions:
    typed character is replaced by it. For example, ``echo_char='*'`` will
    display asterisks instead of the actual input.
 
-   If echo-free input is unavailable, :func:`getpass` falls back to printing
-   a warning message to *stream* and reading from :data:`sys.stdin` and
+   If echo-free input is unavailable, :func:`~getpass.getpass` falls back to
+   printing a warning message to *stream* and reading from :data:`sys.stdin` and
    issuing a :exc:`GetPassWarning`.
 
    .. note::
-      If you call :func:`getpass` from within IDLE, the input may be done in the
-      terminal you launched IDLE from rather than the idle window itself.
+      If you call :func:`~getpass.getpass` from within IDLE, the input may be
+      done in the terminal you launched IDLE from rather than the idle window
+      itself.
 
    .. note::
       On Unix systems, when *echo_char* is set, the terminal will be
 
@@ -89,8 +89,9 @@ class-based API instead.
 .. function:: dnpgettext(domain, context, singular, plural, n, /)
 
    Similar to the corresponding functions without the ``p`` in the prefix (that
-   is, :func:`gettext`, :func:`dgettext`, :func:`ngettext`, :func:`dngettext`),
-   but the translation is restricted to the given message *context*.
+   is, :func:`~gettext.gettext`, :func:`dgettext`, :func:`ngettext`,
+   :func:`dngettext`), but the translation is restricted to the given message
+   *context*.
 
    .. versionadded:: 3.8
 
@@ -426,7 +427,8 @@ take the following steps:
 
 In order to prepare your code for I18N, you need to look at all the strings in
 your files.  Any string that needs to be translated should be marked by wrapping
-it in ``_('...')`` --- that is, a call to the function :func:`_ <gettext>`.  For example::
+it in ``_('...')`` --- that is, a call to the function
+:func:`_ <gettext.gettext>`.  For example::
 
    filename = 'mylog.txt'
    message = _('writing a log message')