Apply suggestions from code review

Co-authored-by: BornChanger <[email protected]>

en/releases/release-1.5.2.md

@@ -10,13 +10,15 @@ TiDB Operator version: 1.5.2
 
 ## New features
 
+Starting from v1.5.2, TiDB Operator supports backing up and restoring the data of a TiDB cluster deployed across multiple AWS Kubernetes clusters to AWS storage using EBS volume snapshots. For more information, refer to [Back up Data Using EBS Snapshots across Multiple Kubernetes](backup-by-ebs-snapshot-across-multiple-kubernetes.md) and [Restore Data Using EBS Snapshots across Multiple Kubernetes](restore-from-ebs-snapshot-across-multiple-kubernetes.md). ([#5003](https://github.com/pingcap/tidb-operator/pull/5003), [@BornChanger](https://github.com/BornChanger), [@WangLe1321](https://github.com/WangLe1321), [@YuJuncen](https://github.com/YuJuncen), [@csuzhangxc](https://github.com/csuzhangxc))
+
 ## Improvements
 
 - `startScriptVersion: v2` supports waiting for Pod IP to match the one published to external DNS before starting a PD or TiKV to better support scenarios such as Stale Read ([#5381](https://github.com/pingcap/tidb-operator/pull/5381), [@smineyev81](https://github.com/smineyev81))
 - `startScriptVersion: v2` supports explicitly specifying PD addresses to better support scenarios where a TiDB cluster is deployed across Kubernetes ([#5400](https://github.com/pingcap/tidb-operator/pull/5400), [@smineyev81](https://github.com/smineyev81))
-- tidb-operator Helm Chart supports specify resource lock for leader election when deploying Advanced-StatefulSet ([#5448](https://github.com/pingcap/tidb-operator/pull/5448), [@csuzhangxc](https://github.com/csuzhangxc))
+- tidb-operator Helm Chart supports specifying resource lock for leader election when deploying Advanced StatefulSet ([#5448](https://github.com/pingcap/tidb-operator/pull/5448), [@csuzhangxc](https://github.com/csuzhangxc))
 
 ## Bug fixes
 
-- Fix the issue that changing meta information such as annotations and replacing volumes at the same time may cause a deadlock for TiDB Operator reconcile ([#5382](https://github.com/pingcap/tidb-operator/pull/5382), [@anish-db](https://github.com/anish-db))
-- Fix the issue that the PD member might be set the wrong label when replacing volumes ([#5393](https://github.com/pingcap/tidb-operator/pull/5393), [@anish-db](https://github.com/anish-db))
+- Fix the issue that changing meta information such as annotations and replacing volumes at the same time might cause a deadlock for TiDB Operator reconcile ([#5382](https://github.com/pingcap/tidb-operator/pull/5382), [@anish-db](https://github.com/anish-db))
+- Fix the issue that the PD member might be set to the wrong label when replacing volumes ([#5393](https://github.com/pingcap/tidb-operator/pull/5393), [@anish-db](https://github.com/anish-db))

zh/releases/release-1.5.2.md

@@ -10,6 +10,8 @@ TiDB Operator 版本：1.5.2
 
 ## 新功能
 
+从 v1.5.2 起, TiDB operator 支持基于 AWS EBS 快照的备份能力的跨多个 K8S 集群的备份恢复。更多详情，请查看文档 [Back up Data Using EBS Snapshots across Multiple Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/stable/backup-by-ebs-snapshot-across-multiple-kubernetes) 和 [Restore Data Using EBS Snapshots across Multiple Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/stable/restore-from-ebs-snapshot-across-multiple-kubernetes)。([#5003](https://github.com/pingcap/tidb-operator/pull/5003), [@BornChanger](https://github.com/BornChanger), [@WangLe1321](https://github.com/WangLe1321), [@YuJuncen](https://github.com/YuJuncen), [@csuzhangxc](https://github.com/csuzhangxc))
+
 ## 优化提升
 
 - `startScriptVersion: v2` 支持在重启 PD、TiKV 时等待 Pod IP 与 DNS 解析一致后再进行启动以更好地支持 Stale Read 等场景 ([#5381](https://github.com/pingcap/tidb-operator/pull/5381), [@smineyev81](https://github.com/smineyev81))