summaryrefslogtreecommitdiff
path: root/doc/source
diff options
context:
space:
mode:
authorBen Nathanson <github@bigriver.xyz>2020-08-05 10:12:26 -0400
committermattip <matti.picus@gmail.com>2020-09-07 11:39:13 +0300
commit55cd824ac52b573273eab0f85712aead8f9a5588 (patch)
tree8f969bcf06ed0574758d957f987a39ac67c30f7c /doc/source
parent15292c9186a8b139ceaaa56aa4cafca42e787fef (diff)
downloadnumpy-55cd824ac52b573273eab0f85712aead8f9a5588.tar.gz
DOC: Fix repeated word in PR #16996
Also adding <BLANKLINE>s to some examples for clarity.
Diffstat (limited to 'doc/source')
-rw-r--r--doc/source/glossary.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/source/glossary.rst b/doc/source/glossary.rst
index c20d98b67..9bfd0d76c 100644
--- a/doc/source/glossary.rst
+++ b/doc/source/glossary.rst
@@ -58,7 +58,7 @@ Glossary
[[12, 13, 14, 15],
[16, 17, 18, 19],
[20, 21, 22, 23]]])
-
+ <BLANKLINE>
>>> a[1:,-2:,:-1]
array([[[16, 17, 18],
[20, 21, 22]]])
@@ -113,10 +113,10 @@ Glossary
and the other dimensions are left full (``:``).
>>> a = np.arange(24).reshape(2,3,4)
-
+ <BLANKLINE>
>>> a.shape
(2,3,4)
-
+ <BLANKLINE>
>>> a[:,0,:].shape
(2,4)
@@ -221,7 +221,7 @@ Glossary
If an array does not own its memory, then its
:doc:`base <reference/generated/numpy.ndarray.base>` attribute
returns the object whose memory the array is referencing. That object
- may may be borrowing the memory from still another object, so the
+ may be borrowing the memory from still another object, so the
owning object may be ``a.base.base.base...``. Despite advice to the
contrary, testing ``base`` is not a surefire way to determine if two
arrays are :term:`view`\ s.