summaryrefslogtreecommitdiff
path: root/doc/neps/nep-0022-ndarray-duck-typing-overview.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/neps/nep-0022-ndarray-duck-typing-overview.rst')
-rw-r--r--doc/neps/nep-0022-ndarray-duck-typing-overview.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/neps/nep-0022-ndarray-duck-typing-overview.rst b/doc/neps/nep-0022-ndarray-duck-typing-overview.rst
index 47b81d9e7..8f3e09995 100644
--- a/doc/neps/nep-0022-ndarray-duck-typing-overview.rst
+++ b/doc/neps/nep-0022-ndarray-duck-typing-overview.rst
@@ -97,7 +97,7 @@ partial duck arrays. We've been guilty of this ourself.
At this point though, we think the best general strategy is to focus
our efforts primarily on supporting full duck arrays, and only worry
-about partial duck arrays as much as we need to to make sure we don't
+about partial duck arrays as much as we need to make sure we don't
accidentally rule them out for no reason.
Why focus on full duck arrays? Several reasons: