From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Sat, 15 Feb 2025 03:37:05 +0000 (+0100)
Subject: [3.13] gh-130106: Fix a typo in unittest.mock doc (GH-130107) (#130143)
X-Git-Tag: v3.13.3~274
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=e5ee784a7c04fd578b8711e1fd859295173f1830;p=thirdparty%2FPython%2Fcpython.git

[3.13] gh-130106: Fix a typo in unittest.mock doc (GH-130107) (#130143)

gh-130106: Fix a typo in unittest.mock doc (GH-130107)
(cherry picked from commit d2e60d8e598b622573b68b80b4fbf98c021dd087)

Co-authored-by: Srinivas Reddy Thatiparthy (తాటిపర్తి శ్రీనివాస్  రెడ్డి) <thatiparthysreenivas@gmail.com>
---

diff --git a/Doc/library/unittest.mock.rst b/Doc/library/unittest.mock.rst
index 514c6b7e6152..2c3574067a84 100644
--- a/Doc/library/unittest.mock.rst
+++ b/Doc/library/unittest.mock.rst
@@ -1984,7 +1984,7 @@ Imagine we have a project that we want to test with the following structure::
 
 Now we want to test ``some_function`` but we want to mock out ``SomeClass`` using
 :func:`patch`. The problem is that when we import module b, which we will have to
-do then it imports ``SomeClass`` from module a. If we use :func:`patch` to mock out
+do when it imports ``SomeClass`` from module a. If we use :func:`patch` to mock out
 ``a.SomeClass`` then it will have no effect on our test; module b already has a
 reference to the *real* ``SomeClass`` and it looks like our patching had no
 effect.