From 8d2c1ab496ae52c57c23e6bfc1a1a5e1ee0c07ad Mon Sep 17 00:00:00 2001
From: shichun-0415 <89768198+shichun-0415@users.noreply.github.com>
Date: Wed, 29 Sep 2021 17:30:47 +0800
Subject: [PATCH] tidb: fix default value of performance.committer-concurrency
 (#6498)

---
 tidb-configuration-file.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tidb-configuration-file.md b/tidb-configuration-file.md
index 0654e68bb280f..b658a018f9a94 100644
--- a/tidb-configuration-file.md
+++ b/tidb-configuration-file.md
@@ -502,13 +502,13 @@ The Plan Cache configuration of the `PREPARE` statement.
 
 - The `keepalive` time interval of the RPC connection between TiDB and TiKV nodes. If there is no network packet within the specified time interval, the gRPC client executes `ping` command to TiKV to see if it is alive.
 - Default: `10`
-- unit: second
+- Unit: second
 
 ### `grpc-keepalive-timeout`
 
 - The timeout of the RPC `keepalive` check between TiDB and TiKV nodes.
 - Default value: `3`
-- unit: second
+- Unit: second
 
 ### `commit-timeout`
 
@@ -525,7 +525,7 @@ The Plan Cache configuration of the `PREPARE` statement.
 
 - Waits for `max-batch-wait-time` to encapsulate the data packets into a large packet in batch and send it to the TiKV node. It is valid only when the value of `tikv-client.max-batch-size` is greater than `0`. It is recommended not to modify this value.
 - Default value: `0`
-- unit: nanoseconds
+- Unit: nanoseconds
 
 ### `batch-wait-size`