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 9fb117005..c1edfa750 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
@@ -52,7 +52,7 @@ elsewhere and let NumPy handle them. But still these arrays have to be started
in their native library and brought back. Instead if it was possible to create
these objects through NumPy API then there would be an almost complete
experience, all using NumPy syntax. For example, say we have some CuPy array
-``cp_arr`` , and want a similar CuPy array with identity matrix. We could still
+``cp_arr``, and want a similar CuPy array with identity matrix. We could still
write the following:
.. code:: python