Note: Doc team updates the current version of the documentation and the
two previous versions (n-2), but we address *only high-priority, or
customer-reported issues* for -2 releases in support.
Describe the changes in the doc and link to your dev story:

1. - [ ] Mandatory: Add the required version to the Fix version/s field.

2. - [ ] Mandatory: Choose the type of documentation change or review.

• [ ] We need to update to an existing topic

3. - [ ] *Mandatory: *Use the following link to open the doc and find where the
documentation update should go. Note: As the feature and doc is
understood and developed, this placement decision may change:

I reviewed what deprecation APIs mean, as it is in the content that it is for Kubernetes deprecations. Somehow we lost the proper use of that section over the releases.

The proper use is in 2.10: https://github.com/stolostron/rhacm-docs/blob/2.10_stage/clusters/release_notes/deprecate_remove.adoc

For 2.11 and later releases, we need to move anything else out of that section and place in "Deprecations", (I did for 2.13). Comment out the section if the section is empty.

story: https://issues.redhat.com/browse/ACM-16237