Preview PR pingcap/docs-tidb-operator#2406 and this preview is trigge…

…red from commit pingcap/docs-tidb-operator@6c78a9f

markdown-pages/en/tidb-in-kubernetes/master/en/backup-by-ebs-snapshot-across-multiple-kubernetes.md

@@ -225,14 +225,14 @@ status:
 
 ### Delete the `VolumeBackup` CR
 
-You can delete the `VolumeBackup` CR by running the following commands:
+If you set `spec.template.cleanPolicy` to `Delete`, when you delete the `VolumeBackup` CR, the BR Federation Manager will clean up the backup file and the volume snapshots on AWS.
+
+To delete the `VolumeBackup` CR, run the following commands:
 
 ```shell
 kubectl delete backup ${backup-name} -n ${namespace}
 ```
 
-If you set `spec.template.cleanPolicy` to `Delete`, when you delete the CR, the BR Federation Manager will clean up the backup file and the volume snapshots on AWS.
-
 ## Scheduled volume backup
 
 To ensure regular backups of the TiDB cluster and prevent an excessive number of backup items, you can set a backup policy and retention policy.

markdown-pages/en/tidb-in-kubernetes/master/en/restore-by-ebs-snapshot-across-multiple-kubernetes.md

@@ -50,7 +50,7 @@ Before restoring a TiDB cluster across multiple Kubernetes from EBS volume snaps
 
 1. Download the [backup-rbac.yaml](https://github.com/pingcap/tidb-operator/blob/master/manifests/backup/backup-rbac.yaml) file to the restore server.
 
-2. Supposed that you deploy the TiDB cluster in `${namespace}`, create the RBAC-related resources required for the restore in this namespace by running the following command.
+2. Create the RBAC-related resources required for the restore by running the following command. Note that the RBAC-related resources must be put in the same `${namespace}` as the TiDB cluster. 
 
     ```shell
     kubectl apply -f backup-rbac.yaml -n ${namespace}