Create an informative issue (See each section, incomplete templates/issues won't be triaged)
Using the current documentation as a model, please complete the issue template.

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have
Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 3:

• Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.5

• Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs

Describe the changes in the doc and link to your dev story
Provide info for the following steps:

1. - [X] Mandatory Choose the documentation release (Published releases are refreshed ~weekly after publication).

• [ ] ACM 2.4
• [ ] ACM 2.5
• [ ] ACM 2.6
• [ ]ACM 2.7 (upcoming release)

• [ ] MCE 2.0
• [ ] MCE 2.1
• [ ] MCE 2.2 (upcoming release)

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

• [ ] New topic in an existing section or new section
• [X] Update to an existing topic

3. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:

4. - [ ] Mandatory for GA content:

Create docs errata for ACM 2.5.7

• [ ] Add steps and/or other important conceptual information here:

• [ ] Add Required access level for the user to complete the task here:

• [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)

• [ ] Add link to dev story here:

• Errata release note version, this is NOT for regular refreshes:
  (published with Errata release)

• [ ] ACM 2.4.x
• [ ] ACM 2.5.x
• [ ] ACM 2.6.x
• [] ACM 2.7.x
•  

• [ ] MCE 2.0.x

• [ ] MCE 2.1.x
• [ X] MCE 2.2.x
•