Please review current docs that support and customers use for information about the release.

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

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

• [X] We need to update to an existing topic

3. - [X] *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:

Review known issues to see what can be removed:

https://github.com/stolostron/rhacm-docs/blob/2.14_stage/release_notes/acm_known_issues_intro.adoc#known-issues-acm (ACM)

https://github.com/stolostron/rhacm-docs/blob/2.14_stage/clusters/release_notes/mce_known_issues.adoc#known-issues-mce (MCE)

Review the Deprecations table to see what needs to be in _removed _status, what can be removed from the doc:

https://github.com/stolostron/rhacm-docs/blob/2.14_stage/release_notes/acm_deprecate_remove.adoc#deprecations-removals-acm (ACM)

https://github.com/stolostron/rhacm-docs/blob/2.14_stage/clusters/release_notes/mce_deprecate_remove.adoc#deprecations-removals-cluster-mce (MCE)

Review Troubleshooting files for what has been fixed and needs to be removed:

https://github.com/stolostron/rhacm-docs/blob/2.14_stage/troubleshooting/troubleshooting_intro.adoc (ACM)

https://github.com/stolostron/rhacm-docs/blob/2.14_stage/clusters/support_troubleshooting/troubleshooting_mce_intro.adoc (MCE)

Important: You have the option to reach out to your writer to handle the removal or to send a PR if the removal is simple. If many things need to change, it may be better to let the doc team create the PR to avoid build issues. PRs for simple changes are welcomed.