matplotlib
diff --git a/‎galleries/users_explain/figure/interactive_guide.rst‎
Lines changed: 11 additions & 10 deletions b/‎galleries/users_explain/figure/interactive_guide.rst‎
Lines changed: 11 additions & 10 deletions
@@ -405,17 +405,18 @@ The hook functions typically exhaust all pending events on the GUI
 event queue, run the main loop for a short fixed amount of time, or
 run the event loop until a key is pressed on stdin.
 
-Matplotlib does not currently do any management of :c:data:`PyOS_InputHook` due
-to the wide range of ways that Matplotlib is used.  This management is left to
-downstream libraries -- either user code or the shell.  Interactive figures,
-even with Matplotlib in "interactive mode", may not work in the vanilla python
-repl if an appropriate :c:data:`PyOS_InputHook` is not registered.
-
-Input hooks, and helpers to install them, are usually included with
-the python bindings for GUI toolkits and may be registered on import.
+Interactive figures, even with Matplotlib in "interactive mode", may not work
+in REPL if an appropriate :c:data:`PyOS_InputHook` is not registered.  This
+management is left to upstream libraries or downstream code -- either explicit
+user code or shell initialization -- in all backends but the native Mac
+backend.  Input hooks, and helpers to install them, are usually included with
+the Python bindings for GUI toolkits and may be registered on import.  For the
+Mac backend Matplotlib owns the code wrapping the native GUI toolkit and we
+register :c:data:`PyOS_InputHook` on application initialization.
+
 IPython also ships input hook functions for all of the GUI frameworks
-Matplotlib supports which can be installed via ``%matplotlib``.  This
-is the recommended method of integrating Matplotlib and a prompt.
+Matplotlib supports which can be installed via ``%matplotlib``.  This is the
+recommended method of integrating Matplotlib and a prompt.
 
 
 IPython / prompt_toolkit