Skip to content

Commit 5226030

Browse files
Add backticks to remaining technical terms in CHANGES.rst
1 parent b3c37ba commit 5226030

1 file changed

Lines changed: 10 additions & 10 deletions

File tree

CHANGES.rst

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ Bug fixes:
103103

104104
Bug fixes:
105105

106-
- Fix to permit TZID forward references to VTIMEZONEs
106+
- Fix to permit TZID forward references to ``VTIMEZONE``s
107107
- Stabelize timezone id lookup, see `Issue 780 <https://github.com/collective/icalendar/issues/780>`_.
108108
109109
6.1.2 (2025-03-19)
@@ -179,7 +179,7 @@ New features:
179179
- Add ``DTSTART``, ``TZOFFSETTO``, and ``TZOFFSETFROM`` to ``TimezoneStandard`` and ``TimezoneDaylight``
180180
- Use ``example`` methods of components without arguments.
181181
- Add ``events``, ``timezones``, and ``todos`` property to ``Calendar`` for nicer access.
182-
- To calculate which timezones are in use and add them to the ``Calendar`` when needed these methods are added: ``get_used_tzids``, ``get_missing_tzids``, and ``add_missing_timezones``.
182+
- To calculate which timezones are in use and add them to the ``Calendar`` when needed these methods are added: ``get_used_tzids``, ``get_missing_tzids``, and ``add_missing_timezones()``.
183183
- Identify the TZID of more timezones from dateutil.
184184
- Identify totally unknown timezones using a UTC offset lookup tree generated in ``icalendar.timezone.equivalent_timezone_ids`` and stored in ``icalendar.timezone.equivalent_timezone_ids``.
185185
- Add ``icalendar.timezone.tzid`` to identify a timezone's TZID.
@@ -710,18 +710,18 @@ New features:
710710

711711
Bug fixes:
712712

713-
- Fix VTIMEZONEs including RDATEs #234. [geier]
713+
- Fix ``VTIMEZONE``s including RDATEs #234. [geier]
714714
715715
716716
3.11.5 (2017-07-03)
717717
-------------------
718718
719719
Bug fixes:
720720
721-
- added an assertion that VTIMEZONE sub-components' DTSTART must be of type
721+
- added an assertion that ``VTIMEZONE`` sub-components' DTSTART must be of type
722722
DATETIME [geier]
723723

724-
- Fix handling of VTIMEZONEs with subcomponents with the same DTSTARTs and
724+
- Fix handling of ``VTIMEZONE``s with subcomponents with the same DTSTARTs and
725725
OFFSETs but which are of different types [geier]
726726
727727
@@ -733,7 +733,7 @@ Bug fixes:
733733
- Don't break on parameter values which contain equal signs, e.g. base64 encoded
734734
binary data [geier]
735735
736-
- Fix handling of VTIMEZONEs with subcomponents with the same DTSTARTs.
736+
- Fix handling of ``VTIMEZONE``s with subcomponents with the same DTSTARTs.
737737
[geier]
738738
739739
@@ -854,7 +854,7 @@ Fixes:
854854
3.9.0 (2015-03-24)
855855
------------------
856856

857-
- Creating timezone objects from VTIMEZONE components.
857+
- Creating timezone objects from ``VTIMEZONE`` components.
858858
[geier]
859859

860860
- Make ``python-dateutil`` a dependency.
@@ -1143,9 +1143,9 @@ Fixes:
11431143

11441144
- Add 'recursive' argument to property_items() to switch recursive listing.
11451145
For example when parsing a text/calendar text including multiple components
1146-
(e.g. a VCALENDAR with 5 VEVENTs), the previous situation required us to look
1147-
over all properties in VEVENTs even if we just want the properties under the
1148-
VCALENDAR component (VERSION, PRODID, CALSCALE, METHOD).
1146+
(e.g. a ``VCALENDAR`` with 5 ``VEVENT``s), the previous situation required us to look
1147+
over all properties in ``VEVENT``s even if we just want the properties under the
1148+
``VCALENDAR`` component (VERSION, PRODID, CALSCALE, METHOD).
11491149
[dmikurube]
11501150

11511151
- All unit tests fixed.

0 commit comments

Comments
 (0)