summaryrefslogtreecommitdiff
path: root/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst')
-rw-r--r--doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst b/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst
index 6d1f8bf27..5ec01081a 100644
--- a/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst
+++ b/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst
@@ -351,7 +351,7 @@ backend type:
type(np.asarray([1, 2, 3], like=da.array(cp.array(()))).compute())
Note how above the array is backed by ``chunktype=cupy.ndarray``, and the
-resulting array after computing it is also a ``cupy.ndarray``. If Dask does
+resulting array after computing it is also a ``cupy.ndarray``. If Dask did
not use the ``like=`` argument via the ``self`` attribute from
``__array_function__``, the example above would be backed by ``numpy.ndarray``
instead: