Skip to content

Commit b06c1cd

Browse files
committed
Improve docs
1 parent 75a346b commit b06c1cd

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/command-line-flags.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ You may want to use this on Amazon RDS.
4747

4848
### attempt-instant-ddl
4949

50-
MySQL 8.0 support "instant DDL" for some operations. If an alter statement can be completed with instant DDL, only a metadata change is required internally, so MySQL will return _instantly_ (only requiring a metadata lock to complete). Instant operations include:
50+
MySQL 8.0 supports "instant DDL" for some operations. If an alter statement can be completed with instant DDL, only a metadata change is required internally. Instant operations include:
5151

5252
- Adding a column
5353
- Dropping a column
@@ -57,9 +57,9 @@ MySQL 8.0 support "instant DDL" for some operations. If an alter statement can b
5757

5858
It is not reliable to parse the `ALTER` statement to determine if it is instant or not. This is because the table might be in an older row format, or have some other incompatibility that is difficult to identify.
5959

60-
The risks of attempting to instant DDL are relatively minor: Gh-ost may need to acquire a metadata lock at the start of the operation. This is not a problem for most scenarios, but it could be a problem for users that start the DDL during a period with long running transactions.
60+
The risks of attempting instant DDL are relatively minor: `gh-ost` may need to acquire a metadata lock at the start of the operation. This is not a problem for most scenarios, but it could be a problem for users that start the DDL during a period with long running transactions.
6161

62-
gh-ost will automatically fallback to the normal DDL process if the attempt to use instant DDL is unsuccessful.
62+
`gh-ost` will automatically fallback to the normal DDL process if the attempt to use instant DDL is unsuccessful.
6363

6464
### conf
6565

0 commit comments

Comments
 (0)