Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: typo fixes in MultiIndex / Advanced Indexing #22179

Merged
merged 1 commit into from
Aug 2, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions doc/source/advanced.rst
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ See the :ref:`Indexing and Selecting Data <indexing>` 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
<indexing.view_versus_copy>`.
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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

Expand Down Expand Up @@ -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

Expand Down Expand Up @@ -659,7 +659,7 @@ Index Types

We have discussed ``MultiIndex`` in the previous sections pretty extensively. ``DatetimeIndex`` and ``PeriodIndex``
are shown :ref:`here <timeseries.overview>`, and information about
`TimedeltaIndex`` is found :ref:`here <timedeltas.timedeltas>`.
``TimedeltaIndex`` is found :ref:`here <timedeltas.timedeltas>`.

In the following sub-sections we will highlight some other index types.

Expand Down Expand Up @@ -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

Expand Down