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. - [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

• [ ] We need to add a new document to an existing section

• [ ] We need a whole new section; this is a function not
  documented before and doesn't belong in any current section

• [ ] We need an Operator Advisory review and approval

• [ ] We need a z-Stream (Errata) Advisory and Release note
  for MCE and/or ACM

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:

• Published doc: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10
• Source: https://github.com/stolostron/rhacm-docs
  • We would need to add an entry to What's New: https://github.com/stolostron/rhacm-docs/blob/2.13_stage/release_notes/acm_whats_new.adoc
  • We will need to update the component table as well: https://github.com/stolostron/rhacm-docs/blob/2.13_stage/install/adv_config_install.adoc

4. - [x] Mandatory for GA content:

• [x] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:
  • In ACM 2.13, the edge-manager-preview component will now be deployed through the multiclusterhub-operator. The component can be enabled/disabled based upon the MultiClusterHub CR that is deployed on the cluster. By default, the edge-manager-preview component will be disabled by default and will require for the user to enable it for usage.

• [x] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:
  • Access to the namespace where the MCH components are deployed. To enable/disable the component, the user will need access to update the MultiClusterHub CR instance.

• [x] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)
  • Verify that in the MultiClusterHub CR, the edge-manager-preview component status is shown as available.

• [x] Add link to dev story here: https://issues.redhat.com/browse/ACM-15689

5. - [ ] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.