@@ -21,7 +21,7 @@ See the :ref:`Indexing and Selecting Data <indexing>` for general indexing docum
2121
2222.. warning ::
2323
24- Whether a copy or a reference is returned for a setting operation, may
24+ Whether a copy or a reference is returned for a setting operation may
2525 depend on the context. This is sometimes called ``chained assignment `` and
2626 should be avoided. See :ref: `Returning a View versus Copy
2727 <indexing.view_versus_copy>`.
@@ -172,7 +172,7 @@ Defined Levels
172172~~~~~~~~~~~~~~
173173
174174The repr of a ``MultiIndex `` shows all the defined levels of an index, even
175- if the they are not actually used. When slicing an index, you may notice this.
175+ if they are not actually used. When slicing an index, you may notice this.
176176For example:
177177
178178.. ipython :: python
@@ -379,7 +379,7 @@ slicers on a single axis.
379379
380380 dfmi.loc(axis = 0 )[:, :, [' C1' , ' C3' ]]
381381
382- Furthermore you can *set * the values using the following methods.
382+ Furthermore, you can *set * the values using the following methods.
383383
384384.. ipython :: python
385385
@@ -559,7 +559,7 @@ return a copy of the data rather than a view:
559559
560560 .. _advanced.unsorted :
561561
562- Furthermore if you try to index something that is not fully lexsorted, this can raise:
562+ Furthermore, if you try to index something that is not fully lexsorted, this can raise:
563563
564564.. code-block :: ipython
565565
@@ -659,7 +659,7 @@ Index Types
659659
660660We have discussed ``MultiIndex `` in the previous sections pretty extensively. ``DatetimeIndex `` and ``PeriodIndex ``
661661are shown :ref: `here <timeseries.overview >`, and information about
662- `TimedeltaIndex`` is found :ref: `here <timedeltas.timedeltas >`.
662+ `` TimedeltaIndex `` is found :ref: `here <timedeltas.timedeltas >`.
663663
664664In the following sub-sections we will highlight some other index types.
665665
@@ -835,8 +835,8 @@ In non-float indexes, slicing using floats will raise a ``TypeError``.
835835
836836
837837Here is a typical use- case for using this type of indexing. Imagine that you have a somewhat
838- irregular timedelta- like indexing scheme, but the data is recorded as floats. This could for
839- example be millisecond offsets.
838+ irregular timedelta- like indexing scheme, but the data is recorded as floats. This could, for
839+ example, be millisecond offsets.
840840
841841.. ipython:: python
842842
0 commit comments