Update pep-0810.rst

Co-authored-by: T. Wouters <thomas@python.org>

Author: pablogsal

peps/pep-0810.rst

@@ -465,13 +465,15 @@ the object. Calling ``dir()`` at the global scope will not reify the globals
 and calling ``dir(mod)`` will be special cased in ``mod.__dir__`` to avoid
 reification as well.
 
-However, calling ``globals()`` or accessing a module's ``__dict__`` does **not**
-trigger reification -- they return the module's dictionary, and accessing lazy
-objects through that dictionary still returns lazy proxy objects that need to
-be manually reified upon use. A lazy object can be resolved explicitly by
-calling the ``resolve`` method. Other, more indirect ways of accessing
-arbitrary globals (e.g. inspecting ``frame.f_globals``) also do **not** reify
-all the objects.
+However, calling ``globals()`` or accessing a module's ``__dict__`` does
+**not** trigger reification -- they return the module's dictionary, and
+accessing lazy objects through that dictionary still returns lazy proxy
+objects that need to be manually reified upon use. A lazy object can be
+resolved explicitly by calling the ``resolve`` method. Calling ``dir()`` at
+the global scope will not reify the globals, nor will calling ``dir(mod)``
+(through special-casing in ``mod.__dir__``.) Other, more indirect ways of
+accessing arbitrary globals (e.g. inspecting ``frame.f_globals``) also do
+**not** reify all the objects.
 
 Example using ``globals()`` and ``__dict__``: