edits

Author: paigecalvert

docs/reference/custom-resource-backup.md

@@ -23,9 +23,6 @@ spec:
   - '*'
   excludedNamespaces:
   - some-namespace
-  orLabelSelectors:
-  - matchLabels:
-      app: my-app
   orderedResources:
     pods: mysql/mysql-cluster-replica-0,mysql/mysql-cluster-replica-1
     persistentvolumes: pvc-12345,pvc-67890
@@ -76,10 +73,6 @@ However, not all fields are supported for full backups. The table below lists th
     <td><code>excludedNamespaces</code></td>
     <td>(Optional) Specifies an array of namespaces to exclude from the backup.</td>
   </tr>
-  <tr>
-    <td><code>orLabelSelectors</code></td>
-    <td>(Optional) A list of metav1.LabelSelector to filter with when adding individual objects to the backup. If multiple are provided, they will be joined by the OR operator.</td>
-  </tr>
   <tr>
     <td><code>orderedResources</code></td>
     <td>(Optional) Specifies the order of the resources to collect during the backup process. This is a map that uses a key as the plural resource. Each resource name has the format NAMESPACE/OBJECTNAME. The object names are a comma delimited list. For cluster resources, use OBJECTNAME only.</td>

docs/vendor/embedded-disaster-recovery.mdx

@@ -38,7 +38,7 @@ Embedded Cluster disaster recovery has the following limitations and known issue
 
    [View a larger version of this image](/images/ec-version-command.png)
 
-* Any Helm extensions included in the `extensions` field of the Embedded Cluster Config are _not_ included in backups. Helm extensions are reinstalled as part of the restore process. To include Helm extensions in backups, configure the Velero Backup resource to include the extensions using namespace-based or label-based selection. For more information, see [Configure the Velero Backup Resource](#config-backup-resource) below.
+* Any Helm extensions included in the `extensions` field of the Embedded Cluster Config are _not_ included in backups. Helm extensions are reinstalled as part of the restore process. To include Helm extensions in backups, configure the Velero Backup resource to include the extensions using namespace-based or label-based selection. For more information, see [Configure the Velero Custom Resources](#config-velero-resources) below.
 
 * Users can only restore from the most recent backup.
 
@@ -50,11 +50,11 @@ Embedded Cluster disaster recovery has the following limitations and known issue
 
 This section describes how to configure disaster recovery for Embedded Cluster installations and enable access to the disaster recovery feature on a per-customer basis.
 
-### Configure the Velero Custom Resource {#config-backup-resource}
+### Configure the Velero Custom Resources {#config-velero-resources}
 
 This section describes how to set up Embedded Cluster disaster recovery for your application by configuring Velero Backup and Restore custom resources in a release.
 
-To configure disaster recovery:
+To configure the Velero custom resources for disaster recovery:
 
 1. In a new release containing your application files, add a Velero Backup resource. In the Backup resource, use namespace-based or label-based selection to indicate the application resources that you want to be included in the backup. For more information, see [Backup API Type](https://velero.io/docs/latest/api-types/backup/) in the Velero documentation.