summaryrefslogtreecommitdiff
path: root/numpy/doc/indexing.py
diff options
context:
space:
mode:
Diffstat (limited to 'numpy/doc/indexing.py')
-rw-r--r--numpy/doc/indexing.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/numpy/doc/indexing.py b/numpy/doc/indexing.py
index 33e9de3c4..3e3e95641 100644
--- a/numpy/doc/indexing.py
+++ b/numpy/doc/indexing.py
@@ -65,7 +65,7 @@ inefficient as a new temporary array is created after the first index
that is subsequently indexed by 2.
Note to those used to IDL or Fortran memory order as it relates to
-indexing. Numpy uses C-order indexing. That means that the last
+indexing. NumPy uses C-order indexing. That means that the last
index usually represents the most rapidly changing memory location,
unlike Fortran or IDL, where the first index represents the most
rapidly changing location in memory. This difference represents a
@@ -111,7 +111,7 @@ specific function.
Index arrays
============
-Numpy arrays may be indexed with other arrays (or any other sequence-
+NumPy arrays may be indexed with other arrays (or any other sequence-
like object that can be converted to an array, such as lists, with the
exception of tuples; see the end of this document for why this is). The
use of index arrays ranges from simple, straightforward cases to