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 b023d6fc8..e09875d15 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
@@ -108,7 +108,7 @@ CuPy arrays:
Note in the ``my_pad`` function above how ``arr`` is used as a reference to
dictate what array type padding should have, before concatenating the arrays to
produce the result. On the other hand, if ``like=`` wasn't used, the NumPy case
-case would still work, but CuPy wouldn't allow this kind of automatic
+would still work, but CuPy wouldn't allow this kind of automatic
conversion, ultimately raising a
``TypeError: Only cupy arrays can be concatenated`` exception.