Skip to content

Commit b403b8b

Browse files
Amanda WestlakeAmanda Westlake
authored andcommitted
Make changes to documentation to improve headings
1 parent 2b2f7e6 commit b403b8b

3 files changed

Lines changed: 4 additions & 4 deletions

File tree

content/en/docs/24.0/user-guides/configuration-basic/global-topo.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,11 +38,11 @@ To be safe, you may want to bring up etcd with `--enable-v2=true`, even though i
3838

3939
It is generally not recommended that you migrate from one type of toposerver to another. However, if absolutely necessary, you can use the [topo2topo](../../../reference/features/topology-service/#migration-between-implementations) command line tool to perform this migration.
4040

41-
## Backups
41+
## Backing up TopoServer data
4242

4343
It is important to periodically backup the data in the TopoServer. Although most of the information in the TopoServer can be manually reconstructed, it is still a painful task. This can be avoided if a recent backup was readily available.
4444

45-
## Checklist
45+
## Verifying TopoServer deployment
4646

4747
* Ensure toposerver is up, and that you can set and get values using their provided client tools.
4848
* Ensure you have the mechanism to include the correct topo flags for all the components: `--topo-implementation`, `--topo-global-server-address` and `--topo-global-root`.

content/en/docs/24.0/user-guides/schema-changes/advanced-usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Listed below are recipes for advanced online DDL usage:
1010
- [Duplicate migration indication](#duplicate-migration-indication)
1111
- [Near instant REVERTs](#near-instant-reverts)
1212

13-
## Duplicate migration detection
13+
## Detecting duplicate migration
1414

1515
Two migrations sharing the same context and DDL are considered duplicate, and only one will run to completion.
1616

content/en/docs/24.0/user-guides/schema-changes/declarative-migrations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Altering tables in declarative DDL is done by issuing `CREATE TABLE` statements
1818

1919
Declarative DDLs have the property of being idempotent. For example, a user may submit the same `CREATE TABLE` statement _twice_, one after another. If the 1st is successful, then the 2nd is a noop, and considered as implicitly successful. Likewise, two `DROP TABLE` DDLs for same statement will each ensure the table does not exist. If the 1st is successful, then the 2nd has nothing to do and is implicitly successful.
2020

21-
## Usage
21+
## Using declarative migrations
2222

2323
Add `--declarative` to any of the online DDL strategies. Example:
2424

0 commit comments

Comments
 (0)