This article oddly includes "depreciation", but (anecdotally) I've never heard of this being confused with "deprecation".
I think, instead, they should have included "obsoletion", which I think is what is more often confused/overlooked in favor of using "deprecated" to mean something that has already been obsoleted.
That is, "deprecated" is often incorrectly used as a synonym for "obsoleted".
"This article oddly includes "depreciation", but (anecdotally) I've never heard of this being confused with "deprecation"."
Then you may be in for an instance of the Baader-Meinhof Phenomenon [1] now. It's very widespread. Sometimes it feels like I see "depreciation" more than "deprecation". I've even heard people say out loud "depreciation" several times.
Ideally, when an element is deprecated, the deprecation notice provides clues toward replacements for the unfortunate user bitten by the deprecation. Too many API's drop capabilities without a hint of what downstream developers should do to preserve application behavior.
I think, instead, they should have included "obsoletion", which I think is what is more often confused/overlooked in favor of using "deprecated" to mean something that has already been obsoleted.
That is, "deprecated" is often incorrectly used as a synonym for "obsoleted".