DOC: edits from review

Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
matplotlib · QuLogic · May 21, 2020 · Jul 24, 2015 · Jul 31, 2015 · Jan 7, 2017
commit eda2ed3f539415eec040996474681b21443de13f
diff --git a/doc/users/interactive.rst b/doc/users/interactive.rst
@@ -15,7 +15,7 @@ tools are sufficient, but you can also use the Matplotlib event system
 to build customized data exploration tools.
 
 Matplotlib ships with :ref:`backends <what-is-a-backend>` binding to
-several GUI toolkits (Qt, Tk, Wx, Gtk, OSX, js) and third party
+several GUI toolkits (Qt, Tk, Wx, GTK, macOS, JavaScript) and third party
 packages provide bindings to `kivy
 <https://github.com/kivy-garden/garden.matplotlib>`__ and `Jupyter Lab
 <https://github.com/matplotlib/ipympl>`__.  For the figures to be
@@ -288,7 +288,7 @@ If you are running your jupyter kernel locally you can use one of the
 GUI backends.  The process running your kernel will show a GUI window
 on your desktop adjacent to your web browser.  However if you move
 that notebook to a remote server the kernel will try to open the GUI
-window on _that_ computer.  Unless you have arranged to forward the
+window on *that* computer.  Unless you have arranged to forward the
 xserver back to your desktop, you not be able to see or interact with
 the figure (if it does not raise an exception outright).
 

diff --git a/doc/users/interactive_guide.rst b/doc/users/interactive_guide.rst
@@ -393,7 +393,7 @@ Eventloop integration mechanism
 CPython / readline
 ------------------
 
-The python capi provides a hook, :c:var:`PyOS_InputHook`, to register a
+The Python C API provides a hook, :c:var:`PyOS_InputHook`, to register a
 function to be run "The function will be called when Python's
 interpreter prompt is about to become idle and wait for user input
 from the terminal.".  This hook can be used to integrate a second
@@ -404,7 +404,7 @@ run the event loop until a key is pressed on stdin.
 
 
 Matplotlib does not currently do any management of
-:c:var:`PyOS_InputHook` due to the wide range of ways that matplotlib
+:c:var:`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
@@ -422,9 +422,9 @@ IPython / prompt toolkit
 
 With IPython >= 5.0 IPython has changed from using cpython's readline
 based prompt to a ``prompt_toolkit`` based prompt.  ``prompt_toolkit``
-has the same conceptual input hook, which is feed into prompt_toolkit via the
+has the same conceptual input hook, which is fed into ``prompt_toolkit`` via the
 :meth:`IPython.terminal.interactiveshell.TerminalInteractiveShell.inputhook`
-method.  The source for the prompt_toolkit input hooks lives at
+method.  The source for the ``prompt_toolkit`` input hooks lives at
 :mod:`IPython.terminal.pt_inputhooks`
 
 

diff --git a/lib/matplotlib/pyplot.py b/lib/matplotlib/pyplot.py
@@ -309,11 +309,11 @@ def show(*args, **kwargs):
     """
     Display all open figures.
 
-    In non-interactive mode, **block** defaults to True.  All figures
+    In non-interactive mode, *block* defaults to True.  All figures
     will display and show will not return until all windows are closed.
     If there are no figures, return immediately.
 
-    In interactive mode **block** defaults to False.  This will ensure
+    In interactive mode *block* defaults to False.  This will ensure
     that all of the figures are shown and this function immediately returns.
 
     Parameters