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: *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:

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

Update https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/business_continuity/business-cont-overview#more-restore-samples

Change :

Just after the last item ( Restore the resources for managed clusters only, using the acm-managed-clusters-schedule-20210902205438 backup: )

Add this new items in the list :

• Use the advanced filtering options available with velero restore to filter out resources to be restored. 
  The sample below shows how to restore only resources from the vb-managed-cls-2 managed cluster namespace and exclude any global ManagedCluster resource. 

You can set the following velero restore spec options when creating the ACM restore resource:

• • includedResources
  • includedNamespaces
  • excludedResources
  • excludedNamespaces
  • LabelSelector
  • OrLabelSelector 
    (just add this sample here , take out the comments from line 1-4 ) https://github.com/stolostron/cluster-backup-operator/blob/main/config/samples/usecases/move-clusters/move-managed-clusters-step1.yaml
    Note: If you set any velero restore filters from the list above, use the `cleanupBeforeRestore` set to `None` to avoid cleaning up hub resources which are part of the restored backup but are not being restored because of the applied filter.