From acc0e828350b1adbfdea8329949989aeed55cd5d Mon Sep 17 00:00:00 2001 From: jianghuyiyuan Date: Thu, 1 Aug 2024 09:26:09 +0900 Subject: [PATCH] Fix typos in docs, error messages and comments (#122502) (cherry-picked from commit 46f5a4f9e1781ad8d60eb53bbaf6cd8534a286cd) Signed-off-by: jianghuyiyuan --- Doc/howto/isolating-extensions.rst | 2 +- Doc/library/threading.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/howto/isolating-extensions.rst b/Doc/howto/isolating-extensions.rst index e35855deedbe5f..a636e06bda8344 100644 --- a/Doc/howto/isolating-extensions.rst +++ b/Doc/howto/isolating-extensions.rst @@ -339,7 +339,7 @@ That is, heap types should: - Define a traverse function using ``Py_tp_traverse``, which visits the type (e.g. using ``Py_VISIT(Py_TYPE(self))``). -Please refer to the the documentation of +Please refer to the documentation of :c:macro:`Py_TPFLAGS_HAVE_GC` and :c:member:`~PyTypeObject.tp_traverse` for additional considerations. diff --git a/Doc/library/threading.rst b/Doc/library/threading.rst index 1dbf9c2614d520..5d94a7760f9f56 100644 --- a/Doc/library/threading.rst +++ b/Doc/library/threading.rst @@ -1014,7 +1014,7 @@ method. The :meth:`~Event.wait` method blocks until the flag is true. has not expired. The return value represents the reason that this blocking method returned; ``True`` if returning because the internal flag is set to true, or ``False`` if a timeout is given and - the the internal flag did not become true within the given wait time. + the internal flag did not become true within the given wait time. When the timeout argument is present and not ``None``, it should be a floating-point number specifying a timeout for the operation in seconds,