Address reviewer comments.

Author: Yhg1s

peps/pep-0810.rst

@@ -1410,14 +1410,16 @@ Allowing the filter to force lazy imports even when globally disabled
 ---------------------------------------------------------------------
 
 As lazy imports allow some forms of circular imports that would otherwise
-fail, as an intentional and desireable thing (especially for typing-related
-imports), the suggestion was made to add a way to override the global
-disable, like allowing the lazy imports filter to override the global
-disable the way it can override a global enable. The risk here is that we
-end up in a confusing situation where some things are overridden and others
-are not depending on the relevant priority as we perceive them now, and that
-we'll need new ways to disable or enable as the use of lazy imports evolves.
-The global disable is not expected to see commonplace use, but be more of a
+fail, as an intentional and desirable thing (especially for typing-related
+imports), there was a suggestion to add a way to override the global disable
+and force particular imports to be lazy, for instance by calling the lazy
+imports filter even if lazy imports are globally disabled.
+
+This approach could a complex hierarchy of the different "override" systems,
+making it much harder to analyze and reason about the code. Additionally,
+this may require additional complexity to introduce finer-grained systems to
+enable or disable particular imports as the use of lazy imports evolves. The
+global disable is not expected to see commonplace use, but be more of a
 debugging and selective testing tool for those who want to tightly control
 their dependency on lazy imports. We think it's reasonable for package
 mantainers, as they update packages to adopt lazy imports, to decide to