Skip to content

Commit

Permalink
fix typo mis-spelled as 'custer' (pingcap#12917)
Browse files Browse the repository at this point in the history
  • Loading branch information
bohnen authored Mar 16, 2023
1 parent d67752e commit f78be31
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion migration-tools.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ This document introduces the user scenarios, supported upstreams and downstreams

## [Backup & Restore (BR)](/br/backup-and-restore-overview.md)

| User scenario | <span style="font-weight:normal">Migrate a large amount of TiDB custer data by backing up and restoring data</span> |
| User scenario | <span style="font-weight:normal">Migrate a large amount of TiDB cluster data by backing up and restoring data</span> |
|---|---|
| **Upstream** | TiDB |
| **Downstream (the output file)** | SST, backup.meta files, backup.lock files |
Expand Down
2 changes: 1 addition & 1 deletion tidb-cloud/backup-and-restore.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ By the automatic backup, you can back up the cluster data every day at the backu

Currently, you cannot select an arbitrary remote region for backup data storage. The regions already supported are as follows:

| Cloud provider | Custer region | Remote region support |
| Cloud provider | Cluster region | Remote region support |
|----------------|-----------------------------|--------------------------|
| GCP | Tokyo (asia-northeast1) | Osaka (asia-northeast2) |

Expand Down

0 comments on commit f78be31

Please sign in to comment.