diff --git a/faq/monitor-faq.md b/faq/monitor-faq.md
index 5cfa36a2781cf..8b015916823d8 100644
--- a/faq/monitor-faq.md
+++ b/faq/monitor-faq.md
@@ -18,7 +18,7 @@ The monitoring system of TiDB consists of Prometheus and Grafana. From the dashb
 
 Yes. Find the startup script on the machine where Prometheus is started, edit the startup parameter and restart Prometheus.
 
-```config
+```
 --storage.tsdb.retention="60d"
 ```
 
diff --git a/information-schema/information-schema-slow-query.md b/information-schema/information-schema-slow-query.md
index 0dc2c9dc6f3b8..3fdfd89edcd08 100644
--- a/information-schema/information-schema-slow-query.md
+++ b/information-schema/information-schema-slow-query.md
@@ -24,7 +24,7 @@ DESC SLOW_QUERY;
 
 The output is as follows:
 
-```sqlsql
+```
 +-------------------------------+---------------------+------+------+---------+-------+
 | Field                         | Type                | Null | Key  | Default | Extra |
 +-------------------------------+---------------------+------+------+---------+-------+
diff --git a/sql-statements/sql-statement-set-password.md b/sql-statements/sql-statement-set-password.md
index 069aff17737e7..2d3ae1e3b6e2e 100644
--- a/sql-statements/sql-statement-set-password.md
+++ b/sql-statements/sql-statement-set-password.md
@@ -10,7 +10,7 @@ This statement changes the user password for a user account in the TiDB system d
 
 ## Synopsis
 
-```enbf+diagram
+```ebnf+diagram
 SetPasswordStmt ::=
     "SET" "PASSWORD" ( "FOR" Username )? "=" ( stringLit | "PASSWORD" "(" stringLit ")" )
 ```
diff --git a/sql-statements/sql-statement-show-engines.md b/sql-statements/sql-statement-show-engines.md
index 4fc855e8de9dd..19ea33560cecb 100644
--- a/sql-statements/sql-statement-show-engines.md
+++ b/sql-statements/sql-statement-show-engines.md
@@ -10,7 +10,7 @@ This statement is used to list all supported storage engines. The syntax is incl
 
 ## Synopsis
 
-```enbf+diagram
+```ebnf+diagram
 ShowEnginesStmt ::=
     "SHOW" "ENGINES" ShowLikeOrWhere?
 
diff --git a/sync-diff-inspector/sync-diff-inspector-overview.md b/sync-diff-inspector/sync-diff-inspector-overview.md
index 56a2dd8937f37..22cf71b76a7c2 100644
--- a/sync-diff-inspector/sync-diff-inspector-overview.md
+++ b/sync-diff-inspector/sync-diff-inspector-overview.md
@@ -182,7 +182,7 @@ sync-diff-inspector sends progress information to `stdout` when running. Progres
 >
 > To ensure the display effect, keep the display window width above 80 characters.
 
-```progress
+```
 A total of 2 tables need to be compared
 
 Comparing the table structure of ``sbtest`.`sbtest96`` ... equivalent
@@ -193,7 +193,7 @@ _____________________________________________________________________________
 Progress [==========================================================>--] 98% 193/200
 ```
 
-```progress
+```
 A total of 2 tables need to be compared
 
 Comparing the table structure of ``sbtest`.`sbtest96`` ... equivalent
@@ -245,7 +245,7 @@ The running sync-diff-inspector periodically (every 10 seconds) prints the progr
 
 After the check is finished, sync-diff-inspector outputs a report. It is located at `${output}/summary.txt`, and `${output}` is the value of `output-dir` in the `config.toml` file.
 
-```summary
+```
 +---------------------+--------------------+----------------+---------+-----------+
 |        TABLE        | STRUCTURE EQUALITY | DATA DIFF ROWS | UPCOUNT | DOWNCOUNT |
 +---------------------+--------------------+----------------+---------+-----------+
diff --git a/tidb-cloud/migrate-from-op-tidb.md b/tidb-cloud/migrate-from-op-tidb.md
index a3bc2a058203d..ce2f4f685e13e 100644
--- a/tidb-cloud/migrate-from-op-tidb.md
+++ b/tidb-cloud/migrate-from-op-tidb.md
@@ -172,7 +172,7 @@ Do the following to export data from the upstream TiDB cluster to Amazon S3 usin
 
 3. Run Dumpling to export data to the Amazon S3 bucket.
 
-    ```ymal
+    ```shell
     dumpling \
     -u root \
     -P 4000 \
diff --git a/tidb-troubleshooting-map.md b/tidb-troubleshooting-map.md
index 8b88e375925ed..74e7ac6e51631 100644
--- a/tidb-troubleshooting-map.md
+++ b/tidb-troubleshooting-map.md
@@ -416,7 +416,7 @@ Check the specific cause for busy by viewing the monitor **Grafana** -> **TiKV**
 
     - The binlog data is too large, so the single message written to Kafka is too large. You need to modify the following configuration of Kafka:
 
-        ```conf
+        ```properties
         message.max.bytes=1073741824
         replica.fetch.max.bytes=1073741824
         fetch.message.max.bytes=1073741824