Merge pull request #24686 from rcomer/backport-24003-doc

oscargus · web-flow · commit a22a334b3d26 · 2022-12-10T14:45:55.000+01:00
Backport PR #24003 on branch v3.6.2-doc: Fix wording and links lifecycle tutorial
diff --git a/tutorials/introductory/lifecycle.py b/tutorials/introductory/lifecycle.py
@@ -26,24 +26,24 @@
 In the explicit object-oriented (OO) interface we directly utilize instances of
 :class:`axes.Axes` to build up the visualization in an instance of
 :class:`figure.Figure`.  In the implicit interface, inspired by and modeled on
-MATLAB, uses an global state-based interface which is is encapsulated in the
+MATLAB, we use a global state-based interface which is encapsulated in the
 :mod:`.pyplot` module to plot to the "current Axes".  See the :doc:`pyplot
 tutorials </tutorials/introductory/pyplot>` for a more in-depth look at the
 pyplot interface.
 
 Most of the terms are straightforward but the main thing to remember
 is that:
 
-* The Figure is the final image that may contain 1 or more Axes.
-* The Axes represent an individual plot (don't confuse this with the word
-  "axis", which refers to the x/y axis of a plot).
+* The `.Figure` is the final image, and may contain one or more `~.axes.Axes`.
+* The `~.axes.Axes` represents an individual plot (not to be confused with
+   `~.axis.Axis`, which refers to the x/y axis of a plot).
 
 We call methods that do the plotting directly from the Axes, which gives
 us much more flexibility and power in customizing our plot.
 
 .. note::
 
-   In general prefer the explicit interface over the implicit pyplot interface
+   In general, use the explicit interface over the implicit pyplot interface
    for plotting.
 
 Our data
