summaryrefslogtreecommitdiff
path: root/numpy/doc
diff options
context:
space:
mode:
Diffstat (limited to 'numpy/doc')
-rw-r--r--numpy/doc/byteswapping.py2
-rw-r--r--numpy/doc/internals.py2
2 files changed, 2 insertions, 2 deletions
diff --git a/numpy/doc/byteswapping.py b/numpy/doc/byteswapping.py
index 59c049878..22eb71e6d 100644
--- a/numpy/doc/byteswapping.py
+++ b/numpy/doc/byteswapping.py
@@ -108,7 +108,7 @@ the correct endianness:
>>> fixed_end_dtype_arr[0]
1
-Note the the array has not changed in memory:
+Note the array has not changed in memory:
>>> fixed_end_dtype_arr.tobytes() == big_end_str
True
diff --git a/numpy/doc/internals.py b/numpy/doc/internals.py
index 6bd6b1ae9..c25872bc0 100644
--- a/numpy/doc/internals.py
+++ b/numpy/doc/internals.py
@@ -49,7 +49,7 @@ uses the same data buffer. This is why it is necessary to force copies through
use of the .copy() method if one really wants to make a new and independent
copy of the data buffer.
-New views into arrays mean the the object reference counts for the data buffer
+New views into arrays mean the object reference counts for the data buffer
increase. Simply doing away with the original array object will not remove the
data buffer if other views of it still exist.