fixup! fixup! PEP 810: Updates based on feedback

Author: pablogsal

peps/pep-0810.rst

@@ -366,10 +366,10 @@ Reification
 
 When a lazy object is first used, it needs to be reified. This means resolving
 the import at that point in the program and replacing the lazy object with the
-concrete one. Lazy modules are imported using the import system at the time of
-reification. The value of ``__import__`` and all import system state (e.g.,
-``sys.path``, ``sys.meta_path``, ``sys.path_hooks``) are resolved at
-reification time, not when the lazy import statement is executed.
+concrete one. Reification imports the module in the same way as it would have
+been if it had been imported eagerly, barring intervening changes to the
+import system (e.g. to ``sys.path``, ``sys.meta_path``, ``sys.path_hooks`` or
+``__import__``).
 
 Reification still calls ``__import__`` to resolve the import. When the module
 is first reified, it's removed from ``sys.lazy_modules`` (even if there are
@@ -1439,11 +1439,6 @@ any eager import.
 
   print('json' in sys.modules)  # True
 
-Note that the import system state (including ``sys.path`` and ``__import__``)
-is evaluated at reification time, not when the lazy import statement executes.
-This means that modifications to the import system between the lazy import
-statement and first use will affect how the module is resolved.
-
 Does ``lazy from __future__ import feature`` work?
 --------------------------------------------------