From ab536391a9ddd31560fea457cef5cbffb2577375 Mon Sep 17 00:00:00 2001
From: qiancai <qqzczy@126.com>
Date: Wed, 5 Nov 2025 08:43:35 +0800
Subject: [PATCH] fix variable format issues

---
 mysql-compatibility.md                       | 2 +-
 sql-statements/sql-statement-add-index.md    | 2 +-
 sql-statements/sql-statement-create-index.md | 2 +-
 sql-statements/sql-statement-create-table.md | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/mysql-compatibility.md b/mysql-compatibility.md
index c3a4ca27ee554..b8f9629b97070 100644
--- a/mysql-compatibility.md
+++ b/mysql-compatibility.md
@@ -49,7 +49,7 @@ You can try out TiDB features on [TiDB Playground](https://play.tidbcloud.com/?u
 
     >**Note:**
     >
-    > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql). TiDB Self-Managed and TiDB Cloud Dedicated support parsing the `FULLTEXT` syntax but do not support using the `FULLTEXT` indexes.
+    > Currently, only {{{ .starter }}} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql). TiDB Self-Managed and TiDB Cloud Dedicated support parsing the `FULLTEXT` syntax but do not support using the `FULLTEXT` indexes.
 
 + `SPATIAL` (also known as `GIS`/`GEOMETRY`) functions, data types and indexes [#6347](https://github.com/pingcap/tidb/issues/6347)
 + Character sets other than `ascii`, `latin1`, `binary`, `utf8`, `utf8mb4`, and `gbk`.
diff --git a/sql-statements/sql-statement-add-index.md b/sql-statements/sql-statement-add-index.md
index b09c0d0a93d42..cec85b275defa 100644
--- a/sql-statements/sql-statement-add-index.md
+++ b/sql-statements/sql-statement-add-index.md
@@ -101,7 +101,7 @@ mysql> EXPLAIN SELECT * FROM t1 WHERE c1 = 3;
 
     >**Note:**
     >
-    > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql).
+    > Currently, only {{{ .starter }}} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql).
 
 * Descending indexes are not supported (similar to MySQL 5.7).
 * Adding the primary key of the `CLUSTERED` type to a table is not supported. For more details about the primary key of the `CLUSTERED` type, refer to [clustered index](/clustered-indexes.md).
diff --git a/sql-statements/sql-statement-create-index.md b/sql-statements/sql-statement-create-index.md
index 4bb62620f16d2..e5a4c832c7937 100644
--- a/sql-statements/sql-statement-create-index.md
+++ b/sql-statements/sql-statement-create-index.md
@@ -389,7 +389,7 @@ The system variables associated with the `CREATE INDEX` statement are `tidb_ddl_
 
     >**Note:**
     >
-    > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql).
+    > Currently, only {{{ .starter }}} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql).
 
 * TiDB accepts index types such as `HASH`, `BTREE` and `RTREE` in syntax for compatibility with MySQL, but ignores them.
 * Descending indexes are not supported (similar to MySQL 5.7).
diff --git a/sql-statements/sql-statement-create-table.md b/sql-statements/sql-statement-create-table.md
index a166fd021df44..6e8e3d355df09 100644
--- a/sql-statements/sql-statement-create-table.md
+++ b/sql-statements/sql-statement-create-table.md
@@ -277,7 +277,7 @@ mysql> DESC t1;
 
     >**Note:**
     >
-    > Currently, only {{{ .starter }} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql).
+    > Currently, only {{{ .starter }}} and {{{ .essential }}} clusters in certain AWS regions support [`FULLTEXT` syntax and indexes](https://docs.pingcap.com/tidbcloud/vector-search-full-text-search-sql).
 
 * Setting a `PRIMARY KEY` or `UNIQUE INDEX` as a [global index](/partitioned-table.md#global-indexes) with the `GLOBAL` index option is a TiDB extension for [partitioned tables](/partitioned-table.md) and is not compatible with MySQL.