From 9691c99974d9941968212a965f67e783bd9d5449 Mon Sep 17 00:00:00 2001 From: "Adam J. Stewart" Date: Thu, 2 Aug 2018 18:26:46 -0500 Subject: [PATCH] Documentation: typo fixes in MultiIndex / Advanced Indexing (#22179) --- doc/source/advanced.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/source/advanced.rst b/doc/source/advanced.rst index e530ece2e12c5..2be1a53aa6c93 100644 --- a/doc/source/advanced.rst +++ b/doc/source/advanced.rst @@ -21,7 +21,7 @@ See the :ref:`Indexing and Selecting Data ` for general indexing docum .. warning:: - Whether a copy or a reference is returned for a setting operation, may + Whether a copy or a reference is returned for a setting operation may depend on the context. This is sometimes called ``chained assignment`` and should be avoided. See :ref:`Returning a View versus Copy `. @@ -172,7 +172,7 @@ Defined Levels ~~~~~~~~~~~~~~ The repr of a ``MultiIndex`` shows all the defined levels of an index, even -if the they are not actually used. When slicing an index, you may notice this. +if they are not actually used. When slicing an index, you may notice this. For example: .. ipython:: python @@ -379,7 +379,7 @@ slicers on a single axis. dfmi.loc(axis=0)[:, :, ['C1', 'C3']] -Furthermore you can *set* the values using the following methods. +Furthermore, you can *set* the values using the following methods. .. ipython:: python @@ -559,7 +559,7 @@ return a copy of the data rather than a view: .. _advanced.unsorted: -Furthermore if you try to index something that is not fully lexsorted, this can raise: +Furthermore, if you try to index something that is not fully lexsorted, this can raise: .. code-block:: ipython @@ -659,7 +659,7 @@ Index Types We have discussed ``MultiIndex`` in the previous sections pretty extensively. ``DatetimeIndex`` and ``PeriodIndex`` are shown :ref:`here `, and information about -`TimedeltaIndex`` is found :ref:`here `. +``TimedeltaIndex`` is found :ref:`here `. In the following sub-sections we will highlight some other index types. @@ -835,8 +835,8 @@ In non-float indexes, slicing using floats will raise a ``TypeError``. Here is a typical use-case for using this type of indexing. Imagine that you have a somewhat -irregular timedelta-like indexing scheme, but the data is recorded as floats. This could for -example be millisecond offsets. +irregular timedelta-like indexing scheme, but the data is recorded as floats. This could, for +example, be millisecond offsets. .. ipython:: python