[3.12] Use correct markup in unittest.mock.reset_mock documentation (GH-119207) ...

Use correct markup in unittest.mock.reset_mock documentation (GH-119207)
(cherry picked from commit 6b80a5b20f31a067bd1c374295608df5f1210f49)

Co-authored-by: Tialo <65392801+Tialo@users.noreply.github.com>

diff --git a/Doc/library/unittest.mock.rst b/Doc/library/unittest.mock.rst
index e8f689b1b454378f4d44e200c4d0ada892658e87..c0debf67ae37ab43b8cc69e5513c9c7839d258e6 100644 (file)
--- a/Doc/library/unittest.mock.rst
+++ b/Doc/library/unittest.mock.rst
@@ -410,13 +410,13 @@ the *new_callable* argument to :func:`patch`.
 
         This can be useful where you want to make a series of assertions that
         reuse the same object. Note that :meth:`reset_mock` *doesn't* clear the
-        return value, :attr:`side_effect` or any child attributes you have
+        :attr:`return_value`, :attr:`side_effect` or any child attributes you have
         set using normal assignment by default. In case you want to reset
-        *return_value* or :attr:`side_effect`, then pass the corresponding
+        :attr:`return_value` or :attr:`side_effect`, then pass the corresponding
         parameter as ``True``. Child mocks and the return value mock
         (if any) are reset as well.
 
-        .. note:: *return_value*, and :attr:`side_effect` are keyword-only
+        .. note:: *return_value*, and *side_effect* are keyword-only
                   arguments.