From 8404605a67a25c0b3b928ebaccd6b444bd93f3e3 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Mon, 20 Jan 2025 13:31:02 +0800 Subject: [PATCH] Fix heading indentation (#2658) (#2683) --- en/restore-from-aws-s3-using-br.md | 4 ++-- en/restore-from-gcs-using-br.md | 2 +- zh/restore-from-aws-s3-using-br.md | 2 +- zh/restore-from-gcs-using-br.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/en/restore-from-aws-s3-using-br.md b/en/restore-from-aws-s3-using-br.md index 0c1c31f04..e50170f1e 100644 --- a/en/restore-from-aws-s3-using-br.md +++ b/en/restore-from-aws-s3-using-br.md @@ -64,7 +64,7 @@ Before restoring backup data on a S3-compatible storage to TiDB using BR, take t kubectl create secret generic restore-demo2-tidb-secret --from-literal=password=${password} --namespace=test2 ``` -## Step 2: Restore the backup data to a TiDB cluster +### Step 2: Restore the backup data to a TiDB cluster Depending on which method you choose to grant permissions to the remote storage when preparing the restore environment, you can restore the data by doing one of the following: @@ -311,4 +311,4 @@ The detailed steps are as follows: ## Troubleshooting -If you encounter any problem during the restore process, refer to [Common Deployment Failures](deploy-failures.md). \ No newline at end of file +If you encounter any problem during the restore process, refer to [Common Deployment Failures](deploy-failures.md). diff --git a/en/restore-from-gcs-using-br.md b/en/restore-from-gcs-using-br.md index e524614f9..ef66ba074 100644 --- a/en/restore-from-gcs-using-br.md +++ b/en/restore-from-gcs-using-br.md @@ -62,7 +62,7 @@ Before restoring backup data on GCS to TiDB using BR, take the following steps t kubectl create secret generic restore-demo2-tidb-secret --from-literal=user=root --from-literal=password= --namespace=test2 ``` -## Step 2: Restore the backup data to a TiDB cluster +### Step 2: Restore the backup data to a TiDB cluster 1. Create the `Restore` custom resource (CR) to restore the specified data to your cluster: diff --git a/zh/restore-from-aws-s3-using-br.md b/zh/restore-from-aws-s3-using-br.md index ca2460db7..0a6cf4d95 100644 --- a/zh/restore-from-aws-s3-using-br.md +++ b/zh/restore-from-aws-s3-using-br.md @@ -63,7 +63,7 @@ PITR 全称为 Point-in-time recovery，该功能可以让你在新集群上恢 kubectl create secret generic restore-demo2-tidb-secret --from-literal=password=${password} --namespace=test2 ``` -## 第 2 步：将指定备份数据恢复到 TiDB 集群 +### 第 2 步：将指定备份数据恢复到 TiDB 集群 根据上一步选择的远程存储访问授权方式，你需要使用下面对应的方法将备份数据恢复到 TiDB： diff --git a/zh/restore-from-gcs-using-br.md b/zh/restore-from-gcs-using-br.md index 1057f3eb2..4c81ae364 100644 --- a/zh/restore-from-gcs-using-br.md +++ b/zh/restore-from-gcs-using-br.md @@ -62,7 +62,7 @@ PITR 全称为 Point-in-time recovery，该功能可以让你在新集群上恢 kubectl create secret generic restore-demo2-tidb-secret --from-literal=user=root --from-literal=password= --namespace=test2 ``` -## 第 2 步：将指定备份数据恢复到 TiDB 集群 +### 第 2 步：将指定备份数据恢复到 TiDB 集群 1. 创建 restore custom resource (CR)，将指定的备份数据恢复至 TiDB 集群：