summaryrefslogtreecommitdiffstats
path: root/Doc/extending
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2024-05-26 01:13:31 (GMT)
committerGitHub <noreply@github.com>2024-05-26 01:13:31 (GMT)
commitd25954dff5409c8926d2a4053d3e892462f8b8b5 (patch)
tree46819604087f2ebf16bbdec8532127180496c0db /Doc/extending
parente418fc3a6e7bade68ab5dfe72f14ddba28e6acb5 (diff)
downloadcpython-d25954dff5409c8926d2a4053d3e892462f8b8b5.zip
cpython-d25954dff5409c8926d2a4053d3e892462f8b8b5.tar.gz
cpython-d25954dff5409c8926d2a4053d3e892462f8b8b5.tar.bz2
docs: fix a few typos identified by codespell (#119516)
Diffstat (limited to 'Doc/extending')
-rw-r--r--Doc/extending/extending.rst2
-rw-r--r--Doc/extending/newtypes.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/extending/extending.rst b/Doc/extending/extending.rst
index b70e1b1..b0493be 100644
--- a/Doc/extending/extending.rst
+++ b/Doc/extending/extending.rst
@@ -868,7 +868,7 @@ It is important to call :c:func:`free` at the right time. If a block's address
is forgotten but :c:func:`free` is not called for it, the memory it occupies
cannot be reused until the program terminates. This is called a :dfn:`memory
leak`. On the other hand, if a program calls :c:func:`free` for a block and then
-continues to use the block, it creates a conflict with re-use of the block
+continues to use the block, it creates a conflict with reuse of the block
through another :c:func:`malloc` call. This is called :dfn:`using freed memory`.
It has the same bad consequences as referencing uninitialized data --- core
dumps, wrong results, mysterious crashes.
diff --git a/Doc/extending/newtypes.rst b/Doc/extending/newtypes.rst
index 473a418..fd05c82 100644
--- a/Doc/extending/newtypes.rst
+++ b/Doc/extending/newtypes.rst
@@ -545,7 +545,7 @@ performance-critical objects (such as numbers).
.. seealso::
Documentation for the :mod:`weakref` module.
-For an object to be weakly referencable, the extension type must set the
+For an object to be weakly referenceable, the extension type must set the
``Py_TPFLAGS_MANAGED_WEAKREF`` bit of the :c:member:`~PyTypeObject.tp_flags`
field. The legacy :c:member:`~PyTypeObject.tp_weaklistoffset` field should
be left as zero.