Clarify text.

Author: Yhg1s

peps/pep-0810.rst

@@ -1419,9 +1419,9 @@ 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
 debugging and selective testing tool for those who want to tightly control
-their dependency on lazy imports. We don't think it's unreasonable as
-packages to adopt lazy imports for them to decide to not work with lazy
-imports globally disabled, if that's what they want.
+their dependency on lazy imports. We don't think it's unreasonable for
+package mantainers, as they update packages to adopt lazy imports, to decide
+to *not* support running with lazy imports globally disabled.
 
 It may be that this means that in time, as more and more packages embrace
 both typing and lazy imports, the global disable becomes mostly unused and