Skip to content

Commit ea74c00

Browse files
committed
Merge pull request pandas-dev#10071 from mortada/doc_typos
DOC/CLN: fixed typos in timeseries.rst
2 parents 2e087c7 + a88d5f5 commit ea74c00

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

doc/source/timeseries.rst

+16-16
Original file line numberDiff line numberDiff line change
@@ -243,7 +243,7 @@ variety of frequency aliases. The default frequency for ``date_range`` is a
243243
rng = bdate_range(start, end)
244244
rng
245245
246-
``date_range`` and ``bdate_range`` makes it easy to generate a range of dates
246+
``date_range`` and ``bdate_range`` make it easy to generate a range of dates
247247
using various combinations of parameters like ``start``, ``end``,
248248
``periods``, and ``freq``:
249249

@@ -353,7 +353,7 @@ This specifies an **exact** stop time (and is not the same as the above)
353353
354354
dft['2013-1':'2013-2-28 00:00:00']
355355
356-
We are stopping on the included end-point as its part of the index
356+
We are stopping on the included end-point as it is part of the index
357357

358358
.. ipython:: python
359359
@@ -541,7 +541,7 @@ The ``rollforward`` and ``rollback`` methods do exactly what you would expect:
541541
It's definitely worth exploring the ``pandas.tseries.offsets`` module and the
542542
various docstrings for the classes.
543543

544-
These operations (``apply``, ``rollforward`` and ``rollback``) preserves time (hour, minute, etc) information by default. To reset time, use ``normalize=True`` keyword when create offset instance. If ``normalize=True``, result is normalized after the function is applied.
544+
These operations (``apply``, ``rollforward`` and ``rollback``) preserves time (hour, minute, etc) information by default. To reset time, use ``normalize=True`` keyword when creating the offset instance. If ``normalize=True``, result is normalized after the function is applied.
545545

546546

547547
.. ipython:: python
@@ -564,7 +564,7 @@ Parametric offsets
564564
~~~~~~~~~~~~~~~~~~
565565

566566
Some of the offsets can be "parameterized" when created to result in different
567-
behavior. For example, the ``Week`` offset for generating weekly data accepts a
567+
behaviors. For example, the ``Week`` offset for generating weekly data accepts a
568568
``weekday`` parameter which results in the generated dates always lying on a
569569
particular day of the week:
570570

@@ -904,7 +904,7 @@ strongly recommended that you switch to using the new offset aliases.
904904
"ms", "L"
905905
"us", "U"
906906

907-
As you can see, legacy quarterly and annual frequencies are business quarter
907+
As you can see, legacy quarterly and annual frequencies are business quarters
908908
and business year ends. Please also note the legacy time rule for milliseconds
909909
``ms`` versus the new offset alias for month start ``MS``. This means that
910910
offset alias parsing is case sensitive.
@@ -1158,8 +1158,8 @@ frequency periods.
11581158
Note that 0.8 marks a watershed in the timeseries functionality in pandas. In
11591159
previous versions, resampling had to be done using a combination of
11601160
``date_range``, ``groupby`` with ``asof``, and then calling an aggregation
1161-
function on the grouped object. This was not nearly convenient or performant as
1162-
the new pandas timeseries API.
1161+
function on the grouped object. This was not nearly as convenient or performant
1162+
as the new pandas timeseries API.
11631163

11641164
.. _timeseries.periods:
11651165

@@ -1197,7 +1197,7 @@ frequency.
11971197
11981198
p - 3
11991199
1200-
If ``Period`` freq is daily or higher (``D``, ``H``, ``T``, ``S``, ``L``, ``U``, ``N``), ``offsets`` and ``timedelta``-like can be added if the result can have same freq. Otherise, ``ValueError`` will be raised.
1200+
If ``Period`` freq is daily or higher (``D``, ``H``, ``T``, ``S``, ``L``, ``U``, ``N``), ``offsets`` and ``timedelta``-like can be added if the result can have the same freq. Otherise, ``ValueError`` will be raised.
12011201

12021202
.. ipython:: python
12031203
@@ -1258,7 +1258,7 @@ objects:
12581258
ps = Series(randn(len(prng)), prng)
12591259
ps
12601260
1261-
``PeriodIndex`` supports addition and subtraction as the same rule as ``Period``.
1261+
``PeriodIndex`` supports addition and subtraction with the same rule as ``Period``.
12621262

12631263
.. ipython:: python
12641264
@@ -1273,7 +1273,7 @@ objects:
12731273
PeriodIndex Partial String Indexing
12741274
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
12751275

1276-
You can pass in dates and strings to `Series` and `DataFrame` with `PeriodIndex`, as the same manner as `DatetimeIndex`. For details, refer to :ref:`DatetimeIndex Partial String Indexing <timeseries.partialindexing>`.
1276+
You can pass in dates and strings to ``Series`` and ``DataFrame`` with ``PeriodIndex``, in the same manner as ``DatetimeIndex``. For details, refer to :ref:`DatetimeIndex Partial String Indexing <timeseries.partialindexing>`.
12771277

12781278
.. ipython:: python
12791279
@@ -1283,7 +1283,7 @@ You can pass in dates and strings to `Series` and `DataFrame` with `PeriodIndex`
12831283
12841284
ps['10/31/2011':'12/31/2011']
12851285
1286-
Passing string represents lower frequency than `PeriodIndex` returns partial sliced data.
1286+
Passing a string representing a lower frequency than ``PeriodIndex`` returns partial sliced data.
12871287

12881288
.. ipython:: python
12891289
@@ -1294,15 +1294,15 @@ Passing string represents lower frequency than `PeriodIndex` returns partial sli
12941294
dfp
12951295
dfp['2013-01-01 10H']
12961296
1297-
As the same as `DatetimeIndex`, the endpoints will be included in the result. Below example slices data starting from 10:00 to 11:59.
1297+
As with ``DatetimeIndex``, the endpoints will be included in the result. The example below slices data starting from 10:00 to 11:59.
12981298

12991299
.. ipython:: python
13001300
13011301
dfp['2013-01-01 10H':'2013-01-01 11H']
13021302
13031303
Frequency Conversion and Resampling with PeriodIndex
13041304
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1305-
The frequency of Periods and PeriodIndex can be converted via the ``asfreq``
1305+
The frequency of ``Period`` and ``PeriodIndex`` can be converted via the ``asfreq``
13061306
method. Let's start with the fiscal year 2011, ending in December:
13071307

13081308
.. ipython:: python
@@ -1345,8 +1345,8 @@ period.
13451345
Period conversions with anchored frequencies are particularly useful for
13461346
working with various quarterly data common to economics, business, and other
13471347
fields. Many organizations define quarters relative to the month in which their
1348-
fiscal year start and ends. Thus, first quarter of 2011 could start in 2010 or
1349-
a few months into 2011. Via anchored frequencies, pandas works all quarterly
1348+
fiscal year starts and ends. Thus, first quarter of 2011 could start in 2010 or
1349+
a few months into 2011. Via anchored frequencies, pandas works for all quarterly
13501350
frequencies ``Q-JAN`` through ``Q-DEC``.
13511351

13521352
``Q-DEC`` define regular calendar quarters:
@@ -1452,7 +1452,7 @@ Time Zone Handling
14521452
------------------
14531453

14541454
Pandas provides rich support for working with timestamps in different time zones using ``pytz`` and ``dateutil`` libraries.
1455-
``dateutil`` support is new [in 0.14.1] and currently only supported for fixed offset and tzfile zones. The default library is ``pytz``.
1455+
``dateutil`` support is new in 0.14.1 and currently only supported for fixed offset and tzfile zones. The default library is ``pytz``.
14561456
Support for ``dateutil`` is provided for compatibility with other applications e.g. if you use ``dateutil`` in other python packages.
14571457

14581458
Working with Time Zones

0 commit comments

Comments
 (0)