Skip to content

Commit a88d5f5

Browse files
committed
DOC/CLN: fixed typos in timeseries.rst
1 parent 2cb7414 commit a88d5f5

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

doc/source/timeseries.rst

Lines changed: 16 additions & 16 deletions
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
@@ -540,7 +540,7 @@ The ``rollforward`` and ``rollback`` methods do exactly what you would expect:
540540
It's definitely worth exploring the ``pandas.tseries.offsets`` module and the
541541
various docstrings for the classes.
542542

543-
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.
543+
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.
544544

545545

546546
.. ipython:: python
@@ -563,7 +563,7 @@ Parametric offsets
563563
~~~~~~~~~~~~~~~~~~
564564

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

@@ -806,7 +806,7 @@ strongly recommended that you switch to using the new offset aliases.
806806
"ms", "L"
807807
"us", "U"
808808

809-
As you can see, legacy quarterly and annual frequencies are business quarter
809+
As you can see, legacy quarterly and annual frequencies are business quarters
810810
and business year ends. Please also note the legacy time rule for milliseconds
811811
``ms`` versus the new offset alias for month start ``MS``. This means that
812812
offset alias parsing is case sensitive.
@@ -1060,8 +1060,8 @@ frequency periods.
10601060
Note that 0.8 marks a watershed in the timeseries functionality in pandas. In
10611061
previous versions, resampling had to be done using a combination of
10621062
``date_range``, ``groupby`` with ``asof``, and then calling an aggregation
1063-
function on the grouped object. This was not nearly convenient or performant as
1064-
the new pandas timeseries API.
1063+
function on the grouped object. This was not nearly as convenient or performant
1064+
as the new pandas timeseries API.
10651065

10661066
.. _timeseries.periods:
10671067

@@ -1099,7 +1099,7 @@ frequency.
10991099
11001100
p - 3
11011101
1102-
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.
1102+
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.
11031103

11041104
.. ipython:: python
11051105
@@ -1160,7 +1160,7 @@ objects:
11601160
ps = Series(randn(len(prng)), prng)
11611161
ps
11621162
1163-
``PeriodIndex`` supports addition and subtraction as the same rule as ``Period``.
1163+
``PeriodIndex`` supports addition and subtraction with the same rule as ``Period``.
11641164

11651165
.. ipython:: python
11661166
@@ -1175,7 +1175,7 @@ objects:
11751175
PeriodIndex Partial String Indexing
11761176
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11771177

1178-
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>`.
1178+
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>`.
11791179

11801180
.. ipython:: python
11811181
@@ -1185,7 +1185,7 @@ You can pass in dates and strings to `Series` and `DataFrame` with `PeriodIndex`
11851185
11861186
ps['10/31/2011':'12/31/2011']
11871187
1188-
Passing string represents lower frequency than `PeriodIndex` returns partial sliced data.
1188+
Passing a string representing a lower frequency than ``PeriodIndex`` returns partial sliced data.
11891189

11901190
.. ipython:: python
11911191
@@ -1196,15 +1196,15 @@ Passing string represents lower frequency than `PeriodIndex` returns partial sli
11961196
dfp
11971197
dfp['2013-01-01 10H']
11981198
1199-
As the same as `DatetimeIndex`, the endpoints will be included in the result. Below example slices data starting from 10:00 to 11:59.
1199+
As with ``DatetimeIndex``, the endpoints will be included in the result. The example below slices data starting from 10:00 to 11:59.
12001200

12011201
.. ipython:: python
12021202
12031203
dfp['2013-01-01 10H':'2013-01-01 11H']
12041204
12051205
Frequency Conversion and Resampling with PeriodIndex
12061206
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1207-
The frequency of Periods and PeriodIndex can be converted via the ``asfreq``
1207+
The frequency of ``Period`` and ``PeriodIndex`` can be converted via the ``asfreq``
12081208
method. Let's start with the fiscal year 2011, ending in December:
12091209

12101210
.. ipython:: python
@@ -1247,8 +1247,8 @@ period.
12471247
Period conversions with anchored frequencies are particularly useful for
12481248
working with various quarterly data common to economics, business, and other
12491249
fields. Many organizations define quarters relative to the month in which their
1250-
fiscal year start and ends. Thus, first quarter of 2011 could start in 2010 or
1251-
a few months into 2011. Via anchored frequencies, pandas works all quarterly
1250+
fiscal year starts and ends. Thus, first quarter of 2011 could start in 2010 or
1251+
a few months into 2011. Via anchored frequencies, pandas works for all quarterly
12521252
frequencies ``Q-JAN`` through ``Q-DEC``.
12531253

12541254
``Q-DEC`` define regular calendar quarters:
@@ -1354,7 +1354,7 @@ Time Zone Handling
13541354
------------------
13551355

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

13601360
Working with Time Zones

0 commit comments

Comments
 (0)