FIX

jklymak · jklymak · commit d00e472c3bc1 · 2021-12-16T11:07:51.000+01:00
diff --git a/doc/users/explain/api_interfaces.rst b/doc/users/explain/api_interfaces.rst
@@ -189,7 +189,7 @@ Third-party library "Data-object" interfaces
 --------------------------------------------
 
 Some third party libraries have chosen to implement plotting for their data
-objects, e.g. `data.plot()`, is seen in `pandas`, `xarray`, and other
+objects, e.g. ``data.plot()``, is seen in `pandas`, `xarray`, and other
 third-party libraries.  For illustrative purposes, a downstream library may
 implement a simple data container that has ``x`` and ``y`` data stored together,
 and then implements a ``plot`` method:
@@ -273,14 +273,14 @@ Most `~.axes.Axes` methods allow yet another API addressing by passing a
     import matplotlib.pyplot as plt
 
     data = {'xdat': [0, 1, 2, 3], 'ydat': [0, 0.2, 0.4, 0.1]}
-    fig, ax = plt.subplots()
+    fig, ax = plt.subplots(figsize=(2, 2))
     ax.plot('xdat', 'ydat', data=data)
 
 
 Appendix: "pylab" interface
 ---------------------------
 
 There is one further interface that is highly discouraged, and that is to
-basically do `from matplotlib.pyplot import *`.  This allows users to simply
-call `plot(x, y)`.  While convenient, this can lead to obvious problems if the
+basically do ``from matplotlib.pyplot import *``.  This allows users to simply
+call ``plot(x, y)``.  While convenient, this can lead to obvious problems if the
 user unwittingly names a variable the same name as a pyplot method.
