@@ -1089,7 +1089,7 @@ Leap second
10891089-----------
10901090
10911091`Leap seconds <https://en.wikipedia.org/wiki/Leap_second >`__ are a periodic
1092- one-second adjustment of Coordinated Universal Time(UTC) in order to keep
1092+ one-second adjustment of Coordinated Universal Time (UTC) in order to keep
10931093a system's time of day close to the mean solar time. However,
10941094the Earth's rotation speed varies in response to climatic and geological events,
10951095and due to this, UTC leap seconds are irregularly spaced and unpredictable.
@@ -1124,18 +1124,18 @@ The ``datetime`` module supports leap seconds at the most basic level:
11241124
11251125 Meanwhile the following cases are NOT supported by the ``datetime `` module:
11261126
1127- * With the :ref: `datetime.new() <datetime-new >` function, the 60 leap seconds in the ``sec `` key
1128- give an extra minute like regular seconds, and the result is represented in a regular manner,
1129- without leap seconds:
1127+ * With the :ref: `datetime.new() <datetime-new >` function, the 60 leap seconds in the ``sec `` key
1128+ give an extra minute like regular seconds, and the result is represented in a regular manner,
1129+ without leap seconds:
11301130
11311131 .. code-block :: tarantoolsession
11321132
11331133 datetime.new({ year = 1998, month = 12, day = 31, hour = 23, min = 59, sec = 60})
11341134 ---
11351135 - 1999-01-01T00:00:00Z
11361136
1137- * The function :ref: `datetime.parse() <datetime-parse >` produces an error when parsing a leap second
1138- input string with 60 seconds and a format that supports leap seconds ('rfc3339', 'iso8601'):
1137+ * The function :ref: `datetime.parse() <datetime-parse >` produces an error when parsing a leap second
1138+ input string with 60 seconds and a format that supports leap seconds ('rfc3339', 'iso8601'):
11391139
11401140 .. code-block :: tarantoolsession
11411141
0 commit comments