summaryrefslogtreecommitdiff
path: root/doc/neps
diff options
context:
space:
mode:
authorPeter Andreas Entschev <peter@entschev.com>2020-08-19 18:44:09 +0200
committerGitHub <noreply@github.com>2020-08-19 18:44:09 +0200
commit17620c2ecb3dc6c2ab3164fa946c373a120d5619 (patch)
tree6f0501f350ce40f05fd43476a3a9cab9152ce981 /doc/neps
parenta82cc4b5cb4c3926d2b555d9e8da1146c472a17c (diff)
downloadnumpy-17620c2ecb3dc6c2ab3164fa946c373a120d5619.tar.gz
Update doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
Diffstat (limited to 'doc/neps')
-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