BUG: Fixed mistake in release note pandas-dev#47953

KingOfTheShow69 · KingOfTheShow69 · commit 74f171bb73d4 · 2022-10-14T11:51:18.000-07:00
diff --git a/doc/source/whatsnew/v1.5.0.rst b/doc/source/whatsnew/v1.5.0.rst
@@ -993,7 +993,6 @@ Datetimelike
 - Bug in :class:`Timestamp` with an integer or float value and ``unit="Y"`` or ``unit="M"`` giving slightly-wrong results (:issue:`47266`)
 - Bug in :class:`.DatetimeArray` construction when passed another :class:`.DatetimeArray` and ``freq=None`` incorrectly inferring the freq from the given array (:issue:`47296`)
 - Bug in :class:`RelativeDeltaOffset` which caused inconsistent behavior upon multiplying a :class:`DateOffset` (:issue:`47953`)
-- Bug in :meth:`RelativeDeltaOffset._apply` which caused inconsistent behavior upon multiplying a :class:`DateOffset` (:issue:`47953`)
 - Bug in :func:`to_datetime` where ``OutOfBoundsDatetime`` would be thrown even if ``errors=coerce`` if there were more than 50 rows (:issue:`45319`)
 - Bug when adding a :class:`DateOffset` to a :class:`Series` would not add the ``nanoseconds`` field (:issue:`47856`)
 -

Original file line number	Diff line number	Diff line change
`@@ -993,7 +993,6 @@ Datetimelike`
`993`	`993`	- Bug in :class:`Timestamp` with an integer or float value and ``unit="Y"`` or ``unit="M"`` giving slightly-wrong results (:issue:`47266`)
`994`	`994`	- Bug in :class:`.DatetimeArray` construction when passed another :class:`.DatetimeArray` and ``freq=None`` incorrectly inferring the freq from the given array (:issue:`47296`)
`995`	`995`	- Bug in :class:`RelativeDeltaOffset` which caused inconsistent behavior upon multiplying a :class:`DateOffset` (:issue:`47953`)
`996`		-- Bug in :meth:`RelativeDeltaOffset._apply` which caused inconsistent behavior upon multiplying a :class:`DateOffset` (:issue:`47953`)
`997`	`996`	- Bug in :func:`to_datetime` where ``OutOfBoundsDatetime`` would be thrown even if ``errors=coerce`` if there were more than 50 rows (:issue:`45319`)
`998`	`997`	- Bug when adding a :class:`DateOffset` to a :class:`Series` would not add the ``nanoseconds`` field (:issue:`47856`)
`999`	`998`	`-`