Apply suggestions from code review

command-line-flags-for-tidb-configuration.md

@@ -58,7 +58,7 @@ When you start the TiDB cluster, you can use command-line options or environment
 
 ## `--initialize-sql-file`
 
-- The SQL script to be executed when the TiDB cluster is started for the first time. For details, see [configuration item `initialize-sql-file`](/tidb-configuration-file.md#initialize-sql-file-new-in-v660)
+- The SQL script to be executed when the TiDB cluster is started for the first time. For details, see [configuration item `initialize-sql-file`](/tidb-configuration-file.md#initialize-sql-file-new-in-v651)
 - Default: `""`
 
 ## `-L`

tidb-configuration-file.md

@@ -184,7 +184,7 @@ The TiDB configuration file supports more options than command-line parameters.
 + Default value: `true`
 + When the value is `true`, both `KILL` and `KILL TIDB` statements can terminate queries or connections across instances so you do not need to worry about erroneously terminating queries or connections. When you use a client to connect to any TiDB instance and execute the `KILL` or `KILL TIDB` statement, the statement will be forwarded to the target TiDB instance. If there is a proxy between the client and the TiDB cluster, the `KILL` and `KILL TIDB` statements will also be forwarded to the target TiDB instance for execution. Currently, using the MySQL command line <kbd>ctrl</kbd>+<kbd>c</kbd> to terminate a query or connection in TiDB is not supported when `enable-global-kill` is `true`. For more information on the `KILL` statement, see [KILL](/sql-statements/sql-statement-kill.md).
 
-### `initialize-sql-file` <span class="version-mark">New in v6.6.0</span>
+### `initialize-sql-file` <span class="version-mark">New in v6.5.1</span>
 
 + Specifies the SQL script to be executed when the TiDB cluster is started for the first time.
 + Default value: `""`