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
  • https://github.com/stolostron/rhacm-docs/blob/2.12_stage/release_notes/whats_new.adoc
  • https://github.com/stolostron/rhacm-docs/blob/2.12_stage/install/install_disconnected.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.12, when MCH is preparing to install/manage MCE on a cluster, it will look for a catalogsource containing the desired version of MCE that is compatible with the current ACM version. If there are multiple catalogsources available, the MCH operator will select the catalogsource with the highest spec.priority value that is set within the resource instances. By default, the redhat-operators priority is set to -100; therefore, if a custom catalogsource is created without a priority level it will be set to 0 and used as the target catalogsource for MCH.
  • Here is an example of how it would look:

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: redhat-operators
  namespace: openshift-marketplace
spec:
   displayName: Red Hat Operators
   priority: -100
...

• [x] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:
  • The user would require cluster admin privilege or access to creating and managing the catalogsource resources in the cluster environment.

• [x] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)
  • If there are more than catalogsource available with the desired release channel for MCE, the user will be able to verify the status by the logs in the multiclusterhub-operator pod logs.

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

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.