From cace2a7af58ea0b708c7a8fe6522a6d8f21d96ab Mon Sep 17 00:00:00 2001
From: dereckduran <67027239+dereckduran@users.noreply.github.com>
Date: Mon, 17 Nov 2025 03:44:44 -0800
Subject: [PATCH] gh-62480: De-personalize "Coping with mutable arguments"
 section in `unittest.mock` examples (GH-141323) (cherry picked from commit
 d527d3bf8beb9cd26c179f2c0111d635cdaa9cd3)

Co-authored-by: dereckduran <67027239+dereckduran@users.noreply.github.com>
---
 Doc/library/unittest.mock-examples.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Doc/library/unittest.mock-examples.rst b/Doc/library/unittest.mock-examples.rst
index 6af4298d44f..61c75b5a03b 100644
--- a/Doc/library/unittest.mock-examples.rst
+++ b/Doc/library/unittest.mock-examples.rst
@@ -863,9 +863,9 @@ Here's one solution that uses the :attr:`~Mock.side_effect`
 functionality. If you provide a ``side_effect`` function for a mock then
 ``side_effect`` will be called with the same args as the mock. This gives us an
 opportunity to copy the arguments and store them for later assertions. In this
-example I'm using *another* mock to store the arguments so that I can use the
+example we're using *another* mock to store the arguments so that we can use the
 mock methods for doing the assertion. Again a helper function sets this up for
-me. ::
+us. ::
 
     >>> from copy import deepcopy
     >>> from unittest.mock import Mock, patch, DEFAULT