summaryrefslogtreecommitdiff
path: root/numpy/doc/indexing.py
diff options
context:
space:
mode:
authorVraj Mohan <r.vrajmohan@gmail.com>2015-05-27 21:19:09 -0400
committerVraj Mohan <r.vrajmohan@gmail.com>2015-05-27 21:19:09 -0400
commiteb4c08d6a4918b223009245027ad92f37c4e0655 (patch)
treef49ed2a26577e8e293f8dc4442e2eea86c053b54 /numpy/doc/indexing.py
parent0794d8f072ae8fc74550a661d646dc122fd47576 (diff)
downloadnumpy-eb4c08d6a4918b223009245027ad92f37c4e0655.tar.gz
DOC: Fix typo and some grammar
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 d3f442c21..0891e7c8d 100644
--- a/numpy/doc/indexing.py
+++ b/numpy/doc/indexing.py
@@ -50,7 +50,7 @@ than dimensions, one gets a subdimensional array. For example: ::
That is, each index specified selects the array corresponding to the
rest of the dimensions selected. In the above example, choosing 0
-means that remaining dimension of lenth 5 is being left unspecified,
+means that the remaining dimension of length 5 is being left unspecified,
and that what is returned is an array of that dimensionality and size.
It must be noted that the returned array is not a copy of the original,
but points to the same values in memory as does the original array.
@@ -62,7 +62,7 @@ element being returned. That is: ::
2
So note that ``x[0,2] = x[0][2]`` though the second case is more
-inefficient a new temporary array is created after the first index
+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