gh-148588: Use 'fully qualified module name' consistently

Author: johnslavik

Doc/reference/datamodel.rst

@@ -1124,7 +1124,7 @@ the following writable attributes:
 
 .. attribute:: module.__lazy_modules__
 
-   An optional :term:`iterable` of absolute module name strings.  When defined
+   An optional :term:`iterable` of fully qualified module name strings.  When defined
    at module scope, any regular :keyword:`import` statement in that module whose
    target module name appears in this iterable is treated as a
    :ref:`lazy import <lazy-imports>`, as if the :keyword:`lazy` keyword had

Doc/reference/simple_stmts.rst

@@ -931,7 +931,7 @@ Compatibility mode via ``__lazy_modules__``
 As an alternative to using the :keyword:`lazy` keyword, a module can opt
 into lazy loading for specific imports by defining a module-level
 :attr:`~module.__lazy_modules__` variable.  When present, it must be an
-:term:`iterable` of absolute module name strings.  Any regular (non-``lazy``)
+:term:`iterable` of fully qualified module name strings.  Any regular (non-``lazy``)
 :keyword:`import` statement at module scope whose target appears in
 :attr:`!__lazy_modules__` is treated as a lazy import, exactly as if the
 :keyword:`lazy` keyword had been used.
@@ -948,7 +948,7 @@ Python versions older than 3.15 while leveraging lazy imports on 3.15+::
    import pathlib  # loaded lazily
 
 Relative imports are resolved to their absolute name before the lookup, so
-the sequence must always contain absolute module names.
+the sequence must always contain fully qualified module names.
 
 Imports inside functions, class bodies, or
 :keyword:`try`/:keyword:`except`/:keyword:`finally` blocks are always eager,

Doc/whatsnew/3.15.rst

@@ -185,7 +185,7 @@ raise :exc:`SyntaxError`).
 For code that cannot use the ``lazy`` keyword directly (for example, when
 supporting Python versions older than 3.15 while still leveraging lazy
 imports on 3.15+), a module can define
-:attr:`~module.__lazy_modules__` as an :term:`iterable` of absolute module
+:attr:`~module.__lazy_modules__` as an :term:`iterable` of fully qualified module
 name strings.  Regular ``import`` statements for those modules are then treated
 as lazy, with the same semantics as the ``lazy`` keyword::