matplotlib
diff --git a/‎doc/users/explain/interactive_guide.rst
Copy file name to clipboardExpand all lines: doc/users/explain/interactive_guide.rst
+2-2Lines changed: 2 additions & 2 deletions b/‎doc/users/explain/interactive_guide.rst
Copy file name to clipboardExpand all lines: doc/users/explain/interactive_guide.rst
+2-2Lines changed: 2 additions & 2 deletions
@@ -166,8 +166,8 @@ takes over again.
 This time-share technique only allows the event loop to run while
 python is otherwise idle and waiting for user input.  If you want the
 GUI to be responsive during long running code it is necessary to
-periodically flush the GUI event queue as described :ref:`above
-<spin_event_loop>`.  In this case it is your code, not the REPL, which
+periodically flush the GUI event queue as described :ref:`spin_event_loop`.
+In this case it is your code, not the REPL, which
 is blocking the process so you need to handle the "time-share" manually.
 Conversely, a very slow figure draw will block the prompt until it
 finishes drawing.