diff options
Diffstat (limited to 'Doc/api')
| -rw-r--r-- | Doc/api/intro.tex | 2 | ||||
| -rw-r--r-- | Doc/api/memory.tex | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/api/intro.tex b/Doc/api/intro.tex index d27a116..752100d 100644 --- a/Doc/api/intro.tex +++ b/Doc/api/intro.tex @@ -277,7 +277,7 @@ set_all(PyObject *target, PyObject *item) The situation is slightly different for function return values. While passing a reference to most functions does not change your ownership responsibilities for that reference, many functions that -return a referece to an object give you ownership of the reference. +return a reference to an object give you ownership of the reference. The reason is simple: in many cases, the returned object is created on the fly, and the reference you get is the only reference to the object. Therefore, the generic functions that return object diff --git a/Doc/api/memory.tex b/Doc/api/memory.tex index 3da6860..3dbe9a5 100644 --- a/Doc/api/memory.tex +++ b/Doc/api/memory.tex @@ -134,7 +134,7 @@ that \var{TYPE} refers to any C type. In addition, the following macro sets are provided for calling the Python memory allocator directly, without involving the C API functions listed above. However, note that their use does not preserve binary -compatibility accross Python versions and is therefore deprecated in +compatibility across Python versions and is therefore deprecated in extension modules. \cfunction{PyMem_MALLOC()}, \cfunction{PyMem_REALLOC()}, \cfunction{PyMem_FREE()}. |