1. - [ ] Mandatory: Add the required version to the Fix version/s field.

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

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

We already have a backup/restore section for HCPs https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/business_continuity/business-cont-overview#config-hcp-backup but the current document is not clear enough.

There is going to be a new document that provides a recommended cluster topology pattern to manage a fleet of HCPs https://issues.redhat.com/browse/ACM-22623. This task is to document the backup and restore procedures for that recommended topology. 

The existing doc https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/business_continuity/business-cont-overview#config-hcp-backup  should be replaced by:

• https://github.com/stolostron/hypershift-addon-operator/blob/main/docs/discovering_hostedclusters.md#disaster-recovery-scope-and-limitations
• https://github.com/stolostron/hypershift-addon-operator/blob/main/docs/discovering_hostedclusters.md#recovery-process

but I am not sure if this should be under the current location in Business Continuity module or under the ACM-MCE integration module. 

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.