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. - [ ] 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. - [ ] Mandatory: Find the link to where the documentation update
should go and add it to the recommended changes. You can either use the
published doc or the staged repo for this step:

Note: As the feature and doc is understood, this recommendation may
change. If this is new documentation, link to the section where you think
it should be placed.

Customer Portal published version

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12

Doc staged repo within the ACM Workspace:
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:

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

Following on a slack discussion where the support team found the doc confusing

https://redhat-internal.slack.com/archives/C02GJ3FU8Q6/p1750436166116219?thread_ts=1750429068.034549&cid=C02GJ3FU8Q6

The doc talks about restoring data back to the initial hub , this is the link

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/business_continuity/business-cont-overview#restoring-data-primary-hub

The take out from this should be :

You can't restore back to the original cluster, because 

1. both hubs compete for the managed clusters so the managed clusters bounce back from the restore hub back to the initial ( this is very important and is not mentioned ) https://redhat-internal.slack.com/archives/C02GJ3FU8Q6/p1750436587731359?thread_ts=1750429068.034549&cid=C02GJ3FU8Q6
2.  if you have user created resources on the initial hub , they don't get synced up https://redhat-internal.slack.com/archives/C02GJ3FU8Q6/p1750439775043259?thread_ts=1750429068.034549&cid=C02GJ3FU8Q6

Update here https://docs.google.com/document/d/1XvDp6815ochfekwNx3a0QdnYL1UXk3kNFGadVKmFI0E/edit?tab=t.0