Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit da5c01d

Browse files
authored
Fix heading indentation (#2658)
1 parent 7e9e666 commit da5c01d

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

en/restore-from-aws-s3-using-br.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Before restoring backup data on a S3-compatible storage to TiDB using BR, take t
6565
kubectl create secret generic restore-demo2-tidb-secret --from-literal=password=${password} --namespace=test2
6666
```
6767

68-
## Step 2: Restore the backup data to a TiDB cluster
68+
### Step 2: Restore the backup data to a TiDB cluster
6969

7070
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:
7171

@@ -312,4 +312,4 @@ The detailed steps are as follows:
312312
313313
## Troubleshooting
314314
315-
If you encounter any problem during the restore process, refer to [Common Deployment Failures](deploy-failures.md).
315+
If you encounter any problem during the restore process, refer to [Common Deployment Failures](deploy-failures.md).

en/restore-from-gcs-using-br.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Before restoring backup data on GCS to TiDB using BR, take the following steps t
6262
kubectl create secret generic restore-demo2-tidb-secret --from-literal=user=root --from-literal=password=<password> --namespace=test2
6363
```
6464

65-
## Step 2: Restore the backup data to a TiDB cluster
65+
### Step 2: Restore the backup data to a TiDB cluster
6666

6767
1. Create the `Restore` custom resource (CR) to restore the specified data to your cluster:
6868

zh/restore-from-aws-s3-using-br.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ PITR 全称为 Point-in-time recovery,该功能可以让你在新集群上恢
6464
kubectl create secret generic restore-demo2-tidb-secret --from-literal=password=${password} --namespace=test2
6565
```
6666

67-
## 第 2 步:将指定备份数据恢复到 TiDB 集群
67+
### 第 2 步:将指定备份数据恢复到 TiDB 集群
6868

6969
根据上一步选择的远程存储访问授权方式,你需要使用下面对应的方法将备份数据恢复到 TiDB:
7070

zh/restore-from-gcs-using-br.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ PITR 全称为 Point-in-time recovery,该功能可以让你在新集群上恢
6363
kubectl create secret generic restore-demo2-tidb-secret --from-literal=user=root --from-literal=password=<password> --namespace=test2
6464
```
6565

66-
## 第 2 步:将指定备份数据恢复到 TiDB 集群
66+
### 第 2 步:将指定备份数据恢复到 TiDB 集群
6767

6868
1. 创建 restore custom resource (CR),将指定的备份数据恢复至 TiDB 集群:
6969

0 commit comments

Comments
 (0)