pingcap · g1eny0ung · May 27, 2020 · May 27, 2020 · May 27, 2020
diff --git a/best-practices/haproxy-best-practices.md b/best-practices/haproxy-best-practices.md
@@ -113,18 +113,18 @@ haproxy --help
 | `-vv` | Displays the version, build options, libraries versions and usable pollers. |
 | `-d` | Enables debug mode. |
 | `-db` | Disables background mode and multi-process mode. |
-| `-dM [<byte>]` | Forces memory poisoning, which means that each and every memory region allocated with malloc() or pool_alloc2() will be filled with \<byte> before being passed to the caller. |
+| `-dM [<byte>]` | Forces memory poisoning, which means that each and every memory region allocated with malloc() or pool_alloc2() will be filled with `<byte>` before being passed to the caller. |
 | `-V` | Enables verbose mode (disables quiet mode). |
 | `-D` | Starts as a daemon.|
-| `-C <dir>` | Changes to directory \<dir> before loading configuration files. |
+| `-C <dir>` | Changes to directory `<dir>` before loading configuration files. |
 | `-W` | Master-worker mode. |
 | `-q` | Sets "quiet" mode: This disables some messages during the configuration parsing and during startup. |
 | `-c` | Only performs a check of the configuration files and exits before trying to bind. |
-| `-n <limit>` | Limits the per-process connection limit to \<limit>. |
-| `-m <limit>` | Limits the total allocatable memory to \<limit> megabytes across all processes. |
-| `-N <limit>` | Sets the default per-proxy maxconn to \<limit> instead of the builtin default value (usually 2000). |
-| `-L <name>` | Changes the local peer name to \<name>, which defaults to the local hostname. |
-| `-p <file>` | Writes all processes' PIDs into \<file> during startup. |
+| `-n <limit>` | Limits the per-process connection limit to `<limit>`. |
+| `-m <limit>` | Limits the total allocatable memory to `<limit>` megabytes across all processes. |
+| `-N <limit>` | Sets the default per-proxy maxconn to `<limit>` instead of the builtin default value (usually 2000). |
+| `-L <name>` | Changes the local peer name to `<name>`, which defaults to the local hostname. |
+| `-p <file>` | Writes all processes' PIDs into `<file>` during startup. |
 | `-de` | Disables the use of epoll(7). epoll(7) is available only on Linux 2.6 and some custom Linux 2.4 systems. |
 | `-dp` | Disables the use of poll(2). select(2) might be used instead. |
 | `-dS` | Disables the use of splice(2), which is broken on older kernels. |

diff --git a/functions-and-operators/expressions-pushed-down.md b/functions-and-operators/expressions-pushed-down.md
@@ -14,10 +14,10 @@ When TiDB reads data from TiKV, TiDB tries to push down some expressions (includ
 | Expression Type | Operations |
 | :-------------- | :------------------------------------- |
 | [Logical operators](/functions-and-operators/operators.md#logical-operators) | AND (&&), OR (&#124;&#124;), NOT (!) |
-| [Comparison functions and operators](/functions-and-operators/operators.md#comparison-functions-and-operators) | <, <=, =, != (<>), >, >=, [`<=>`](https://v3.1.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_equal-to), [`IN()`](https://v3.1.mysql.com/doc/refman/5.7/en/comparison-operators.html#function_in), IS NULL, LIKE, IS TRUE, IS FALSE, [`COALESCE()`](https://v3.1.mysql.com/doc/refman/5.7/en/comparison-operators.html#function_coalesce) |
+| [Comparison functions and operators](/functions-and-operators/operators.md#comparison-functions-and-operators) | `<`, `<=`, `=`, `!=` (`<>`), `>`, `>=`, [`<=>`](https://v3.1.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_equal-to), [`IN()`](https://v3.1.mysql.com/doc/refman/5.7/en/comparison-operators.html#function_in), IS NULL, LIKE, IS TRUE, IS FALSE, [`COALESCE()`](https://v3.1.mysql.com/doc/refman/5.7/en/comparison-operators.html#function_coalesce) |
 | [Numeric functions and operators](/functions-and-operators/numeric-functions-and-operators.md) | +, -, *, /, [`ABS()`](https://v3.1.mysql.com/doc/refman/5.7/en/mathematical-functions.html#function_abs), [`CEIL()`](https://v3.1.mysql.com/doc/refman/5.7/en/mathematical-functions.html#function_ceil), [`CEILING()`](https://v3.1.mysql.com/doc/refman/5.7/en/mathematical-functions.html#function_ceiling), [`FLOOR()`](https://v3.1.mysql.com/doc/refman/5.7/en/mathematical-functions.html#function_floor) |
 | [Control flow functions](/functions-and-operators/control-flow-functions.md) | [`CASE`](https://v3.1.mysql.com/doc/refman/5.7/en/control-flow-functions.html#operator_case), [`IF()`](https://v3.1.mysql.com/doc/refman/5.7/en/control-flow-functions.html#function_if), [`IFNULL()`](https://v3.1.mysql.com/doc/refman/5.7/en/control-flow-functions.html#function_ifnull) |
-| [JSON functions](/functions-and-operators/json-functions.md) | [JSON_TYPE(json_val)][json_type],<br> [JSON_EXTRACT(json_doc, path[, path] ...)][json_extract],<br> [JSON_UNQUOTE(json_val)][json_unquote],<br> [JSON_OBJECT(key, val[, key, val] ...)][json_object],<br> [JSON_ARRAY([val[, val] ...])][json_array],<br> [JSON_MERGE(json_doc, json_doc[, json_doc] ...)][json_merge],<br> [JSON_SET(json_doc, path, val[, path, val] ...)][json_set],<br> [JSON_INSERT(json_doc, path, val[, path, val] ...)][json_insert],<br> [JSON_REPLACE(json_doc, path, val[, path, val] ...)][json_replace],<br> [JSON_REMOVE(json_doc, path[, path] ...)][json_remove] |
+| [JSON functions](/functions-and-operators/json-functions.md) | [JSON_TYPE(json_val)][json_type],<br/> [JSON_EXTRACT(json_doc, path[, path] ...)][json_extract],<br/> [JSON_UNQUOTE(json_val)][json_unquote],<br/> [JSON_OBJECT(key, val[, key, val] ...)][json_object],<br/> [JSON_ARRAY([val[, val] ...])][json_array],<br/> [JSON_MERGE(json_doc, json_doc[, json_doc] ...)][json_merge],<br/> [JSON_SET(json_doc, path, val[, path, val] ...)][json_set],<br/> [JSON_INSERT(json_doc, path, val[, path, val] ...)][json_insert],<br/> [JSON_REPLACE(json_doc, path, val[, path, val] ...)][json_replace],<br/> [JSON_REMOVE(json_doc, path[, path] ...)][json_remove] |
 | [Date and time functions](/functions-and-operators/date-and-time-functions.md) | [`DATE_FORMAT()`](https://v3.1.mysql.com/doc/refman/5.7/en/date-and-time-functions.html#function_date-format)  |
 
 ## Blacklist specific expressions
@@ -103,14 +103,14 @@ tidb> explain select * from t where a < 2 and a > 2;
 
 | Operator Name | Aliases |
 | :-------- | :---------- |
-| < | lt |
-| > | gt |
-| <= | le |
-| >= | ge |
-| = | eq |
-| != | ne |
-| <> | ne |
-| <=> | nulleq |
+| `<` | lt |
+| `>` | gt |
+| `<=` | le |
+| `>=` | ge |
+| `=` | eq |
+| `!=` | ne |
+| `<>` | ne |
+| `<=>` | nulleq |
 | &#124; | bitor |
 | && | bitand|
 | &#124;&#124; | or |

diff --git a/functions-and-operators/operators.md b/functions-and-operators/operators.md
@@ -29,7 +29,7 @@ This document describes the operators precedence, comparison functions and opera
 | [DIV](https://dev.mysql.com/doc/refman/5.7/en/arithmetic-functions.html#operator_div) | Integer division |
 | [/](https://dev.mysql.com/doc/refman/5.7/en/arithmetic-functions.html#operator_divide) | Division operator |
 | [=](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_equal) | Equal operator |
-| [<=>](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_equal-to) | NULL-safe equal to operator |
+| [`<=>`](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_equal-to) | NULL-safe equal to operator |
 | [>](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_greater-than) | Greater than operator |
 | [>=](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_greater-than-or-equal) | Greater than or equal operator |
 | [IS](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_is) | Test a value against a boolean |
@@ -46,7 +46,7 @@ This document describes the operators precedence, comparison functions and opera
 | [%, MOD](https://dev.mysql.com/doc/refman/5.7/en/arithmetic-functions.html#operator_mod) | Modulo operator |
 | [NOT, !](https://dev.mysql.com/doc/refman/5.7/en/logical-operators.html#operator_not) | Negates value |
 | [NOT BETWEEN ... AND ...](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_not-between) | Check whether a value is not within a range of values |
-| [!=, <>](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_not-equal) | Not equal operator |
+| [!=, `<>`](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_not-equal) | Not equal operator |
 | [NOT LIKE](https://dev.mysql.com/doc/refman/5.7/en/string-comparison-functions.html#operator_not-like) | Negation of simple pattern matching |
 | [NOT REGEXP](https://dev.mysql.com/doc/refman/5.7/en/regexp.html#operator_not-regexp) | Negation of REGEXP |
 | [\|\|, OR](https://dev.mysql.com/doc/refman/5.7/en/logical-operators.html#operator_or) | Logical OR |
@@ -92,7 +92,7 @@ For details, see [Operator Precedence](https://dev.mysql.com/doc/refman/5.7/en/o
 | [BETWEEN ... AND ...](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_between) | Check whether a value is within a range of values |
 | [COALESCE()](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#function_coalesce) | Return the first non-NULL argument |
 | [=](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_equal) | Equal operator |
-| [<=>](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_equal-to) | NULL-safe equal to operator |
+| [`<=>`](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_equal-to) | NULL-safe equal to operator |
 | [>](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_greater-than) | Greater than operator |
 | [>=](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_greater-than-or-equal) | Greater than or equal operator |
 | [GREATEST()](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#function_greatest) | Return the largest argument |
@@ -108,7 +108,7 @@ For details, see [Operator Precedence](https://dev.mysql.com/doc/refman/5.7/en/o
 | [<=](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_less-than-or-equal) | Less than or equal operator |
 | [LIKE](https://dev.mysql.com/doc/refman/5.7/en/string-comparison-functions.html#operator_like) | Simple pattern matching |
 | [NOT BETWEEN ... AND ...](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_not-between) | Check whether a value is not within a range of values |
-| [!=, <>](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_not-equal) | Not equal operator |
+| [!=, `<>`](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#operator_not-equal) | Not equal operator |
 | [NOT IN()](https://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html#function_not-in) | Check whether a value is not within a set of values |
 | [NOT LIKE](https://dev.mysql.com/doc/refman/5.7/en/string-comparison-functions.html#operator_not-like) | Negation of simple pattern matching |
 | [STRCMP()](https://dev.mysql.com/doc/refman/5.7/en/string-comparison-functions.html#function_strcmp) | Compare two strings |

diff --git a/sql-mode.md b/sql-mode.md
@@ -43,7 +43,7 @@ Ensure that you have `SUPER` privilege when setting SQL mode at `GLOBAL` level,
 | `NO_ZERO_IN_DATE` | Strict mode, where dates with a month or day part of `0` are not accepted. If you use the `IGNORE` option, TiDB inserts '0000-00-00' for a similar date. In non-strict mode, this date is accepted but a warning is returned. (full support)
 | `NO_ZERO_DATE` | Does not use '0000-00-00' as a legal date in strict mode. You can still insert a zero date with the `IGNORE` option. In non-strict mode, this date is accepted but a warning is returned. (full support)|
 | `ALLOW_INVALID_DATES` | In this mode, the system does not check the validity of all dates. It only checks the month value ranging from `1` to `12` and the date value ranging from `1` to `31`. The mode only applies to `DATE` and `DATATIME` columns. All `TIMESTAMP` columns need a full validity check. (full support) |
-| `ERROR_FOR_DIVISION_BY_ZERO` | If this mode is enabled, the system returns an error when handling division by `0` in data-change operations (`INSERT` or `UPDATE`). <br> If this mode is not enabled, the system returns a warning and `NULL` is used instead. (full support) |
+| `ERROR_FOR_DIVISION_BY_ZERO` | If this mode is enabled, the system returns an error when handling division by `0` in data-change operations (`INSERT` or `UPDATE`). <br/> If this mode is not enabled, the system returns a warning and `NULL` is used instead. (full support) |
 | `NO_AUTO_CREATE_USER` | Prevents `GRANT` from automatically creating new users, except for the specified password (full support)|
 | `HIGH_NOT_PRECEDENCE` | The precedence of the NOT operator is such that expressions such as `NOT a BETWEEN b AND c` are parsed as `NOT (a BETWEEN b AND c)`. In some older versions of MySQL, this expression is parsed as `(NOT a) BETWEEN b AND c`. (full support) |
 | `NO_ENGINE_SUBSTITUTION` | Prevents the automatic replacement of storage engines if the required storage engine is disabled or not compiled. (syntax support only)|

diff --git a/sql-statements/sql-statement-grant-privileges.md b/sql-statements/sql-statement-grant-privileges.md
@@ -1,11 +1,11 @@
 ---
-title: GRANT <privileges> | TiDB SQL Statement Reference
-summary: An overview of the usage of GRANT <privileges> for the TiDB database.
+title: `GRANT <privileges>` | TiDB SQL Statement Reference
+summary: An overview of the usage of GRANT `<privileges>` for the TiDB database.
 category: reference
 aliases: ['/docs/v3.1/reference/sql/statements/grant-privileges/']
 ---
 
-# GRANT <privileges>
+# `GRANT <privileges>`
 
 This statement allocates privileges to a pre-existing user in TiDB. The privilege system in TiDB follows MySQL, where credentials are assigned based on a database/table pattern.
 
@@ -66,6 +66,6 @@ mysql> SHOW GRANTS FOR 'newuser';
 
 ## See also
 
-* [REVOKE <privileges>](/sql-statements/sql-statement-revoke-privileges.md)
+* [`REVOKE <privileges>`](/sql-statements/sql-statement-revoke-privileges.md)
 * [SHOW GRANTS](/sql-statements/sql-statement-show-grants.md)
 * [Privilege Management](/privilege-management.md)
diff --git a/sql-statements/sql-statement-revoke-privileges.md b/sql-statements/sql-statement-revoke-privileges.md
@@ -1,11 +1,11 @@
 ---
-title: REVOKE <privileges> | TiDB SQL Statement Reference
-summary: An overview of the usage of REVOKE <privileges> for the TiDB database.
+title: `REVOKE <privileges>` | TiDB SQL Statement Reference
+summary: An overview of the usage of `REVOKE <privileges>` for the TiDB database.
 category: reference
 aliases: ['/docs/v3.1/reference/sql/statements/revoke-privileges/']
 ---
 
-# REVOKE <privileges>
+# `REVOKE <privileges>`
 
 This statement removes privileges from an existing user.
 
@@ -81,6 +81,6 @@ This statement is understood to be fully compatible with MySQL. Any compatibilit
 
 ## See also
 
-* [GRANT <privileges>](/sql-statements/sql-statement-grant-privileges.md)
+* [`GRANT <privileges>`](/sql-statements/sql-statement-grant-privileges.md)
 * [SHOW GRANTS](/sql-statements/sql-statement-show-grants.md)
 * [Privilege Management](/privilege-management.md)
diff --git a/sql-statements/sql-statement-set-names.md b/sql-statements/sql-statement-set-names.md
@@ -76,6 +76,6 @@ This statement is understood to be fully compatible with MySQL. Any compatibilit
 
 ## See also
 
-* [SHOW \[GLOBAL|SESSION\] VARIABLES](/sql-statements/sql-statement-show-variables.md)
-* [SET <variable>](/sql-statements/sql-statement-set-variable.md)
+* [`SHOW [GLOBAL|SESSION] VARIABLES`](/sql-statements/sql-statement-show-variables.md)
+* [`SET <variable>`](/sql-statements/sql-statement-set-variable.md)
 * [Character Set Support](/character-set-and-collation.md)
diff --git a/sql-statements/sql-statement-set-transaction.md b/sql-statements/sql-statement-set-transaction.md
@@ -65,5 +65,5 @@ mysql> SHOW SESSION VARIABLES like 'transaction_isolation';
 
 ## See also
 
-* [SET \[GLOBAL|SESSION\] <variable>](/sql-statements/sql-statement-set-variable.md)
+* [`SET [GLOBAL|SESSION] <variable>`](/sql-statements/sql-statement-set-variable.md)
 * [Isolation Levels](/transaction-isolation-levels.md)
diff --git a/sql-statements/sql-statement-set-variable.md b/sql-statements/sql-statement-set-variable.md
@@ -1,11 +1,11 @@
 ---
-title: SET [GLOBAL|SESSION] <variable> | TiDB SQL Statement Reference
-summary: An overview of the usage of SET [GLOBAL|SESSION] <variable> for the TiDB database.
+title: `SET [GLOBAL|SESSION] <variable>` | TiDB SQL Statement Reference
+summary: An overview of the usage of `SET [GLOBAL|SESSION] <variable>` for the TiDB database.
 category: reference
 aliases: ['/docs/v3.1/reference/sql/statements/set-variable/']
 ---
 
-# SET [GLOBAL|SESSION] <variable>
+# `SET [GLOBAL|SESSION] <variable>`
 
 The statement `SET [GLOBAL|SESSION]` modifies one of TiDB's built in variables, of either `SESSION` or `GLOBAL` scope. Note that similar to MySQL, changes to `GLOBAL` variables will not apply to either existing connections, or the local connection. Only new sessions will reflect the changes to the value.
 

diff --git a/sql-statements/sql-statement-show-privileges.md b/sql-statements/sql-statement-show-privileges.md
@@ -65,4 +65,4 @@ This statement is understood to be fully compatible with MySQL. Any compatibilit
 ## See also
 
 * [SHOW GRANTS](/sql-statements/sql-statement-show-grants.md)
-* [GRANT <privileges>](/sql-statements/sql-statement-grant-privileges.md)
+* [`GRANT <privileges>`](/sql-statements/sql-statement-grant-privileges.md)
diff --git a/tidb-lightning/tidb-lightning-checkpoints.md b/tidb-lightning/tidb-lightning-checkpoints.md
@@ -7,7 +7,7 @@ aliases: ['/docs/v3.1/reference/tools/tidb-lightning/checkpoints/']
 
 # TiDB Lightning Checkpoints
 
-Importing a large database usually takes hours or days, and if such long running processes spuriously crashes, it can be very time-wasting to redo the previously completed tasks. To solve this, Lightning uses *checkpoints* to store the import progress, so that `tidb-lightning` continues importing from where it lefts off after restarting.
+It usually takes hours or days to import a large database , and if such long running processes spuriously crashes, it can be very time-wasting to redo the previously completed tasks. To solve this, Lightning uses *checkpoints* to store the import progress, so that `tidb-lightning` continues importing from where it lefts off after restarting.
 
 This document describes how to enable, configure, store, and control *checkpoints*.
 

diff --git a/tidb-lightning/tidb-lightning-tidb-backend.md b/tidb-lightning/tidb-lightning-tidb-backend.md
@@ -100,7 +100,7 @@ on-duplicate = "replace" # or "error" or "ignore"
 TiDB Lightning using the TiDB-backend can completely replace functions of [Loader](/loader-overview.md). The following list shows how to translate Loader configurations into [TiDB Lightning configurations](/tidb-lightning/deploy-tidb-lightning.md#step-4-start-tidb-lightning).
 
 <table>
-<thead><tr><th>Loader</th><th>TiDB Lightning</th></tr></thread>
+<thead><tr><th>Loader</th><th>TiDB Lightning</th></tr></thead>
 <tbody>
 <tr><td>
 

diff --git a/tiflash/maintain-tiflash.md b/tiflash/maintain-tiflash.md
@@ -170,9 +170,9 @@ Take the following steps to handle the data file corruption:
 
 | Log Information | Log Description |
 |---------------|-------------------|
-| [ 23 ] <Information> KVStore: Start to persist [region 47, applied: term 6 index 10] | Data starts to be replicated (the number in the square brackets at the start of the log refers to the thread ID |
-| [ 30 ] <Debug> CoprocessorHandler: grpc::Status DB::CoprocessorHandler::execute() | Handling DAG request, that is, TiFlash starts to handle a Coprocessor request |
-| [ 30 ] <Debug> CoprocessorHandler: grpc::Status DB::CoprocessorHandler::execute() | Handling DAG request done, that is, TiFlash finishes handling a Coprocessor request |
+| [ 23 ] `<Information>` KVStore: Start to persist [region 47, applied: term 6 index 10] | Data starts to be replicated (the number in the square brackets at the start of the log refers to the thread ID |
+| [ 30 ] `<Debug>` CoprocessorHandler: grpc::Status DB::CoprocessorHandler::execute() | Handling DAG request, that is, TiFlash starts to handle a Coprocessor request |
+| [ 30 ] `<Debug>` CoprocessorHandler: grpc::Status DB::CoprocessorHandler::execute() | Handling DAG request done, that is, TiFlash finishes handling a Coprocessor request |
 
 You can find the beginning or the end of a Coprocessor request, and then locate the related logs of the Coprocessor request through the thread ID printed at the start of the log.