From 2fc3a06286638a3c7f4b9990a1abdaf4cf32e3ef Mon Sep 17 00:00:00 2001
From: Yu Chen <74105241+yu285@users.noreply.github.com>
Date: Wed, 4 Dec 2024 09:19:20 +0800
Subject: [PATCH 1/5] docs/optimize the description in 08-delete-data.mdx

---
 docs/zh/14-reference/03-taos-sql/08-delete-data.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/zh/14-reference/03-taos-sql/08-delete-data.mdx b/docs/zh/14-reference/03-taos-sql/08-delete-data.mdx
index 3f9c431338..ea03552795 100644
--- a/docs/zh/14-reference/03-taos-sql/08-delete-data.mdx
+++ b/docs/zh/14-reference/03-taos-sql/08-delete-data.mdx
@@ -6,7 +6,7 @@ title: "删除数据"
 
 删除数据是 TDengine 提供的根据指定时间段删除指定表或超级表中数据记录的功能，方便用户清理由于设备故障等原因产生的异常数据。
 
-**注意**：删除数据并不会立即释放该表所占用的磁盘空间，而是把该表的数据标记为已删除，在查询时这些数据将不会再出现，但释放磁盘空间会延迟到系统自动或用户手动进行数据重整时。
+**注意**：删除数据并不会立即释放该表所占用的磁盘空间，而是把该表的数据标记为已删除，在查询时这些数据将不会再出现，但释放磁盘空间会延迟到系统自动清理（建库参数 keep 生效）或用户手动进行数据重整时（企业版功能 compact）。
 
 **语法：**
 

From 58e1322014c0c7df22dafcdcead559350483dfb4 Mon Sep 17 00:00:00 2001
From: wangjiaming0909 <604227650@qq.com>
Date: Mon, 9 Dec 2024 16:57:12 +0800
Subject: [PATCH 2/5] fix packing build with stringop-overflow

---
 source/libs/parser/src/parUtil.c           | 10 +++++-----
 source/libs/planner/src/planPhysiCreater.c |  5 +++--
 2 files changed, 8 insertions(+), 7 deletions(-)

diff --git a/source/libs/parser/src/parUtil.c b/source/libs/parser/src/parUtil.c
index bfe9513594..6cfbacce5b 100644
--- a/source/libs/parser/src/parUtil.c
+++ b/source/libs/parser/src/parUtil.c
@@ -612,10 +612,10 @@ static int32_t getIntegerFromAuthStr(const char* pStart, char** pNext) {
   return taosStr2Int32(buf, NULL, 10);
 }
 
-static void getStringFromAuthStr(const char* pStart, char* pStr, char** pNext) {
+static void getStringFromAuthStr(const char* pStart, char* pStr, uint32_t dstLen, char** pNext) {
   char* p = strchr(pStart, '*');
   if (NULL == p) {
-    tstrncpy(pStr, pStart, strlen(pStart) + 1);
+    tstrncpy(pStr, pStart, dstLen);
     *pNext = NULL;
   } else {
     strncpy(pStr, pStart, p - pStart);
@@ -628,10 +628,10 @@ static void getStringFromAuthStr(const char* pStart, char* pStr, char** pNext) {
 
 static void stringToUserAuth(const char* pStr, int32_t len, SUserAuthInfo* pUserAuth) {
   char* p = NULL;
-  getStringFromAuthStr(pStr, pUserAuth->user, &p);
+  getStringFromAuthStr(pStr, pUserAuth->user, TSDB_USER_LEN, &p);
   pUserAuth->tbName.acctId = getIntegerFromAuthStr(p, &p);
-  getStringFromAuthStr(p, pUserAuth->tbName.dbname, &p);
-  getStringFromAuthStr(p, pUserAuth->tbName.tname, &p);
+  getStringFromAuthStr(p, pUserAuth->tbName.dbname, TSDB_DB_NAME_LEN, &p);
+  getStringFromAuthStr(p, pUserAuth->tbName.tname, TSDB_TABLE_NAME_LEN, &p);
   if (pUserAuth->tbName.tname[0]) {
     pUserAuth->tbName.type = TSDB_TABLE_NAME_T;
   } else {
diff --git a/source/libs/planner/src/planPhysiCreater.c b/source/libs/planner/src/planPhysiCreater.c
index af232c667d..5d47e73e42 100644
--- a/source/libs/planner/src/planPhysiCreater.c
+++ b/source/libs/planner/src/planPhysiCreater.c
@@ -91,11 +91,12 @@ static int32_t getSlotKey(SNode* pNode, const char* pStmtName, char** ppKey, int
           *pLen = taosHashBinary(*ppKey, strlen(*ppKey));
           return code;
         }
-        *ppKey = taosMemoryCalloc(1, strlen(pVal->literal) + 1 + TSDB_COL_NAME_LEN + 1 + extraBufLen);
+        int32_t literalLen = strlen(pVal->literal);
+        *ppKey = taosMemoryCalloc(1, literalLen + 1 + TSDB_COL_NAME_LEN + 1 + extraBufLen);
         if (!*ppKey) {
           return terrno;
         }
-        TAOS_STRNCAT(*ppKey, pVal->literal, strlen(pVal->literal));
+        TAOS_STRNCAT(*ppKey, pVal->literal, literalLen);
         TAOS_STRNCAT(*ppKey, ".", 2);
         TAOS_STRNCAT(*ppKey, ((SExprNode*)pNode)->aliasName, TSDB_COL_NAME_LEN);
         *pLen = taosHashBinary(*ppKey, strlen(*ppKey));

From 22748f470934ca634a05c3a881140645c9e45e3a Mon Sep 17 00:00:00 2001
From: Shengliang Guan <slguan@taosdata.com>
Date: Tue, 10 Dec 2024 09:10:22 +0800
Subject: [PATCH 3/5] doc: minor changes

---
 docs/en/14-reference/03-taos-sql/03-table.md  |  4 +-
 .../14-reference/03-taos-sql/32-compress.md   | 14 +++----
 docs/zh/08-operation/12-multi.md              | 40 +++++++++----------
 docs/zh/14-reference/03-taos-sql/03-table.md  |  4 +-
 .../14-reference/03-taos-sql/10-function.md   |  8 ++--
 .../14-reference/03-taos-sql/32-compress.md   | 14 +++----
 6 files changed, 42 insertions(+), 42 deletions(-)

diff --git a/docs/en/14-reference/03-taos-sql/03-table.md b/docs/en/14-reference/03-taos-sql/03-table.md
index 3c047eb19e..b7a8bb5b1c 100644
--- a/docs/en/14-reference/03-taos-sql/03-table.md
+++ b/docs/en/14-reference/03-taos-sql/03-table.md
@@ -170,7 +170,7 @@ ALTER TABLE [db_name.]tb_name alter_table_clause
 
 alter_table_clause: {
     alter_table_options
-  | SET tag tag_name = new_tag_value,tag_name2=new_tag2_value...
+  | SET tag tag_name = new_tag_value, tag_name2=new_tag2_value ...
 }
 
 alter_table_options:
@@ -194,7 +194,7 @@ alter_table_option: {
 ### Modify Subtable Tag Value
 
 ```sql
-ALTER TABLE tb_name SET TAG tag_name1=new_tag_value1,tag_name2=new_tag_value2...;
+ALTER TABLE tb_name SET TAG tag_name1=new_tag_value1, tag_name2=new_tag_value2 ...;
 ```
 
 ### Modify Table Lifespan
diff --git a/docs/en/14-reference/03-taos-sql/32-compress.md b/docs/en/14-reference/03-taos-sql/32-compress.md
index 8bb2ae31e3..30b107b632 100644
--- a/docs/en/14-reference/03-taos-sql/32-compress.md
+++ b/docs/en/14-reference/03-taos-sql/32-compress.md
@@ -29,13 +29,13 @@ In this document, it specifically refers to the internal levels of the second-le
 - Default compression algorithms list and applicable range for each data type
 
 | Data Type |Available Encoding Algorithms | Default Encoding Algorithm | Available Compression Algorithms | Default Compression Algorithm | Default Compression Level |
-|:------------------------------------:|:----------------:|:-----------:|:--------------------:|:----:|:------:|
-| int/uint                             | simple8b         | simple8b    | lz4/zlib/zstd/xz     | lz4  | medium |
-| tinyint/untinyint/smallint/usmallint | simple8b         | simple8b    | lz4/zlib/zstd/xz     | zlib | medium |
-| bigint/ubigint/timestamp             | simple8b/delta-i | delta-i     | lz4/zlib/zstd/xz     | lz4  | medium |
-| float/double                         | delta-d          | delta-d     | lz4/zlib/zstd/xz/tsz | lz4  | medium |
-| binary/nchar                         | disabled         | disabled    | lz4/zlib/zstd/xz     | zstd | medium |
-| bool                                 | bit-packing      | bit-packing | lz4/zlib/zstd/xz     | zstd | medium |
+|:------------------------------------:|:-------------------------:|:-----------:|:--------------------:|:----:|:------:|
+| int/uint                             | disabled/simple8b         | simple8b    | lz4/zlib/zstd/xz     | lz4  | medium |
+| tinyint/untinyint/smallint/usmallint | disabled/simple8b         | simple8b    | lz4/zlib/zstd/xz     | zlib | medium |
+| bigint/ubigint/timestamp             | disabled/simple8b/delta-i | delta-i     | lz4/zlib/zstd/xz     | lz4  | medium |
+| float/double                         | disabled/delta-d          | delta-d     | lz4/zlib/zstd/xz/tsz | lz4  | medium |
+| binary/nchar                         | disabled                  | disabled    | lz4/zlib/zstd/xz     | zstd | medium |
+| bool                                 | disabled/bit-packing      | bit-packing | lz4/zlib/zstd/xz     | zstd | medium |
 
 ## SQL Syntax
 
diff --git a/docs/zh/08-operation/12-multi.md b/docs/zh/08-operation/12-multi.md
index 1e81a7ff1e..d18957d7d2 100644
--- a/docs/zh/08-operation/12-multi.md
+++ b/docs/zh/08-operation/12-multi.md
@@ -68,19 +68,19 @@ dataDir /mnt/data6 2 0
 
 在配置文件 /etc/taos/taos.cfg 中，添加用于 S3 访问的参数：
 
-|参数名称        |   参数含义                                      |
-|:-------------|:-----------------------------------------------|
-|s3EndPoint | 用户所在地域的 COS 服务域名，支持 http 和 https，bucket 的区域需要与 endpoint 的保持一致，否则无法访问。 |
-|s3AccessKey |冒号分隔的用户 SecretId:SecretKey。例如：AKIDsQmwsfKxTo2A6nGVXZN0UlofKn6JRRSJ:lIdoy99ygEacU7iHfogaN2Xq0yumSm1E |
-|s3BucketName | 存储桶名称，减号后面是用户注册 COS 服务的 AppId。其中 AppId 是 COS 特有，AWS 和阿里云都没有，配置时需要作为 bucket name 的一部分，使用减号分隔。参数值均为字符串类型，但不需要引号。例如：test0711-1309024725 |
-|s3UploadDelaySec | data 文件持续多长时间不再变动后上传至 s3，单位：秒。最小值：1；最大值：2592000 (30天），默认值 60 秒 |
-|s3PageCacheSize |s3 page cache 缓存页数目，单位：页。最小值：4；最大值：1024*1024\*1024。 ，默认值 4096|
-|s3MigrateIntervalSec | 本地数据文件自动上传 S3 的触发周期，单位为秒。最小值：600；最大值：100000。默认值 3600 |
-|s3MigrateEnabled | 是否自动进行 S3 迁移，默认值为 0，表示关闭自动 S3 迁移，可配置为 1。 |
+| 参数名称 | 参数含义 |
+|:---------------------|:-----------------------------------------------|
+| s3EndPoint           | 用户所在地域的 COS 服务域名，支持 http 和 https，bucket 的区域需要与 endpoint 的保持一致，否则无法访问。 |
+| s3AccessKey          | 冒号分隔的用户 SecretId:SecretKey。例如：AKIDsQmwsfKxTo2A6nGVXZN0UlofKn6JRRSJ:lIdoy99ygEacU7iHfogaN2Xq0yumSm1E |
+| s3BucketName         | 存储桶名称，减号后面是用户注册 COS 服务的 AppId。其中 AppId 是 COS 特有，AWS 和阿里云都没有，配置时需要作为 bucket name 的一部分，使用减号分隔。参数值均为字符串类型，但不需要引号。例如：test0711-1309024725 |
+| s3UploadDelaySec     | data 文件持续多长时间不再变动后上传至 s3，单位：秒。最小值：1；最大值：2592000（30天），默认值 60 秒 |
+| s3PageCacheSize      | S3 page cache 缓存页数目，单位：页。最小值：4；最大值：1024*1024*1024。 ，默认值 4096|
+| s3MigrateIntervalSec | 本地数据文件自动上传 S3 的触发周期，单位为秒。最小值：600；最大值：100000。默认值 3600 |
+| s3MigrateEnabled     | 是否自动进行 S3 迁移，默认值为 0，表示关闭自动 S3 迁移，可配置为 1。 |
 
 ### 检查配置参数可用性
 
-在 taos.cfg 中完成对 s3 的配置后，通过 taosd 命令的 checks3 参数可以检查所配置的 S3 服务是否可用：
+在 taos.cfg 中完成对 S3 的配置后，通过 taosd 命令的 checks3 参数可以检查所配置的 S3 服务是否可用：
 
 ```
 taosd --checks3
@@ -106,11 +106,11 @@ s3migrate database <db_name>;
 
 详细的 DB 参数见下表：
 
-| #    | 参数         | 默认值 | 最小值 | 最大值  | 描述                                                         |
-| :--- | :----------- | :----- | :----- | :------ | :----------------------------------------------------------- |
-| 1    | s3_keeplocal | 365    | 1      | 365000  | 数据在本地保留的天数，即 data 文件在本地磁盘保留多长时间后可以上传到 S3。默认单位：天，支持 m（分钟）、h（小时）和 d（天）三个单位 |
-| 2    | s3_chunkpages | 131072 | 131072 | 1048576 | 上传对象的大小阈值，与 tsdb_pagesize 参数一样，不可修改，单位为 TSDB 页 |
-| 3    | s3_compact   | 1      | 0      | 1       | TSDB 文件组首次上传 S3 时，是否自动进行 compact 操作。       |
+| # | 参数 | 默认值 | 最小值 | 最大值 | 描述 |
+|:--|:--------------|:-------|:------ |:------- | :----------------------------------------------------------- |
+| 1 | s3_keeplocal  | 365    | 1      | 365000  | 数据在本地保留的天数，即 data 文件在本地磁盘保留多长时间后可以上传到 S3。默认单位：天，支持 m（分钟）、h（小时）和 d（天）三个单位 |
+| 2 | s3_chunkpages | 131072 | 131072 | 1048576 | 上传对象的大小阈值，与 tsdb_pagesize 参数一样，不可修改，单位为 TSDB 页 |
+| 3 | s3_compact    | 1      | 0      | 1       | TSDB 文件组首次上传 S3 时，是否自动进行 compact 操作 |
 
 ### 对象存储读写次数估算
 
@@ -168,10 +168,10 @@ s3BucketName td-test
 
 用户界面同 S3，不同的地方在于下面三个参数的配置：
 
-| #    | 参数         | 示例值                                   | 描述                                                         |
-| :--- | :----------- | :--------------------------------------- | :----------------------------------------------------------- |
-| 1    | s3EndPoint   | https://fd2d01c73.blob.core.windows.net  | Blob URL                                                     |
-| 2    | s3AccessKey  | fd2d01c73:veUy/iRBeWaI2YAerl+AStw6PPqg== | 冒号分隔的用户 accountId:accountKey                          |
-| 3    | s3BucketName | test-container                           | Container name                                               |
+| # | 参数 | 示例值 | 描述 |
+|:--|:-------------|:-----------------------------------------|:----------------------------------|
+| 1 | s3EndPoint   | https://fd2d01c73.blob.core.windows.net  | Blob URL                          |
+| 2 | s3AccessKey  | fd2d01c73:veUy/iRBeWaI2YAerl+AStw6PPqg== | 冒号分隔的用户 accountId:accountKey |
+| 3 | s3BucketName | test-container                           | Container name                    |
 
 其中 fd2d01c73 是账户 ID；微软 Blob 存储服务只支持 Https 协议，不支持 Http。
diff --git a/docs/zh/14-reference/03-taos-sql/03-table.md b/docs/zh/14-reference/03-taos-sql/03-table.md
index a9f9ddb517..ca2170db8b 100644
--- a/docs/zh/14-reference/03-taos-sql/03-table.md
+++ b/docs/zh/14-reference/03-taos-sql/03-table.md
@@ -171,7 +171,7 @@ ALTER TABLE [db_name.]tb_name alter_table_clause
 
 alter_table_clause: {
     alter_table_options
-  | SET TAG tag_name = new_tag_value,tag_name2=new_tag2_value...
+  | SET TAG tag_name = new_tag_value, tag_name2=new_tag2_value ...
 }
 
 alter_table_options:
@@ -195,7 +195,7 @@ alter_table_option: {
 ### 修改子表标签值
 
 ```
-ALTER TABLE tb_name SET TAG tag_name1=new_tag_value1,tag_name2=new_tag_value2...;
+ALTER TABLE tb_name SET TAG tag_name1=new_tag_value1, tag_name2=new_tag_value2 ...;
 ```
 
 ### 修改表生命周期
diff --git a/docs/zh/14-reference/03-taos-sql/10-function.md b/docs/zh/14-reference/03-taos-sql/10-function.md
index 1d96db0969..7799e6f50e 100644
--- a/docs/zh/14-reference/03-taos-sql/10-function.md
+++ b/docs/zh/14-reference/03-taos-sql/10-function.md
@@ -1817,7 +1817,7 @@ ignore_null_values: {
 }
 ```
 
-**功能说明**：返回指定时间截面指定列的记录值或插值。ignore_null_values 参数的值可以是 0 或 1，为 1 时表示忽略 NULL 值, 缺省值为0。
+**功能说明**：返回指定时间截面指定列的记录值或插值。ignore_null_values 参数的值可以是 0 或 1，为 1 时表示忽略 NULL 值, 缺省值为 0。
 
 **返回数据类型**：同字段类型。
 
@@ -1838,9 +1838,9 @@ ignore_null_values: {
 - INTERP 可以与伪列 _irowts 一起使用，返回插值点所对应的时间戳(3.0.2.0 版本以后支持)。
 - INTERP 可以与伪列 _isfilled 一起使用，显示返回结果是否为原始记录或插值算法产生的数据(3.0.3.0 版本以后支持)。
 - INTERP 对于带复合主键的表的查询，若存在相同时间戳的数据，则只有对应的复合主键最小的数据参与运算。
-- INTERP 查询支持NEAR FILL模式, 即当需要FILL时, 使用距离当前时间点最近的数据进行插值, 当前后时间戳与当前时间断面一样近时, FILL 前一行的值. 此模式在流计算中和窗口查询中不支持。例如: SELECT INTERP(col) FROM tb RANGE('2023-01-01 00:00:00', '2023-01-01 00:10:00') FILL(NEAR)。(3.3.4.9版本及以后支持)。
-- INTERP 只有在使用FILL PREV/NEXT/NEAR 模式时才可以使用伪列 `_irowts_origin`。`_irowts_origin`在3.3.4.9版本及以后支持。
-- INTERP `RANEG`子句支持时间范围的扩展(3.3.4.9版本及以后支持), 如`RANGE('2023-01-01 00:00:00', 10s)`表示在时间点'2023-01-01 00:00:00'查找前后10s的数据进行插值, FILL PREV/NEXT/NEAR分别表示从时间点向前/向后/前后查找数据, 若时间点周围没有数据, 则使用FILL指定的值进行插值, 因此此时FILL子句必须指定值。例如: SELECT INTERP(col) FROM tb RANGE('2023-01-01 00:00:00', 10s) FILL(PREV, 1). 目前仅支持时间点和时间范围的组合, 不支持时间区间和时间范围的组合, 即不支持RANGE('2023-01-01 00:00:00', '2023-02-01 00:00:00', 1h)。所指定的时间范围规则与EVERY类似, 单位不能是年或月, 值不能为0, 不能带引号。使用该扩展时, 不支持除FILL PREV/NEXT/NEAR外的其他FILL模式, 且不能指定EVERY子句。
+- INTERP 查询支持 NEAR FILL 模式, 即当需要 FILL 时, 使用距离当前时间点最近的数据进行插值, 当前后时间戳与当前时间断面一样近时, FILL 前一行的值. 此模式在流计算中和窗口查询中不支持。例如: SELECT INTERP(col) FROM tb RANGE('2023-01-01 00:00:00', '2023-01-01 00:10:00') FILL(NEAR)(3.3.4.9 版本及以后支持)。
+- INTERP 只有在使用 FILL PREV/NEXT/NEAR 模式时才可以使用伪列 `_irowts_origin`。`_irowts_origin`在 3.3.4.9 版本及以后支持。
+- INTERP `RANGE`子句支持时间范围的扩展(3.3.4.9 版本及以后支持), 如`RANGE('2023-01-01 00:00:00', 10s)`表示在时间点 '2023-01-01 00:00:00' 查找前后 10s 的数据进行插值, FILL PREV/NEXT/NEAR 分别表示从时间点向前/向后/前后查找数据, 若时间点周围没有数据, 则使用 FILL 指定的值进行插值, 因此此时 FILL 子句必须指定值。例如: SELECT INTERP(col) FROM tb RANGE('2023-01-01 00:00:00', 10s) FILL(PREV, 1)。目前仅支持时间点和时间范围的组合, 不支持时间区间和时间范围的组合, 即不支持 RANGE('2023-01-01 00:00:00', '2023-02-01 00:00:00', 1h)。所指定的时间范围规则与 EVERY 类似, 单位不能是年或月, 值不能为 0, 不能带引号。使用该扩展时, 不支持除FILL PREV/NEXT/NEAR外的其他 FILL 模式, 且不能指定 EVERY 子句。
 
 ### LAST
 
diff --git a/docs/zh/14-reference/03-taos-sql/32-compress.md b/docs/zh/14-reference/03-taos-sql/32-compress.md
index 2ef6e9e06a..60d03e0cc0 100644
--- a/docs/zh/14-reference/03-taos-sql/32-compress.md
+++ b/docs/zh/14-reference/03-taos-sql/32-compress.md
@@ -30,13 +30,13 @@ description: 可配置压缩算法
 - 各个数据类型的默认压缩算法列表和适用范围
 
 | 数据类型 | 可选编码算法 | 编码算法默认值 | 可选压缩算法 | 压缩算法默认值 |压缩等级默认值|
-|:------------------------------------:|:----------------:|:-----------:|:--------------------:|:----:|:------:|
-| int/uint                             | simple8b         | simple8b    | lz4/zlib/zstd/xz     | lz4  | medium |
-| tinyint/untinyint/smallint/usmallint | simple8b         | simple8b    | lz4/zlib/zstd/xz     | zlib | medium |
-| bigint/ubigint/timestamp             | simple8b/delta-i | delta-i     | lz4/zlib/zstd/xz     | lz4  | medium |
-| float/double                         | delta-d          | delta-d     | lz4/zlib/zstd/xz/tsz | lz4  | medium |
-| binary/nchar                         | disabled         | disabled    | lz4/zlib/zstd/xz     | zstd | medium |
-| bool                                 | bit-packing      | bit-packing | lz4/zlib/zstd/xz     | zstd | medium |
+|:------------------------------------:|:-------------------------:|:-----------:|:--------------------:|:----:|:------:|
+| int/uint                             | disabled/simple8b         | simple8b    | lz4/zlib/zstd/xz     | lz4  | medium |
+| tinyint/untinyint/smallint/usmallint | disabled/simple8b         | simple8b    | lz4/zlib/zstd/xz     | zlib | medium |
+| bigint/ubigint/timestamp             | disabled/simple8b/delta-i | delta-i     | lz4/zlib/zstd/xz     | lz4  | medium |
+| float/double                         | disabled/delta-d          | delta-d     | lz4/zlib/zstd/xz/tsz | lz4  | medium |
+| binary/nchar                         | disabled                  | disabled    | lz4/zlib/zstd/xz     | zstd | medium |
+| bool                                 | disabled/bit-packing      | bit-packing | lz4/zlib/zstd/xz     | zstd | medium |
 
 
 ## SQL 语法

From 651bd16048b5737fa0c5d3c593665c37184b2b3d Mon Sep 17 00:00:00 2001
From: danielclow <106956386+danielclow@users.noreply.github.com>
Date: Tue, 10 Dec 2024 11:01:19 +0800
Subject: [PATCH 4/5] docs: unify codeblock language strings

---
 docs/en/06-advanced/05-data-in/07-mqtt.md     |  4 ++--
 docs/en/06-advanced/05-data-in/08-kafka.md    |  6 ++---
 docs/en/06-advanced/05-data-in/index.md       | 12 +++++-----
 docs/en/07-develop/02-sql.md                  | 10 ++++-----
 docs/en/07-develop/09-udf.md                  | 18 +++++++--------
 docs/en/08-operation/04-maintenance.md        |  4 ++--
 docs/en/08-operation/12-multi.md              |  6 ++---
 .../01-collection/09-emq-broker.md            |  2 +-
 .../10-third-party/01-collection/11-kafka.md  |  6 ++---
 .../10-third-party/03-visual/01-grafana.mdx   | 12 +++++-----
 .../en/14-reference/01-components/04-taosx.md |  8 +++----
 .../01-components/05-taosx-agent.md           |  6 ++---
 .../01-components/06-taoskeeper.md            |  6 ++---
 .../14-reference/01-components/07-explorer.md |  4 ++--
 .../01-components/12-tdinsight.mdx            |  4 ++--
 docs/en/14-reference/02-tools/08-taos-cli.md  |  4 ++--
 .../14-reference/02-tools/10-taosbenchmark.md |  6 ++---
 docs/en/14-reference/03-taos-sql/06-select.md | 12 +++++-----
 .../14-reference/03-taos-sql/10-function.md   |  4 ++--
 docs/en/14-reference/05-connector/20-go.mdx   |  2 +-
 .../14-reference/05-connector/60-rest-api.mdx | 22 +++++++++----------
 docs/en/27-train-faq/index.md                 |  6 ++---
 22 files changed, 82 insertions(+), 82 deletions(-)

diff --git a/docs/en/06-advanced/05-data-in/07-mqtt.md b/docs/en/06-advanced/05-data-in/07-mqtt.md
index 3f6eed5834..73ef3b534c 100644
--- a/docs/en/06-advanced/05-data-in/07-mqtt.md
+++ b/docs/en/06-advanced/05-data-in/07-mqtt.md
@@ -112,14 +112,14 @@ Fill in the example data from the MQTT message body in **Message Body**.
 
 JSON data supports JSONObject or JSONArray, and the json parser can parse the following data:
 
-``` json
+```json
 {"id": 1, "message": "hello-word"}
 {"id": 2, "message": "hello-word"}
 ```
 
 or
 
-``` json
+```json
 [{"id": 1, "message": "hello-word"},{"id": 2, "message": "hello-word"}]
 ```
 
diff --git a/docs/en/06-advanced/05-data-in/08-kafka.md b/docs/en/06-advanced/05-data-in/08-kafka.md
index bdd652a5e7..b3bdca4cf9 100644
--- a/docs/en/06-advanced/05-data-in/08-kafka.md
+++ b/docs/en/06-advanced/05-data-in/08-kafka.md
@@ -109,7 +109,7 @@ In addition, the [Kerberos](https://web.mit.edu/kerberos/) authentication servic
 
 After configuration, you can use the [kcat](https://github.com/edenhill/kcat) tool to verify Kafka topic consumption:
 
-```bash
+```shell
 kcat <topic> \
   -b <kafka-server:port> \
   -G kcat \
@@ -171,14 +171,14 @@ Enter sample data from the Kafka message body in **Message Body**.
 
 JSON data supports JSONObject or JSONArray, and the following data can be parsed using a JSON parser:
 
-``` json
+```json
 {"id": 1, "message": "hello-word"}
 {"id": 2, "message": "hello-word"}
 ```
 
 or
 
-``` json
+```json
 [{"id": 1, "message": "hello-word"},{"id": 2, "message": "hello-word"}]
 ```
 
diff --git a/docs/en/06-advanced/05-data-in/index.md b/docs/en/06-advanced/05-data-in/index.md
index 59a3c6da7b..5221aa2002 100644
--- a/docs/en/06-advanced/05-data-in/index.md
+++ b/docs/en/06-advanced/05-data-in/index.md
@@ -83,7 +83,7 @@ Parsing is the process of parsing unstructured strings into structured data. The
 
 JSON parsing supports JSONObject or JSONArray. The following JSON sample data can automatically parse fields: `groupid`, `voltage`, `current`, `ts`, `inuse`, `location`.
 
-``` json
+```json
 {"groupid": 170001, "voltage": "221V", "current": 12.3, "ts": "2023-12-18T22:12:00", "inuse": true, "location": "beijing.chaoyang.datun"}
 {"groupid": 170001, "voltage": "220V", "current": 12.2, "ts": "2023-12-18T22:12:02", "inuse": true, "location": "beijing.chaoyang.datun"}
 {"groupid": 170001, "voltage": "216V", "current": 12.5, "ts": "2023-12-18T22:12:04", "inuse": false, "location": "beijing.chaoyang.datun"}
@@ -91,7 +91,7 @@ JSON parsing supports JSONObject or JSONArray. The following JSON sample data ca
 
 Or
 
-``` json
+```json
 [{"groupid": 170001, "voltage": "221V", "current": 12.3, "ts": "2023-12-18T22:12:00", "inuse": true, "location": "beijing.chaoyang.datun"},
 {"groupid": 170001, "voltage": "220V", "current": 12.2, "ts": "2023-12-18T22:12:02", "inuse": true, "location": "beijing.chaoyang.datun"},
 {"groupid": 170001, "voltage": "216V", "current": 12.5, "ts": "2023-12-18T22:12:04", "inuse": false, "location": "beijing.chaoyang.datun"}]
@@ -101,7 +101,7 @@ Subsequent examples will only explain using JSONObject.
 
 The following nested JSON data can automatically parse fields `groupid`, `data_voltage`, `data_current`, `ts`, `inuse`, `location_0_province`, `location_0_city`, `location_0_datun`, and you can also choose which fields to parse and set aliases for the parsed fields.
 
-``` json
+```json
 {"groupid": 170001, "data": { "voltage": "221V", "current": 12.3 }, "ts": "2023-12-18T22:12:00", "inuse": true, "location": [{"province": "beijing", "city":"chaoyang", "street": "datun"}]}
 ```
 
@@ -114,7 +114,7 @@ The following nested JSON data can automatically parse fields `groupid`, `data_v
 
 You can use **named capture groups** in regular expressions to extract multiple fields from any string (text) field. As shown in the figure, extract fields such as access IP, timestamp, and accessed URL from nginx logs.
 
-``` re
+```regex
 (?<ip>\b(?:[0-9]{1,3}\.){3}[0-9]{1,3}\b)\s-\s-\s\[(?<ts>\d{2}/\w{3}/\d{4}:\d{2}:\d{2}:\d{2}\s\+\d{4})\]\s"(?<method>[A-Z]+)\s(?<url>[^\s"]+).*(?<status>\d{3})\s(?<length>\d+)
 ```
 
@@ -133,7 +133,7 @@ Custom rhai syntax scripts for parsing input data (refer to `https://rhai.rs/boo
 
 For example, for data reporting three-phase voltage values, which are entered into three subtables respectively, such data needs to be parsed
 
-``` json
+```json
 {
     "ts": "2024-06-27 18:00:00", 
     "voltage": "220.1,220.3,221.1", 
@@ -164,7 +164,7 @@ The final parsing result is shown below:
 
 The parsed data may still not meet the data requirements of the target table. For example, the original data collected by a smart meter is as follows (in json format):
 
-``` json
+```json
 {"groupid": 170001, "voltage": "221V", "current": 12.3, "ts": "2023-12-18T22:12:00", "inuse": true, "location": "beijing.chaoyang.datun"}
 {"groupid": 170001, "voltage": "220V", "current": 12.2, "ts": "2023-12-18T22:12:02", "inuse": true, "location": "beijing.chaoyang.datun"}
 {"groupid": 170001, "voltage": "216V", "current": 12.5, "ts": "2023-12-18T22:12:04", "inuse": false, "location": "beijing.chaoyang.datun"}
diff --git a/docs/en/07-develop/02-sql.md b/docs/en/07-develop/02-sql.md
index 57376e615d..d32ff340f3 100644
--- a/docs/en/07-develop/02-sql.md
+++ b/docs/en/07-develop/02-sql.md
@@ -83,14 +83,14 @@ Next, create a supertable (STABLE) named `meters`, whose table structure include
 
 Create Database
 
-```bash
+```shell
 curl --location -uroot:taosdata 'http://127.0.0.1:6041/rest/sql' \
 --data 'CREATE DATABASE IF NOT EXISTS power'
 ```
 
 Create Table, specify the database as `power` in the URL
 
-```bash
+```shell
 curl --location -uroot:taosdata 'http://127.0.0.1:6041/rest/sql/power' \
 --data 'CREATE STABLE IF NOT EXISTS meters (ts TIMESTAMP, current FLOAT, voltage INT, phase FLOAT) TAGS (groupId INT, location BINARY(24))'
 ```
@@ -167,7 +167,7 @@ NOW is an internal system function, defaulting to the current time of the client
 
 Write data
 
-```bash
+```shell
 curl --location -uroot:taosdata 'http://127.0.0.1:6041/rest/sql' \
 --data 'INSERT INTO power.d1001 USING power.meters TAGS(2,'\''California.SanFrancisco'\'') VALUES (NOW + 1a, 10.30000, 219, 0.31000) (NOW + 2a, 12.60000, 218, 0.33000) (NOW + 3a, 12.30000, 221, 0.31000) power.d1002 USING power.meters TAGS(3, '\''California.SanFrancisco'\'') VALUES (NOW + 1a, 10.30000, 218, 0.25000)'
 ```
@@ -247,7 +247,7 @@ Rust connector also supports using **serde** for deserializing to get structured
 
 Query Data
 
-```bash
+```shell
 curl --location -uroot:taosdata 'http://127.0.0.1:6041/rest/sql' \
 --data 'SELECT ts, current, location FROM power.meters limit 100'
 ```
@@ -329,7 +329,7 @@ Below are code examples of setting reqId to execute SQL in various language conn
 
 Query data, specify reqId as 3
 
-```bash
+```shell
 curl --location -uroot:taosdata 'http://127.0.0.1:6041/rest/sql?req_id=3' \
 --data 'SELECT ts, current, location FROM power.meters limit 1'
 ```
diff --git a/docs/en/07-develop/09-udf.md b/docs/en/07-develop/09-udf.md
index 795556c225..0e91dd09db 100644
--- a/docs/en/07-develop/09-udf.md
+++ b/docs/en/07-develop/09-udf.md
@@ -273,19 +273,19 @@ To better operate the above data structures, some convenience functions are prov
 
 Create table:
 
-```bash
+```shell
 create table battery(ts timestamp, vol1 float, vol2 float, vol3 float, deviceId varchar(16));
 ```
 
 Create custom function:
 
-```bash
+```shell
 create aggregate function max_vol as '/root/udf/libmaxvol.so' outputtype binary(64) bufsize 10240 language 'C'; 
 ```
 
 Use custom function:
 
-```bash
+```shell
 select max_vol(vol1, vol2, vol3, deviceid) from battery;
 ```
 
@@ -334,7 +334,7 @@ When developing UDFs in Python, you need to implement the specified interface fu
 
 The interface for scalar functions is as follows.
 
-```Python
+```python
 def process(input: datablock) -> tuple[output_type]:
 ```
 
@@ -347,7 +347,7 @@ The main parameters are as follows:
 
 The interface for aggregate functions is as follows.
 
-```Python
+```python
 def start() -> bytes:
 def reduce(inputs: datablock, buf: bytes) -> bytes
 def finish(buf: bytes) -> output_type:
@@ -365,7 +365,7 @@ Finally, when all row data blocks have been processed, the finish function is ca
 
 The interfaces for initialization and destruction are as follows.
 
-```Python
+```python
 def init()
 def destroy()
 ```
@@ -381,7 +381,7 @@ Parameter description:
 
 The template for developing scalar functions in Python is as follows.
 
-```Python
+```python
 def init():
     # initialization
 def destroy():
@@ -393,7 +393,7 @@ def process(input: datablock) -> tuple[output_type]:
 
 The template for developing aggregate functions in Python is as follows.
 
-```Python
+```python
 def init():
     #initialization
 def destroy():
@@ -828,7 +828,7 @@ Through this example, we learned how to define aggregate functions and print cus
 <details>
 <summary>pybitand.py</summary>
 
-```Python
+```python
 {{#include tests/script/sh/pybitand.py}}
 ```
 
diff --git a/docs/en/08-operation/04-maintenance.md b/docs/en/08-operation/04-maintenance.md
index 5e7fca1f08..970ee40d18 100644
--- a/docs/en/08-operation/04-maintenance.md
+++ b/docs/en/08-operation/04-maintenance.md
@@ -15,7 +15,7 @@ TDengine is designed for various writing scenarios, and many of these scenarios
 
 ### Syntax
 
-```SQL
+```sql
 COMPACT DATABASE db_name [start with 'XXXX'] [end with 'YYYY'];
 SHOW COMPACTS [compact_id];
 KILL COMPACT compact_id;
@@ -41,7 +41,7 @@ KILL COMPACT compact_id;
 
 When one or more nodes in a multi-replica cluster restart due to upgrades or other reasons, it may lead to an imbalance in the load among the various dnodes in the cluster. In extreme cases, all vgroup leaders may be located on the same dnode. To solve this problem, you can use the following commands, which were first released in version 3.0.4.0. It is recommended to use the latest version as much as possible.
 
-```SQL
+```sql
 balance vgroup leader; # Rebalance all vgroup leaders
 balance vgroup leader on <vgroup_id>; # Rebalance a vgroup leader
 balance vgroup leader database <database_name>; # Rebalance all vgroup leaders within a database
diff --git a/docs/en/08-operation/12-multi.md b/docs/en/08-operation/12-multi.md
index f2f464be1c..1d0b8ad6cb 100644
--- a/docs/en/08-operation/12-multi.md
+++ b/docs/en/08-operation/12-multi.md
@@ -121,7 +121,7 @@ The cost of using object storage services is related to the amount of data store
 
 When the TSDB time-series data exceeds the time specified by the `s3_keeplocal` parameter, the related data files will be split into multiple file blocks, each with a default size of 512 MB (`s3_chunkpages * tsdb_pagesize`). Except for the last file block, which is retained on the local file system, the rest of the file blocks are uploaded to the object storage service.
 
-```math
+```text
 Upload Count = Data File Size / (s3_chunkpages * tsdb_pagesize) - 1
 ```
 
@@ -135,7 +135,7 @@ During query operations, if data in object storage needs to be accessed, TSDB do
 
 Adjacent multiple data pages are downloaded as a single data block from object storage to reduce the number of downloads. The size of each data page is specified by the `tsdb_pagesize` parameter when creating the database, with a default of 4 KB.
 
-```math
+```text
 Download Count = Number of Data Blocks Needed for Query - Number of Cached Data Blocks
 ```
 
@@ -155,7 +155,7 @@ For deployment methods, please refer to the [Flexify](https://azuremarketplace.m
 
 In the configuration file /etc/taos/taos.cfg, add parameters for S3 access:
 
-```cfg
+```text
 s3EndPoint   http //20.191.157.23,http://20.191.157.24,http://20.191.157.25
 s3AccessKey  FLIOMMNL0:uhRNdeZMLD4wo,ABCIOMMN:uhRNdeZMD4wog,DEFOMMNL049ba:uhRNdeZMLD4wogXd
 s3BucketName td-test
diff --git a/docs/en/10-third-party/01-collection/09-emq-broker.md b/docs/en/10-third-party/01-collection/09-emq-broker.md
index 24cb12997f..4f3eadcca6 100644
--- a/docs/en/10-third-party/01-collection/09-emq-broker.md
+++ b/docs/en/10-third-party/01-collection/09-emq-broker.md
@@ -140,7 +140,7 @@ Finally, click the "Create" button at the bottom left to save the rule.
 
 ## Write a Mock Test Program
 
-```javascript
+```js
 {{#include docs/examples/other/mock.js}}
 ```
 
diff --git a/docs/en/10-third-party/01-collection/11-kafka.md b/docs/en/10-third-party/01-collection/11-kafka.md
index 2627e33b65..25ba7fd54a 100644
--- a/docs/en/10-third-party/01-collection/11-kafka.md
+++ b/docs/en/10-third-party/01-collection/11-kafka.md
@@ -95,7 +95,7 @@ curl http://localhost:8083/connectors
 
 If all components have started successfully, the following output will be displayed:
 
-```txt
+```text
 []
 ```
 
@@ -181,7 +181,7 @@ If the above command is executed successfully, the following output will be disp
 
 Prepare a text file with test data, content as follows:
 
-```txt title="test-data.txt"
+```text title="test-data.txt"
 meters,location=California.LosAngeles,groupid=2 current=11.8,voltage=221,phase=0.28 1648432611249000000
 meters,location=California.LosAngeles,groupid=2 current=13.4,voltage=223,phase=0.29 1648432611250000000
 meters,location=California.LosAngeles,groupid=3 current=10.8,voltage=223,phase=0.29 1648432611249000000
@@ -303,7 +303,7 @@ kafka-console-consumer.sh --bootstrap-server localhost:9092 --from-beginning --t
 
 Output:
 
-```txt
+```text
 ......
 meters,location="California.SanFrancisco",groupid=2i32 current=10.3f32,voltage=219i32,phase=0.31f32 1538548685000000000
 meters,location="California.SanFrancisco",groupid=2i32 current=12.6f32,voltage=218i32,phase=0.33f32 1538548695000000000
diff --git a/docs/en/10-third-party/03-visual/01-grafana.mdx b/docs/en/10-third-party/03-visual/01-grafana.mdx
index bd2d313def..ec857f7795 100644
--- a/docs/en/10-third-party/03-visual/01-grafana.mdx
+++ b/docs/en/10-third-party/03-visual/01-grafana.mdx
@@ -60,7 +60,7 @@ Click `Save & Test` to test, if successful, it will prompt: `TDengine Data sourc
 
 For users using Grafana version 7.x or configuring with [Grafana Provisioning](https://grafana.com/docs/grafana/latest/administration/provisioning/), you can use the installation script on the Grafana server to automatically install the plugin and add the data source Provisioning configuration file.
 
-```sh
+```shell
 bash -c "$(curl -fsSL \
   https://raw.githubusercontent.com/taosdata/grafanaplugin/master/install.sh)" -- \
   -a http://localhost:6041 \
@@ -77,7 +77,7 @@ Save the script and execute `./install.sh --help` to view detailed help document
 
 Use the [`grafana-cli` command line tool](https://grafana.com/docs/grafana/latest/administration/cli/) to install the plugin [installation](https://grafana.com/grafana/plugins/tdengine-datasource/?tab=installation).
 
-```bash
+```shell
 grafana-cli plugins install tdengine-datasource
 # with sudo
 sudo -u grafana grafana-cli plugins install tdengine-datasource
@@ -85,7 +85,7 @@ sudo -u grafana grafana-cli plugins install tdengine-datasource
 
 Alternatively, download the .zip file from [GitHub](https://github.com/taosdata/grafanaplugin/releases/tag/latest) or [Grafana](https://grafana.com/grafana/plugins/tdengine-datasource/?tab=installation) to your local machine and unzip it into the Grafana plugins directory. Example command line download is as follows:
 
-```bash
+```shell
 GF_VERSION=3.5.1
 # from GitHub
 wget https://github.com/taosdata/grafanaplugin/releases/download/v$GF_VERSION/tdengine-datasource-$GF_VERSION.zip
@@ -95,13 +95,13 @@ wget -O tdengine-datasource-$GF_VERSION.zip https://grafana.com/api/plugins/tden
 
 For CentOS 7.2 operating system, unzip the plugin package into the /var/lib/grafana/plugins directory and restart Grafana.
 
-```bash
+```shell
 sudo unzip tdengine-datasource-$GF_VERSION.zip -d /var/lib/grafana/plugins/
 ```
 
 If Grafana is running in a Docker environment, you can use the following environment variable to set up automatic installation of the TDengine data source plugin:
 
-```bash
+```shell
 GF_INSTALL_PLUGINS=tdengine-datasource
 ```
 
@@ -120,7 +120,7 @@ Click `Save & Test` to test, if successful, it will prompt: `TDengine Data sourc
 
 Refer to [Grafana containerized installation instructions](https://grafana.com/docs/grafana/next/setup-grafana/installation/docker/#install-plugins-in-the-docker-container). Use the following command to start a container and automatically install the TDengine plugin:
 
-```bash
+```shell
 docker run -d \
   -p 3000:3000 \
   --name=grafana \
diff --git a/docs/en/14-reference/01-components/04-taosx.md b/docs/en/14-reference/01-components/04-taosx.md
index b53d9f6777..8ce16f471d 100644
--- a/docs/en/14-reference/01-components/04-taosx.md
+++ b/docs/en/14-reference/01-components/04-taosx.md
@@ -31,7 +31,7 @@ The following parameter descriptions and examples use `<content>` as a placehold
 
 In command line mode, taosX uses DSN to represent a data source (source or destination), a typical DSN is as follows:
 
-```bash
+```shell
 # url-like
 <driver>[+<protocol>]://[[<username>:<password>@]<host>:<port>][/<object>][?<p1>=<v1>[&<p2>=<v2>]]
 |------|------------|---|-----------|-----------|------|------|----------|-----------------------|
@@ -390,7 +390,7 @@ You can view the log files or use the `journalctl` command to view the logs of `
 
 The command to view logs under Linux using `journalctl` is as follows:
 
-```bash
+```shell
 journalctl -u taosx [-f]
 ```
 
@@ -572,7 +572,7 @@ uint32_t len: The binary length of this string (excluding `\0`).
 
 **Return Value**:
 
-``` c
+```c
 struct parser_resp_t {
   int e;    // 0 if success.
   void* p;  // Success if contains.
@@ -589,7 +589,7 @@ When creation is successful, e = 0, p is the parser object.
 
 Parse the input payload and return the result in JSON format [u8]. The returned JSON will be fully decoded using the default JSON parser (expanding the root array and all objects).
 
-``` c
+```c
 const char* parser_mutate(
   void* parser,
   const uint8_t* in_ptr, uint32_t in_len,
diff --git a/docs/en/14-reference/01-components/05-taosx-agent.md b/docs/en/14-reference/01-components/05-taosx-agent.md
index 9353d45de3..3e8b4f4d63 100644
--- a/docs/en/14-reference/01-components/05-taosx-agent.md
+++ b/docs/en/14-reference/01-components/05-taosx-agent.md
@@ -26,7 +26,7 @@ The default configuration file for `Agent` is located at `/etc/taos/agent.toml`,
 
 As shown below:
 
-```TOML
+```toml
 # taosX service endpoint
 #
 #endpoint = "http://localhost:6055"
@@ -83,7 +83,7 @@ You don't need to be confused about how to set up the configuration file. Read a
 
 On Linux systems, the `Agent` can be started with the Systemd command:
 
-```bash
+```shell
 systemctl start taosx-agent
 ```
 
@@ -95,6 +95,6 @@ You can view the log files or use the `journalctl` command to view the logs of t
 
 The command to view logs with `journalctl` on Linux is as follows:
 
-```bash
+```shell
 journalctl -u taosx-agent [-f]
 ```
diff --git a/docs/en/14-reference/01-components/06-taoskeeper.md b/docs/en/14-reference/01-components/06-taoskeeper.md
index 570cf7305f..78556d888a 100644
--- a/docs/en/14-reference/01-components/06-taoskeeper.md
+++ b/docs/en/14-reference/01-components/06-taoskeeper.md
@@ -143,13 +143,13 @@ For details on TDengine monitoring configuration, please refer to: [TDengine Mon
 
 After installation, please use the `systemctl` command to start the taoskeeper service process.
 
-```bash
+```shell
 systemctl start taoskeeper
 ```
 
 Check if the service is working properly:
 
-```bash
+```shell
 systemctl status taoskeeper
 ```
 
@@ -261,7 +261,7 @@ Query OK, 14 row(s) in set (0.006542s)
 
 You can view the most recent report record of a supertable, such as:
 
-``` shell
+```shell
 taos> select last_row(*) from taosd_dnodes_info;
       last_row(_ts)      |   last_row(disk_engine)   |  last_row(system_net_in)  |   last_row(vnodes_num)    | last_row(system_net_out)  |     last_row(uptime)      |    last_row(has_mnode)    |  last_row(io_read_disk)   | last_row(error_log_count) |     last_row(io_read)     |    last_row(cpu_cores)    |    last_row(has_qnode)    |    last_row(has_snode)    |   last_row(disk_total)    |   last_row(mem_engine)    | last_row(info_log_count)  |   last_row(cpu_engine)    |  last_row(io_write_disk)  | last_row(debug_log_count) |    last_row(disk_used)    |    last_row(mem_total)    |    last_row(io_write)     |     last_row(masters)     |   last_row(cpu_system)    | last_row(trace_log_count) |    last_row(mem_free)     |
 ======================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================
diff --git a/docs/en/14-reference/01-components/07-explorer.md b/docs/en/14-reference/01-components/07-explorer.md
index 726b07d050..a9a2ebb356 100644
--- a/docs/en/14-reference/01-components/07-explorer.md
+++ b/docs/en/14-reference/01-components/07-explorer.md
@@ -14,7 +14,7 @@ taosExplorer does not require separate installation. Starting from TDengine vers
 
 Before starting taosExplorer, please make sure the content in the configuration file is correct.
 
-```TOML
+```toml
 # This is an automatically generated configuration file for Explorer in [TOML](https://toml.io/) format.
 #
 # Here is a full list of available options.
@@ -148,7 +148,7 @@ Description:
 
 Then start taosExplorer, you can directly execute taos-explorer in the command line or use the systemctl command:
 
-```bash
+```shell
 systemctl start taos-explorer  # Linux
 sc.exe start taos-explorer # Windows
 ```
diff --git a/docs/en/14-reference/01-components/12-tdinsight.mdx b/docs/en/14-reference/01-components/12-tdinsight.mdx
index 463ceaaca6..12423c512d 100644
--- a/docs/en/14-reference/01-components/12-tdinsight.mdx
+++ b/docs/en/14-reference/01-components/12-tdinsight.mdx
@@ -248,13 +248,13 @@ The new version of the plugin uses the Grafana unified alerting feature, the `-E
 
 Assuming you start the TDengine database on the host `tdengine` with HTTP API port `6041`, user `root1`, and password `pass5ord`. Execute the script:
 
-```bash
+```shell
 ./TDinsight.sh -a http://tdengine:6041 -u root1 -p pass5ord
 ```
 
 If you want to monitor multiple TDengine clusters, you need to set up multiple TDinsight dashboards. Setting up a non-default TDinsight requires some changes: the `-n` `-i` `-t` options need to be changed to non-default names, and if using the built-in SMS alert feature, `-N` and `-L` should also be changed.
 
-```bash
+```shell
 sudo ./TDengine.sh -n TDengine-Env1 -a http://another:6041 -u root -p taosdata -i tdinsight-env1 -t 'TDinsight Env1'
 ```
 
diff --git a/docs/en/14-reference/02-tools/08-taos-cli.md b/docs/en/14-reference/02-tools/08-taos-cli.md
index 1dd77de186..9309da831d 100644
--- a/docs/en/14-reference/02-tools/08-taos-cli.md
+++ b/docs/en/14-reference/02-tools/08-taos-cli.md
@@ -10,7 +10,7 @@ The TDengine command line program (hereinafter referred to as TDengine CLI) is t
 
 To enter the TDengine CLI, simply execute `taos` in the terminal.
 
-```bash
+```shell
 taos
 ```
 
@@ -81,7 +81,7 @@ There are many other parameters:
 
 Example:
 
-```bash
+```shell
 taos -h h1.taos.com -s "use db; show tables;"
 ```
 
diff --git a/docs/en/14-reference/02-tools/10-taosbenchmark.md b/docs/en/14-reference/02-tools/10-taosbenchmark.md
index c41cff49e1..09227f210b 100644
--- a/docs/en/14-reference/02-tools/10-taosbenchmark.md
+++ b/docs/en/14-reference/02-tools/10-taosbenchmark.md
@@ -28,7 +28,7 @@ taosBenchmark supports comprehensive performance testing for TDengine, and the T
 
 Execute the following command to quickly experience taosBenchmark performing a write performance test on TDengine based on the default configuration.
 
-```bash
+```shell
 taosBenchmark
 ```
 
@@ -38,7 +38,7 @@ When running without parameters, taosBenchmark by default connects to the TDengi
 
 When running taosBenchmark using command line parameters and controlling its behavior, the `-f <json file>` parameter cannot be used. All configuration parameters must be specified through the command line. Below is an example of using command line mode to test the write performance of taosBenchmark.
 
-```bash
+```shell
 taosBenchmark -I stmt -n 200 -t 100
 ```
 
@@ -50,7 +50,7 @@ The taosBenchmark installation package includes examples of configuration files,
 
 Use the following command line to run taosBenchmark and control its behavior through a configuration file.
 
-```bash
+```shell
 taosBenchmark -f <json file>
 ```
 
diff --git a/docs/en/14-reference/03-taos-sql/06-select.md b/docs/en/14-reference/03-taos-sql/06-select.md
index 5c71697110..c33fef95fb 100644
--- a/docs/en/14-reference/03-taos-sql/06-select.md
+++ b/docs/en/14-reference/03-taos-sql/06-select.md
@@ -210,19 +210,19 @@ However, renaming individual columns is not supported for `first(*)`, `last(*)`,
 
 Retrieve all subtable names and related tag information from a supertable:
 
-```mysql
+```sql
 SELECT TAGS TBNAME, location FROM meters;
 ```
 
 It is recommended that users query the subtable tag information of supertables using the INS_TAGS system table under INFORMATION_SCHEMA, for example, to get all subtable names and tag values of the supertable meters:
 
-```mysql
+```sql
 SELECT table_name, tag_name, tag_type, tag_value FROM information_schema.ins_tags WHERE stable_name='meters';
 ```
 
 Count the number of subtables under a supertable:
 
-```mysql
+```sql
 SELECT COUNT(*) FROM (SELECT DISTINCT TBNAME FROM meters);
 ```
 
@@ -385,7 +385,7 @@ SELECT CURRENT_USER();
 
 ### Syntax
 
-```txt
+```text
 WHERE (column|tbname) match/MATCH/nmatch/NMATCH _regex_
 ```
 
@@ -403,7 +403,7 @@ The length of the regular match string cannot exceed 128 bytes. You can set and
 
 ### Syntax
 
-```txt
+```text
 CASE value WHEN compare_value THEN result [WHEN compare_value THEN result ...] [ELSE result] END
 CASE WHEN condition THEN result [WHEN condition THEN result ...] [ELSE result] END
 ```
@@ -493,7 +493,7 @@ SELECT ... FROM (SELECT ... FROM ...) ...;
 
 ## UNION ALL Clause
 
-```txt title=Syntax
+```text title=Syntax
 SELECT ...
 UNION ALL SELECT ...
 [UNION ALL SELECT ...]
diff --git a/docs/en/14-reference/03-taos-sql/10-function.md b/docs/en/14-reference/03-taos-sql/10-function.md
index fa6b8d333a..4eb7b083fb 100644
--- a/docs/en/14-reference/03-taos-sql/10-function.md
+++ b/docs/en/14-reference/03-taos-sql/10-function.md
@@ -417,7 +417,7 @@ MOD(expr1, expr2)
 
 **Example**:
 
-``` sql
+```sql
 taos> select mod(10,3);
          mod(10,3)         |
 ============================
@@ -454,7 +454,7 @@ RAND([seed])
 
 **Example**:
 
-``` sql
+```sql
 taos> select rand();
           rand()           |
 ============================
diff --git a/docs/en/14-reference/05-connector/20-go.mdx b/docs/en/14-reference/05-connector/20-go.mdx
index b6313ae3b1..3342066a3d 100644
--- a/docs/en/14-reference/05-connector/20-go.mdx
+++ b/docs/en/14-reference/05-connector/20-go.mdx
@@ -108,7 +108,7 @@ For the source code of the example programs, please refer to: [Example Programs]
 
 The Data Source Name has a generic format, similar to [PEAR DB](http://pear.php.net/manual/en/package.database.db.intro-dsn.php), but without the type prefix (brackets indicate optional):
 
-``` text
+```text
 [username[:password]@][protocol[(address)]]/[dbname][?param1=value1&...&paramN=valueN]
 ```
 
diff --git a/docs/en/14-reference/05-connector/60-rest-api.mdx b/docs/en/14-reference/05-connector/60-rest-api.mdx
index a63022f547..88e53f7618 100644
--- a/docs/en/14-reference/05-connector/60-rest-api.mdx
+++ b/docs/en/14-reference/05-connector/60-rest-api.mdx
@@ -21,7 +21,7 @@ Below is an example using the `curl` tool in an Ubuntu environment (please confi
 
 The following example lists all databases, please replace `h1.tdengine.com` and 6041 (default value) with the actual running TDengine service FQDN and port number:
 
-```bash
+```shell
 curl -L -H "Authorization: Basic cm9vdDp0YW9zZGF0YQ==" \
   -d "select name, ntables, status from information_schema.ins_databases;" \
   h1.tdengine.com:6041/rest/sql
@@ -100,13 +100,13 @@ The BODY of the HTTP request contains a complete SQL statement. The data table i
 
 Use `curl` to initiate an HTTP Request with custom authentication as follows:
 
-```bash
+```shell
 curl -L -H "Authorization: Basic <TOKEN>" -d "<SQL>" <ip>:<PORT>/rest/sql/[db_name][?tz=timezone[&req_id=req_id][&row_with_meta=true]]
 ```
 
 Or,
 
-```bash
+```shell
 curl -L -u username:password -d "<SQL>" <ip>:<PORT>/rest/sql/[db_name][?tz=timezone[&req_id=req_id][&row_with_meta=true]]
 ```
 
@@ -279,7 +279,7 @@ Column types use the following strings:
 
 Prepare data
 
-```bash
+```shell
 create database demo
 use demo
 create table t(ts timestamp,c1 varbinary(20),c2 geometry(100))
@@ -288,7 +288,7 @@ insert into t values(now,'\x7f8290','point(100 100)')
 
 Execute query
 
-```bash
+```shell
 curl --location 'http://<fqdn>:<port>/rest/sql' \
 --header 'Content-Type: text/plain' \
 --header 'Authorization: Basic cm9vdDp0YW9zZGF0YQ==' \
@@ -428,7 +428,7 @@ Data Query Return Example
 
 HTTP requests need to include an authorization code `<TOKEN>`, used for identity verification. The authorization code is usually provided by the administrator and can be simply obtained by sending an `HTTP GET` request as follows:
 
-```bash
+```shell
 curl http://<fqnd>:<port>/rest/login/<username>/<password>
 ```
 
@@ -440,7 +440,7 @@ Here, `fqdn` is the FQDN or IP address of the TDengine database, `port` is the p
 
 Example of obtaining an authorization code:
 
-```bash
+```shell
 curl http://192.168.0.1:6041/rest/login/root/taosdata
 ```
 
@@ -457,7 +457,7 @@ Return value:
 
 - Query all records of table d1001 in the demo database:
 
-  ```bash
+  ```shell
   curl -L -H "Authorization: Basic cm9vdDp0YW9zZGF0YQ==" -d "select * from demo.d1001" 192.168.0.1:6041/rest/sql
   curl -L -H "Authorization: Taosd /KfeAzX/f9na8qdtNZmtONryp201ma04bEl8LcvLUd7a8qdtNZmtONryp201ma04" -d "select * from demo.d1001" 192.168.0.1:6041/rest/sql
   ```
@@ -509,7 +509,7 @@ Return value:
 
 - Create database demo:
 
-  ```bash
+  ```shell
   curl -L -H "Authorization: Basic cm9vdDp0YW9zZGF0YQ==" -d "create database demo" 192.168.0.1:6041/rest/sql
   curl -L -H "Authorization: Taosd /KfeAzX/f9na8qdtNZmtONryp201ma04bEl8LcvLUd7a8qdtNZmtONryp201ma04" -d "create database demo" 192.168.0.1:6041/rest/sql
   ```
@@ -560,7 +560,7 @@ Return value:
 
 #### TDengine 2.x response codes and message bodies
 
-```JSON
+```json
 {
   "status": "succ",
   "head": [
@@ -624,7 +624,7 @@ Return value:
 
 #### TDengine 3.0 Response Codes and Message Body
 
-```JSON
+```json
 {
     "code": 0,
     "column_meta": [
diff --git a/docs/en/27-train-faq/index.md b/docs/en/27-train-faq/index.md
index 3b3f7a8e17..a5ec977e29 100644
--- a/docs/en/27-train-faq/index.md
+++ b/docs/en/27-train-faq/index.md
@@ -90,7 +90,7 @@ Batch insertion. Each insert statement can insert multiple records into one tabl
 
 When inserting nchar type data containing Chinese characters on Windows, first ensure that the system's regional settings are set to China (this can be set in the Control Panel). At this point, the `taos` client in cmd should already be working properly; if developing a Java application in an IDE, such as Eclipse or IntelliJ, ensure that the file encoding in the IDE is set to GBK (which is the default encoding type for Java), then initialize the client configuration when creating the Connection, as follows:
 
-```JAVA
+```java
 Class.forName("com.taosdata.jdbc.TSDBDriver");
 Properties properties = new Properties();
 properties.setProperty(TSDBDriver.LOCALE_KEY, "UTF-8");
@@ -145,7 +145,7 @@ Version 3.0 of TDengine includes a standalone component developed in Go called `
 
 The Go language version requirement is 1.14 or higher. If there are Go compilation errors, often due to issues accessing Go mod in China, they can be resolved by setting Go environment variables:
 
-```sh
+```shell
 go env -w GO111MODULE=on
 go env -w GOPROXY=https://goproxy.cn,direct
 ```
@@ -196,7 +196,7 @@ Here are the solutions:
 
 1. Create a file /Library/LaunchDaemons/limit.maxfiles.plist, write the following content (the example changes limit and maxfiles to 100,000, modify as needed):
 
-```plist
+```xml
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
 "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

From 81a2e21c7dccc282d046a2a817cfad17f3e96db4 Mon Sep 17 00:00:00 2001
From: danielclow <106956386+danielclow@users.noreply.github.com>
Date: Tue, 10 Dec 2024 18:05:29 +0800
Subject: [PATCH 5/5] docs: unify file extensions

---
 .../en/10-third-party/03-visual/{01-grafana.mdx => 01-grafana.md} | 0
 .../01-components/{12-tdinsight.mdx => 12-tdinsight.md}           | 0
 .../03-taos-sql/{08-delete-data.mdx => 08-delete-data.md}         | 0
 docs/en/14-reference/05-connector/{10-cpp.mdx => 10-cpp.md}       | 0
 docs/en/14-reference/05-connector/{14-java.mdx => 14-java.md}     | 0
 docs/en/14-reference/05-connector/{20-go.mdx => 20-go.md}         | 0
 docs/en/14-reference/05-connector/{26-rust.mdx => 26-rust.md}     | 0
 docs/en/14-reference/05-connector/{30-python.mdx => 30-python.md} | 0
 docs/en/14-reference/05-connector/{35-node.mdx => 35-node.md}     | 0
 docs/en/14-reference/05-connector/{40-csharp.mdx => 40-csharp.md} | 0
 docs/en/14-reference/05-connector/{43-r-lang.mdx => 43-r-lang.md} | 0
 docs/en/14-reference/05-connector/{45-php.mdx => 45-php.md}       | 0
 docs/en/14-reference/05-connector/{50-odbc.mdx => 50-odbc.md}     | 0
 .../14-reference/05-connector/{60-rest-api.mdx => 60-rest-api.md} | 0
 14 files changed, 0 insertions(+), 0 deletions(-)
 rename docs/en/10-third-party/03-visual/{01-grafana.mdx => 01-grafana.md} (100%)
 rename docs/en/14-reference/01-components/{12-tdinsight.mdx => 12-tdinsight.md} (100%)
 rename docs/en/14-reference/03-taos-sql/{08-delete-data.mdx => 08-delete-data.md} (100%)
 rename docs/en/14-reference/05-connector/{10-cpp.mdx => 10-cpp.md} (100%)
 rename docs/en/14-reference/05-connector/{14-java.mdx => 14-java.md} (100%)
 rename docs/en/14-reference/05-connector/{20-go.mdx => 20-go.md} (100%)
 rename docs/en/14-reference/05-connector/{26-rust.mdx => 26-rust.md} (100%)
 rename docs/en/14-reference/05-connector/{30-python.mdx => 30-python.md} (100%)
 rename docs/en/14-reference/05-connector/{35-node.mdx => 35-node.md} (100%)
 rename docs/en/14-reference/05-connector/{40-csharp.mdx => 40-csharp.md} (100%)
 rename docs/en/14-reference/05-connector/{43-r-lang.mdx => 43-r-lang.md} (100%)
 rename docs/en/14-reference/05-connector/{45-php.mdx => 45-php.md} (100%)
 rename docs/en/14-reference/05-connector/{50-odbc.mdx => 50-odbc.md} (100%)
 rename docs/en/14-reference/05-connector/{60-rest-api.mdx => 60-rest-api.md} (100%)

diff --git a/docs/en/10-third-party/03-visual/01-grafana.mdx b/docs/en/10-third-party/03-visual/01-grafana.md
similarity index 100%
rename from docs/en/10-third-party/03-visual/01-grafana.mdx
rename to docs/en/10-third-party/03-visual/01-grafana.md
diff --git a/docs/en/14-reference/01-components/12-tdinsight.mdx b/docs/en/14-reference/01-components/12-tdinsight.md
similarity index 100%
rename from docs/en/14-reference/01-components/12-tdinsight.mdx
rename to docs/en/14-reference/01-components/12-tdinsight.md
diff --git a/docs/en/14-reference/03-taos-sql/08-delete-data.mdx b/docs/en/14-reference/03-taos-sql/08-delete-data.md
similarity index 100%
rename from docs/en/14-reference/03-taos-sql/08-delete-data.mdx
rename to docs/en/14-reference/03-taos-sql/08-delete-data.md
diff --git a/docs/en/14-reference/05-connector/10-cpp.mdx b/docs/en/14-reference/05-connector/10-cpp.md
similarity index 100%
rename from docs/en/14-reference/05-connector/10-cpp.mdx
rename to docs/en/14-reference/05-connector/10-cpp.md
diff --git a/docs/en/14-reference/05-connector/14-java.mdx b/docs/en/14-reference/05-connector/14-java.md
similarity index 100%
rename from docs/en/14-reference/05-connector/14-java.mdx
rename to docs/en/14-reference/05-connector/14-java.md
diff --git a/docs/en/14-reference/05-connector/20-go.mdx b/docs/en/14-reference/05-connector/20-go.md
similarity index 100%
rename from docs/en/14-reference/05-connector/20-go.mdx
rename to docs/en/14-reference/05-connector/20-go.md
diff --git a/docs/en/14-reference/05-connector/26-rust.mdx b/docs/en/14-reference/05-connector/26-rust.md
similarity index 100%
rename from docs/en/14-reference/05-connector/26-rust.mdx
rename to docs/en/14-reference/05-connector/26-rust.md
diff --git a/docs/en/14-reference/05-connector/30-python.mdx b/docs/en/14-reference/05-connector/30-python.md
similarity index 100%
rename from docs/en/14-reference/05-connector/30-python.mdx
rename to docs/en/14-reference/05-connector/30-python.md
diff --git a/docs/en/14-reference/05-connector/35-node.mdx b/docs/en/14-reference/05-connector/35-node.md
similarity index 100%
rename from docs/en/14-reference/05-connector/35-node.mdx
rename to docs/en/14-reference/05-connector/35-node.md
diff --git a/docs/en/14-reference/05-connector/40-csharp.mdx b/docs/en/14-reference/05-connector/40-csharp.md
similarity index 100%
rename from docs/en/14-reference/05-connector/40-csharp.mdx
rename to docs/en/14-reference/05-connector/40-csharp.md
diff --git a/docs/en/14-reference/05-connector/43-r-lang.mdx b/docs/en/14-reference/05-connector/43-r-lang.md
similarity index 100%
rename from docs/en/14-reference/05-connector/43-r-lang.mdx
rename to docs/en/14-reference/05-connector/43-r-lang.md
diff --git a/docs/en/14-reference/05-connector/45-php.mdx b/docs/en/14-reference/05-connector/45-php.md
similarity index 100%
rename from docs/en/14-reference/05-connector/45-php.mdx
rename to docs/en/14-reference/05-connector/45-php.md
diff --git a/docs/en/14-reference/05-connector/50-odbc.mdx b/docs/en/14-reference/05-connector/50-odbc.md
similarity index 100%
rename from docs/en/14-reference/05-connector/50-odbc.mdx
rename to docs/en/14-reference/05-connector/50-odbc.md
diff --git a/docs/en/14-reference/05-connector/60-rest-api.mdx b/docs/en/14-reference/05-connector/60-rest-api.md
similarity index 100%
rename from docs/en/14-reference/05-connector/60-rest-api.mdx
rename to docs/en/14-reference/05-connector/60-rest-api.md