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. - [ ] Mandatory: Add the required version to the Fix version/s field.
ACM 2.12

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

• [X] We need to update to an existing topic
  1.7.1.2. Import discovered clusters from the console
  1.6.5.1.3. Importing a cluster

• [ ] 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. - [ ] *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

4. - [ ] Mandatory for GA content:

• [ ] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:

A. - 1.7.1.2. Import discovered clusters from the console - New step #5 - Import information for Red Hat OpenShift Service on AWS clusters will be detected and pre-filled by the console.

• To confirm the cluster ID, a user can also use the ROSA CLI to describe the cluster they plan to import. Authenticate with ROSA CLI to authenticate into your OCM account and use the command `rosa describe cluster --cluster=<cluster-name> | grep -o '^ID:.*'` to view your cluster id.

B. 1.6.5.1.3. Importing a cluster. - Add the option `Import from Red Hat OpenShift Cluster Manager`

• Provide the Namespace and Credential name and Cluster ID of the cluster that you are importing.
• To confirm the cluster ID, a user can also use the ROSA CLI to describe the cluster they plan to import. Authenticate with ROSA CLI to authenticate into your OCM account and use the command `rosa describe cluster --cluster=<cluster-name> | grep -o '^ID:.*'` to view your cluster id.

• [ ] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:

• [ ] 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:

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.