From 28c3ae5c3ee51ed5867b2cdd76cbfd5a98eba3d9 Mon Sep 17 00:00:00 2001
From: joey-yez <104608045+joey-yez@users.noreply.github.com>
Date: Mon, 25 Dec 2023 18:39:57 +0800
Subject: [PATCH] Update tiflash/use-tidb-to-read-tiflash.md

---
 tiflash/use-tidb-to-read-tiflash.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tiflash/use-tidb-to-read-tiflash.md b/tiflash/use-tidb-to-read-tiflash.md
index 9bcc1440683b4..6532bd9fbaf4c 100644
--- a/tiflash/use-tidb-to-read-tiflash.md
+++ b/tiflash/use-tidb-to-read-tiflash.md
@@ -144,6 +144,6 @@ In the above three ways of reading TiFlash replicas, engine isolation specifies
 > **Note:**
 >
 > - Before v4.0.3, the behavior of reading from TiFlash replica in a non-read-only SQL statement (for example, `INSERT INTO ... SELECT`, `SELECT ... FOR UPDATE`, `UPDATE ...`, `DELETE ...`) is undefined.
-> - In versions between v4.0.3 and v6.3.0, internally TiDB ignores the TiFlash replica for a non-read-only SQL statement to guarantee the data correctness. That is, for [smart selection](#smart-selection), TiDB automatically selects the non-TiFlash replica; for [engine isolation](#engine-isolation) that specifies TiFlash replica **only**, TiDB reports an error; and for [manual hint](#manual-hint), TiDB ignores the hint.
+> - In versions between v4.0.3 and v6.2.0, internally TiDB ignores the TiFlash replica for a non-read-only SQL statement to guarantee the data correctness. That is, for [smart selection](#smart-selection), TiDB automatically selects the non-TiFlash replica; for [engine isolation](#engine-isolation) that specifies TiFlash replica **only**, TiDB reports an error; and for [manual hint](#manual-hint), TiDB ignores the hint.
 > - In versions between v6.4.0 and v7.0.0, if the TiFlash replica is enabled, you can use the variable [tidb_enable_tiflash_read_for_write_stmt](/system-variables.md#tidb_enable_tiflash_read_for_write_stmt-new-in-v630) to decide whether to use the TiFlash replica for a non-read-only SQL statement.
 > - In v7.1.0 and later versions, if the TiFlash replica is enabled and the [SQL Mode](/sql-mode.md) of the current session is not STRICT Mode(the variable `sql_mode` does not include `STRICT_TRANS_TABLES` or `STRICT_ALL_TABLES`), TiDB will decide automatically whether to use the TiFlash replica based on cost estimation for a non-read-only SQL statement.