DOC: fix typo in indexing section

1 files changed, 8 insertions, 7 deletions

diff --git a/doc/source/reference/arrays.scalars.rst b/doc/source/reference/arrays.scalars.rst
index 4acaf1b3b..f76087ce2 100644
--- a/doc/source/reference/arrays.scalars.rst
+++ b/doc/source/reference/arrays.scalars.rst
@@ -248,7 +248,8 @@ Indexing
 Array scalars can be indexed like 0-dimensional arrays: if *x* is an
 array scalar,
 
-- ``x[()]`` returns a 0-dimensional :class:`ndarray`
+- ``x[()]`` returns a copy of array scalar
+- ``x[...]`` returns a 0-dimensional :class:`ndarray`
 - ``x['field-name']`` returns the array scalar in the field *field-name*.
   (*x* can have fields, for example, when it corresponds to a structured data type.)
 
@@ -282,10 +283,10 @@ Defining new types
 ==================
 
 There are two ways to effectively define a new array scalar type
-(apart from composing structured types :ref:`dtypes <arrays.dtypes>` from 
-the built-in scalar types): One way is to simply subclass the 
-:class:`ndarray` and overwrite the methods of interest. This will work to 
-a degree, but internally certain behaviors are fixed by the data type of 
-the array.  To fully customize the data type of an array you need to 
-define a new data-type, and register it with NumPy. Such new types can only 
+(apart from composing structured types :ref:`dtypes <arrays.dtypes>` from
+the built-in scalar types): One way is to simply subclass the
+:class:`ndarray` and overwrite the methods of interest. This will work to
+a degree, but internally certain behaviors are fixed by the data type of
+the array.  To fully customize the data type of an array you need to
+define a new data-type, and register it with NumPy. Such new types can only
 be defined in C, using the :ref:`NumPy C-API <c-api>`.