summaryrefslogtreecommitdiff
path: root/doc/neps/nep-0018-array-function-protocol.rst
diff options
context:
space:
mode:
authorMin ho Kim <minho42@gmail.com>2019-06-23 00:07:13 +1000
committerMin ho Kim <minho42@gmail.com>2019-06-23 00:07:13 +1000
commit4f0742b0f63b59adbac3e9c101de2f64c41106d6 (patch)
tree8ae0f5f43c36ccd002cf157d5102a240922be8c8 /doc/neps/nep-0018-array-function-protocol.rst
parentd037f06c85bf15140084e537d12d6cf9c5cf4fa2 (diff)
downloadnumpy-4f0742b0f63b59adbac3e9c101de2f64c41106d6.tar.gz
Fix typo
Diffstat (limited to 'doc/neps/nep-0018-array-function-protocol.rst')
-rw-r--r--doc/neps/nep-0018-array-function-protocol.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/neps/nep-0018-array-function-protocol.rst b/doc/neps/nep-0018-array-function-protocol.rst
index 27a462239..fb9b838b5 100644
--- a/doc/neps/nep-0018-array-function-protocol.rst
+++ b/doc/neps/nep-0018-array-function-protocol.rst
@@ -642,7 +642,7 @@ layer, separating NumPy's high level API from default implementations on
The downsides are that this would require an explicit opt-in from all
existing code, e.g., ``import numpy.api as np``, and in the long term
-would result in the maintainence of two separate NumPy APIs. Also, many
+would result in the maintenance of two separate NumPy APIs. Also, many
functions from ``numpy`` itself are already overloaded (but
inadequately), so confusion about high vs. low level APIs in NumPy would
still persist.