@@ -21,7 +21,7 @@ See the :ref:`Indexing and Selecting Data <indexing>` for general indexing docum
21
21
22
22
.. warning ::
23
23
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
25
25
depend on the context. This is sometimes called ``chained assignment `` and
26
26
should be avoided. See :ref: `Returning a View versus Copy
27
27
<indexing.view_versus_copy>`.
@@ -172,7 +172,7 @@ Defined Levels
172
172
~~~~~~~~~~~~~~
173
173
174
174
The 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.
176
176
For example:
177
177
178
178
.. ipython :: python
@@ -379,7 +379,7 @@ slicers on a single axis.
379
379
380
380
dfmi.loc(axis = 0 )[:, :, [' C1' , ' C3' ]]
381
381
382
- Furthermore you can *set * the values using the following methods.
382
+ Furthermore, you can *set * the values using the following methods.
383
383
384
384
.. ipython :: python
385
385
@@ -559,7 +559,7 @@ return a copy of the data rather than a view:
559
559
560
560
.. _advanced.unsorted :
561
561
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:
563
563
564
564
.. code-block :: ipython
565
565
@@ -659,7 +659,7 @@ Index Types
659
659
660
660
We have discussed ``MultiIndex `` in the previous sections pretty extensively. ``DatetimeIndex `` and ``PeriodIndex ``
661
661
are shown :ref: `here <timeseries.overview >`, and information about
662
- `TimedeltaIndex`` is found :ref: `here <timedeltas.timedeltas >`.
662
+ `` TimedeltaIndex `` is found :ref: `here <timedeltas.timedeltas >`.
663
663
664
664
In the following sub-sections we will highlight some other index types.
665
665
@@ -835,8 +835,8 @@ In non-float indexes, slicing using floats will raise a ``TypeError``.
835
835
836
836
837
837
Here 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.
840
840
841
841
.. ipython:: python
842
842
0 commit comments