Create an informative issue (See each section, incomplete templates/issues won't be triaged)

Using the current documentation as a model, please complete the issue template. 

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have

Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

 - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

 - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

Describe the changes in the doc and link to your dev story

Provide info for the following steps:

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

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

      - [ ] New topic in an existing section or new section
      - [ x] Update to an existing topic

3. - [ ] Mandatory for GA content:
            
       - [ ] Add steps and/or other important conceptual information here: 
       
            
       - [ ] Add Required access level for the user to complete the task here:
       

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

4. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:

Related to this dicussion https://redhat-internal.slack.com/archives/C0282HW2YHZ/p1701700088243429?thread_ts=1701661035.214189&cid=C0282HW2YHZ

Changes:

Update this section

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.8/html/business_continuity/business-cont-overview#resources-restored-managed-cluster-activation

Just above the paragraph starting with : Aside from the activation data resources that are identified by using the

Add the following
Note:
Secrets and config maps are always restored when passive resources are restore, regardless of the 

cluster.open-cluster-management.io/backup label value.  The cluster-activation value is ignored for these type of resources. You should set the cluster.open-cluster-management.io/backup: cluster-activation value to the resources using these secrets instead, so they are not restored until the activation step.