DOC: fix typos / wording

Co-authored-by: Greg Lucas <[email protected]>

Author: tacaswell

doc/api/index.rst

@@ -115,15 +115,15 @@ Usage patterns
 --------------
 
 Below we describe several common approaches to plotting with Matplotlib.  See
-:ref:`api_interfaces` for an explanation of the trade off of the supported user
+:ref:`api_interfaces` for an explanation of the trade-offs between the supported user
 APIs.
 
 
-The Explicit API
+The explicit API
 ^^^^^^^^^^^^^^^^
 
 At its core, Matplotlib is an object-oriented library. We recommend directly
-working with the objects, if you need more control and customization of your
+working with the objects if you need more control and customization of your
 plots.
 
 In many cases you will create a `.Figure` and one or more

examples/misc/pythonic_matplotlib.py

@@ -3,9 +3,9 @@
 Pythonic Matplotlib
 ===================
 
-Some people prefer to write more "Pythonic", explicitly object-oriented code
-rather than use the implicit pyplot interface to Matplotlib.  This example
-shows you how.
+Some people prefer to write more "Pythonic", explicit object-oriented code,
+rather than use the implicit pyplot interface to Matplotlib. This example
+shows you how to take advantage of the explicit Matplotlib interface.
 
 Unless you are an application developer, I recommend using part of the
 pyplot interface, particularly the figure, close, subplot, axes, and

examples/subplots_axes_and_figures/multiple_figs_demo.py

@@ -10,11 +10,11 @@
 
 .. note::
 
-    We discourage working with multiple figures in implicit pyplot interface
+    We discourage working with multiple figures through the implicit pyplot interface
     because managing the *current figure* is cumbersome and
-    error-prone. Instead, we recommend to use the explicit approach and call
+    error-prone. Instead, we recommend using the explicit approach and call
     methods on Figure and Axes instances. See :ref:`api_interfaces` for an
-    explanation of the tradeoffs between the implicit and explicit interfaces.
+    explanation of the trade-offs between the implicit and explicit interfaces.
 
 """
 import matplotlib.pyplot as plt

lib/matplotlib/__init__.py

@@ -19,7 +19,7 @@
 
 For the most part, direct use of the explicit object-oriented library is
 encouraged when programming; the implicit pyplot interface is primarily for
-working interactively.  The exceptions are the pyplot functions
+working interactively. The exceptions to this suggestion are the pyplot functions
 `.pyplot.figure`, `.pyplot.subplot`, `.pyplot.subplots`, and `.pyplot.savefig`,
 which can greatly simplify scripting.  See :ref:`api_interfaces` for an
 explanation of the tradeoffs between the implicit and explicit interfaces.

tutorials/introductory/lifecycle.py

@@ -20,7 +20,7 @@
 A note on the explicit vs. implicit interfaces
 ==============================================
 
-Matplotlib has two interfaces. For an explanation of the tradeoffs between the
+Matplotlib has two interfaces. For an explanation of the trade-offs between the
 implicit and explicit interfaces see :ref:`api_interfaces`.
 
 The first is an explicit object-oriented (OO) interface. In this case, we

tutorials/introductory/pyplot.py

@@ -5,7 +5,7 @@
 
 An introduction to the pyplot interface.  Please also see
 :doc:`/tutorials/introductory/quick_start` for an overview of how Matplotlib
-works and :ref:`api_interfaces` for an explanation of the trade off of the
+works and :ref:`api_interfaces` for an explanation of the trade-offs between the
 supported user APIs.
 
 """