summaryrefslogtreecommitdiff
path: root/doc/source/reference/c-api/array.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/source/reference/c-api/array.rst')
-rw-r--r--doc/source/reference/c-api/array.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/source/reference/c-api/array.rst b/doc/source/reference/c-api/array.rst
index ccff2ae91..bb22a1b03 100644
--- a/doc/source/reference/c-api/array.rst
+++ b/doc/source/reference/c-api/array.rst
@@ -152,7 +152,7 @@ and its sub-types).
.. c:function:: int PyArray_FinalizeFunc(PyArrayObject* arr, PyObject* obj)
- The function pointed to by the CObject
+ The function pointed to by the :c:type:`PyCapsule`
:obj:`~numpy.class.__array_finalize__`.
The first argument is the newly created sub-type. The second argument
(if not NULL) is the "parent" array (if the array was created using
@@ -1337,7 +1337,7 @@ Special functions for NPY_OBJECT
by NumPy. Users **should** also ensure to pass fully initialized buffers
to NumPy, since NumPy may make this a strong requirement in the future.
- There is currently an intention to ensure that NumPy always initalizes
+ There is currently an intention to ensure that NumPy always initializes
object arrays before they may be read. Any failure to do so will be
regarded as a bug.
In the future, users may be able to rely on non-NULL values when reading