Value Statement

• Documentation that is no longer relevant clutters the doc, conflicts with feature changes, and confuses users.
• Keeping this current increases SEO, UX, conciseness, and accuracy.
• This is not for new documentation. This is an audit of existing documentation.

Procedure

Step 1: ACM/MCE dev teams please review the Known issues for outdated entries.
Step 2: Comment in your issue and tag your writer, OR send a PR and tag your writer if something needs to be removed or updated.
Step 3: Review the Deprecations table. If something has been removed, tag your writer in the comments so they can move it to the Removals table. You can also create a PR.
Step 4: Review the Troubleshooting topics for outdated entries.
Step 5: Comment in your issue and tag your writer, OR send a PR and tag your writer if something needs to be removed or updated.
Step 6: Place your Jira ticket in Review and the writer will close when all updates are made.

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

MCE Deprecations
https://github.com/stolostron/rhacm-docs/blob/2.15_stage/clusters/release_notes/mce_deprecate_remove.adoc

ACM Known issues
https://github.com/stolostron/rhacm-docs/blob/2.15_stage/release_notes/acm_known_issues_intro.adoc

MCE Known issues
https://github.com/stolostron/rhacm-docs/blob/2.15_stage/clusters/release_notes/mce_known_issues.adoc

ACM Troubleshooting

https://github.com/stolostron/rhacm-docs/blob/2.15_stage/troubleshooting/troubleshooting_intro.adoc

MCE Troubleshooting

https://github.com/stolostron/rhacm-docs/blob/2.15_stage/clusters/support_troubleshooting/troubleshooting_mce_intro.adoc