Apply suggestions from code review

timhoffm · QuLogic · web-flow · commit c6425b1e809e · 2022-12-17T17:51:17.000+01:00
Co-authored-by: Elliott Sales de Andrade &lt;quantum.analyst@gmail.com&gt;
diff --git a/doc/api/next_api_changes/deprecations/24730-TH.rst b/doc/api/next_api_changes/deprecations/24730-TH.rst
@@ -6,7 +6,7 @@ Nothing will change for regular users because ``rcParams`` will continue to
 be dict-like (technically fulfill the ``MutableMapping`` interface).
 
 The `.RcParams` class does validation checking on calls to
-`.RcParams.__get_item__` and `.RcParams.__set_item__`.  However, there are rare
+``.RcParams.__getitem__`` and ``.RcParams.__setitem__``.  However, there are rare
 cases where we want to circumvents the validation logic and directly access the
 underlying data values.   Previously, this could be accomplished via  a call to
 the parent methods  ``dict.__getitem__(rcParams, key)`` and
@@ -15,7 +15,7 @@ the parent methods  ``dict.__getitem__(rcParams, key)`` and
 Matplotlib 3.7 introduces ``rcParams._set(key, val)`` and
 ``rcParams._get(key)`` as a replacement to calling the parent methods. They are
 intentionally marked private because there is little need for external users
-to use them. However, if you have a compelling reason for direct `.RcParam`
+to use them. However, if you have a compelling reason for direct `.RcParams`
 data access, please switch from the dict functions to the new ``_get()`` and
 ``_set()``. Even though marked private, we guarantee API stability for these
 methods and they are subject to Matplotlib's API and deprecation policy.
