docs: update docs for docusaurus 3.0

docs/en/07-develop/03-insert-data/50-opentsdb-json.mdx

@@ -101,7 +101,7 @@ Query OK, 2 row(s) in set (0.004076s)
 
 ## Query Examples
 
-If you want query the data of "tags": {"location": "California.LosAngeles", "groupid": 1}, here is the query SQL:
+If you want query the data of "tags": {"location": "California.LosAngeles", "groupid": 1}, here is the query SQL:
 
 ```sql
 SELECT * FROM `meters_current` WHERE location = "California.LosAngeles" AND groupid = 3;

docs/en/07-develop/04-query-data/index.mdx

@@ -22,7 +22,7 @@ import CAsync from "./_c_async.mdx";
 SQL is used by TDengine as its query language. Application programs can send SQL statements to TDengine through REST API or client libraries. TDengine's CLI `taos` can also be used to execute ad hoc SQL queries. Here is the list of major query functionalities supported by TDengine:
 
 - Query on single column or multiple columns
-- Filter on tags or data columns: >, <, =, <\>, like
+- Filter on tags or data columns: &gt;, &lt;, =, &lt;&gt;, like
 - Grouping of results: `Group By` - Sorting of results: `Order By` - Limit the number of results: `Limit/Offset`
 - Windowed aggregate queries for time windows (interval), session windows (session), and state windows (state_window) 
 - Arithmetic on columns of numeric types or aggregate results
@@ -159,7 +159,7 @@ In the section describing [Insert](../insert-data/sql-writing), a database named
 :::note
 
 1. With either REST connection or native connection, the above sample code works well.
-2. Please note that `use db` can't be used in case of REST connection because it's stateless. You can specify the database name by either the REST endpoint's parameter or <db_name>.<table_name> in the SQL command.
+2. Please note that `use db` can't be used in case of REST connection because it's stateless. You can specify the database name by either the REST endpoint's parameter or &lt;db_name&gt;.&lt;table_name&gt; in the SQL command.
 
 :::
 

docs/en/07-develop/09-udf.md

@@ -104,7 +104,7 @@ Replace `aggfn` with the name of your function.
 
 ### UDF Interface Definition in C
 
-There are strict naming conventions for interface functions. The names of the start, finish, init, and destroy interfaces must be <udf-name\>_start, <udf-name\>_finish, <udf-name\>_init, and <udf-name\>_destroy, respectively. Replace `scalarfn`, `aggfn`, and `udf` with the name of your user-defined function.
+There are strict naming conventions for interface functions. The names of the start, finish, init, and destroy interfaces must be &lt;udf-name&gt;_start, &lt;udf-name&gt;_finish, &lt;udf-name&gt;_init, and &lt;udf-name&gt;_destroy, respectively. Replace `scalarfn`, `aggfn`, and `udf` with the name of your user-defined function.
 
 Interface functions return a value that indicates whether the operation was successful. If an operation fails, the interface function returns an error code. Otherwise, it returns TSDB_CODE_SUCCESS. The error codes are defined in `taoserror.h` and in the common API error codes in `taos.h`. For example, TSDB_CODE_UDF_INVALID_INPUT indicates invalid input. TSDB_CODE_OUT_OF_MEMORY indicates insufficient memory.
 
@@ -194,7 +194,7 @@ typedef struct SUdfInterBuf {
 ```
 The data structure is described as follows:
 
-- The SUdfDataBlock block includes the number of rows (numOfRows) and the number of columns (numCols). udfCols[i] (0 <= i <= numCols-1) indicates that each column is of type SUdfColumn.
+- The SUdfDataBlock block includes the number of rows (numOfRows) and the number of columns (numCols). udfCols[i] (0 &lt;= i &lt;= numCols-1) indicates that each column is of type SUdfColumn.
 - SUdfColumn includes the definition of the data type of the column (colMeta) and the data in the column (colData).
 - The member definitions of SUdfColumnMeta are the same as the data type definitions in `taos.h`.
 - The data in SUdfColumnData can become longer. varLenCol indicates variable-length data, and fixLenCol indicates fixed-length data.

docs/en/08-client-libraries/03-cpp.mdx

@@ -186,7 +186,7 @@ The base API is used to do things like create database connections and provide a
 
   - The variables database and len are applied by the user outside and allocated space. The current database name and length will be assigned to database and len.
   - As long as the db name is not assigned to the database normally (including truncation), an error will be returned with the return value of -1, and then the user can use taos_errstr(NULL) to get error message.
-  - If database==NULL or len<=0, returns an error, the space required to store the db (including the last '\0') in the variable required
+  - If database==NULL or len&lt;=0, returns an error, the space required to store the db (including the last '\0') in the variable required
   - If len is less than the space required to store the db (including the last '\0'), an error is returned. The truncated data assigned in the database ends with '\0'.
   - If len is greater than or equal to the space required to store the db (including the last '\0'), return normal 0, and assign the db name ending with '\0' in the database.
 

docs/en/08-client-libraries/06-rust.mdx

@@ -69,7 +69,7 @@ TDengine currently supports timestamp, number, character, Boolean type, and the
 | SMALLINT          | i16               |
 | TINYINT           | i8                |
 | BOOL              | bool              |
-| BINARY            | Vec<u8\>          |
+| BINARY            | Vec&lt;u8&gt;     |
 | NCHAR             | String            |
 | JSON              | serde_json::Value |
 

docs/en/08-client-libraries/07-python.mdx

@@ -315,7 +315,7 @@ The `connect()` function returns a `taos.TaosConnection` instance. In client-sid
 
 All arguments to the `connect()` function are optional keyword arguments. The following are the connection parameters specified.
 
-- `url`: The URL of taosAdapter REST service. The default is <http://localhost:6041>.
+- `url`: The URL of taosAdapter REST service. The default is `http://localhost:6041`.
 - `user`: TDengine user name. The default is `root`.
 - `password`: TDengine user password. The default is `taosdata`.
 - `timeout`: HTTP request timeout. Enter a value in seconds. The default is `socket._GLOBAL_DEFAULT_TIMEOUT`. Usually, no configuration is needed.

docs/en/08-client-libraries/80-php.mdx

@@ -8,7 +8,7 @@ description: This document describes the TDengine PHP client library.
 
 PHP client library relies on TDengine client driver.
 
-Project Repository: <https://github.com/Yurunsoft/php-tdengine>
+Project Repository: [https://github.com/Yurunsoft/php-tdengine](https://github.com/Yurunsoft/php-tdengine)
 
 After TDengine client or server is installed, `taos.h` is located at:
 

docs/en/12-taos-sql/01-data-type.md

@@ -68,14 +68,14 @@ TDengine supports a variety of constants:
 
 | #   |                    **Syntax**                     | **Type**  | **Description**                                                                                                                                                                                                   |
 | --- | :-----------------------------------------------: | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 1   |                   [{+ \| -}]123                   | BIGINT    | Integer literals are of type BIGINT. Data that exceeds the length of the BIGINT type is truncated.                                                                                                                |
+| 1   |                   [+ \| -]123                   | BIGINT    | Integer literals are of type BIGINT. Data that exceeds the length of the BIGINT type is truncated.                                                                                                                |
 | 2   |                      123.45                       | DOUBLE    | Floating-point literals are of type DOUBLE. Numeric values will be determined as integer or float type according to whether there is decimal point or whether scientific notation is used.                        |
 | 3   |                       1.2E3                       | DOUBLE    | Literals in scientific notation are of type DOUBLE.                                                                                                                                                               |
 | 4   |                       'abc'                       | BINARY    | Content enclosed in single quotation marks is of type BINARY. The size of a BINARY is the size of the string in bytes. A literal single quote inside the string must be escaped with a backslash `\'`.            |
 | 5   |                       'abc'                       | BINARY    | Content enclosed in double quotation marks is of type BINARY. The size of a BINARY is the size of the string in bytes. A literal double quote inside the string must be escaped with a backslash `\"`.            |
-| 6   |        TIMESTAMP {'literal' \| "literal"}         | TIMESTAMP | The TIMESTAMP keyword indicates that the following string literal is interpreted as a timestamp. The string must be in YYYY-MM-DD HH:mm:ss.MS format. The precision is inherited from the database configuration. |
+| 6   |        TIMESTAMP ['literal' \| "literal"]         | TIMESTAMP | The TIMESTAMP keyword indicates that the following string literal is interpreted as a timestamp. The string must be in YYYY-MM-DD HH:mm:ss.MS format. The precision is inherited from the database configuration. |
-| 7   |                  {TRUE \| FALSE}                  | BOOL      | Boolean literals are of type BOOL.                                                                                                                                                                                |
+| 7   |                  [TRUE \| FALSE]                  | BOOL      | Boolean literals are of type BOOL.                                                                                                                                                                                |
-| 8   | {'' \| "" \| '\t' \| "\t" \| ' ' \| " " \| NULL } | --        | The preceding characters indicate null literals. These can be used with any data type.                                                                                                                            |
+| 8   | ['' \| "" \| '\t' \| "\t" \| ' ' \| " " \| NULL ] | --        | The preceding characters indicate null literals. These can be used with any data type.                                                                                                                            |
 
 :::note
 Numeric values will be determined as integer or float type according to whether there is decimal point or whether scientific notation is used, so attention must be paid to avoid overflow. For example, 9999999999999999999 will be considered as overflow because it exceeds the upper limit of long integer, but 9999999999999999999.0 will be considered as a legal float number.

docs/en/12-taos-sql/02-database.md

@@ -56,7 +56,7 @@ database_option: {
 - WAL_FSYNC_PERIOD: specifies the interval (in milliseconds) at which data is written from the WAL to disk. This parameter takes effect only when the WAL parameter is set to 2. The default value is 3000. Enter a value between 0 and 180000. The value 0 indicates that incoming data is immediately written to disk.
 - MAXROWS: specifies the maximum number of rows recorded in a block. The default value is 4096.
 - MINROWS: specifies the minimum number of rows recorded in a block. The default value is 100.
-- KEEP: specifies the time for which data is retained. Enter a value between 1 and 365000. The default value is 3650. The value of the KEEP parameter must be greater than or equal to three times of the value of the DURATION parameter. TDengine automatically deletes data that is older than the value of the KEEP parameter. You can use m (minutes), h (hours), and d (days) as the unit, for example KEEP 100h or KEEP 10d. If you do not include a unit, d is used by default. TDengine Enterprise supports [Tiered Storage](https://docs.tdengine.com/tdinternal/arch/#tiered-storage) function, thus multiple KEEP values (comma separated and up to 3 values supported, and meet keep 0 <= keep 1 <= keep 2, e.g. KEEP 100h,100d,3650d) are supported; TDengine OSS does not support Tiered Storage function (although multiple keep values are configured, they do not take effect, only the maximum keep value is used as KEEP).
+- KEEP: specifies the time for which data is retained. Enter a value between 1 and 365000. The default value is 3650. The value of the KEEP parameter must be greater than or equal to three times of the value of the DURATION parameter. TDengine automatically deletes data that is older than the value of the KEEP parameter. You can use m (minutes), h (hours), and d (days) as the unit, for example KEEP 100h or KEEP 10d. If you do not include a unit, d is used by default. TDengine Enterprise supports [Tiered Storage](https://docs.tdengine.com/tdinternal/arch/#tiered-storage) function, thus multiple KEEP values (comma separated and up to 3 values supported, and meet keep 0 &lt;= keep 1 &lt;= keep 2, e.g. KEEP 100h,100d,3650d) are supported; TDengine OSS does not support Tiered Storage function (although multiple keep values are configured, they do not take effect, only the maximum keep value is used as KEEP).
 - PAGES: specifies the number of pages in the metadata storage engine cache on each vnode. Enter a value greater than or equal to 64. The default value is 256. The space occupied by metadata storage on each vnode is equal to the product of the values of the PAGESIZE and PAGES parameters. The space occupied by default is 1 MB.
 - PAGESIZE: specifies the size (in KB) of each page in the metadata storage engine cache on each vnode. The default value is 4. Enter a value between 1 and 16384.
 - PRECISION: specifies the precision at which a database records timestamps. Enter ms for milliseconds, us for microseconds, or ns for nanoseconds. The default value is ms.

docs/en/12-taos-sql/10-function.md

@@ -877,11 +877,11 @@ HISTOGRAM(expr, bin_type, bin_description, normalized)
     - "user_input": "[1, 3, 5, 7]":
        User specified bin values.
 
-    - "linear_bin": "{"start": 0.0, "width": 5.0, "count": 5, "infinity": true}"
+    - "linear_bin": "{"start": 0.0, "width": 5.0, "count": 5, "infinity": true}"
        "start" - bin starting point.       "width" - bin offset.       "count" - number of bins generated.       "infinity" - whether to add (-inf, inf) as start/end point in generated set of bins.
        The above "linear_bin" descriptor generates a set of bins: [-inf, 0.0, 5.0, 10.0, 15.0, 20.0, +inf].
 
-    - "log_bin": "{"start":1.0, "factor": 2.0, "count": 5, "infinity": true}"
+    - "log_bin": "{"start":1.0, "factor": 2.0, "count": 5, "infinity": true}"
        "start" - bin starting point.       "factor" - exponential factor of bin offset.       "count" - number of bins generated.       "infinity" - whether to add (-inf, inf) as start/end point in generated range of bins.
        The above "linear_bin" descriptor generates a set of bins: [-inf, 1.0, 2.0, 4.0, 8.0, 16.0, +inf].
 - normalized: setting to 1/0 to turn on/off result normalization. Valid values are 0 or 1.
@@ -977,7 +977,7 @@ ignore_null_values: {
 - `INTERP` is used to get the value that matches the specified time slice from a column. If no such value exists an interpolation value will be returned based on `FILL` parameter.
 - The input data of `INTERP` is the value of the specified column and a `where` clause can be used to filter the original data. If no `where` condition is specified then all original data is the input.
 - `INTERP` must be used along with `RANGE`, `EVERY`, `FILL` keywords.
-- The output time range of `INTERP` is specified by `RANGE(timestamp1,timestamp2)` parameter, with timestamp1 <= timestamp2. timestamp1 is the starting point of the output time range. timestamp2 is the ending point of the output time range.
+- The output time range of `INTERP` is specified by `RANGE(timestamp1,timestamp2)` parameter, with timestamp1 &lt;= timestamp2. timestamp1 is the starting point of the output time range. timestamp2 is the ending point of the output time range.
 - The number of rows in the result set of `INTERP` is determined by the parameter `EVERY(time_unit)`. Starting from timestamp1, one interpolation is performed for every time interval specified `time_unit` parameter. The parameter `time_unit` must be an integer, with no quotes, with a time unit of: a(millisecond)), s(second), m(minute), h(hour), d(day), or w(week). For example, `EVERY(500a)` will interpolate every 500 milliseconds.
 - Interpolation is performed based on `FILL` parameter. For more information about FILL clause, see [FILL Clause](../distinguished/#fill-clause).
 - When only one timestamp value is specified in `RANGE` clause, `INTERP` is used to generate interpolation at this point in time. In this case, `EVERY` clause can be omitted. For example, SELECT INTERP(col) FROM tb RANGE('2023-01-01 00:00:00') FILL(linear).

docs/en/12-taos-sql/16-operators.md

@@ -35,9 +35,9 @@ TDengine supports the `UNION` and `UNION ALL` operations. UNION ALL collects all
 | #   | **Operator** | **Supported Data Types** | **Description**                   |
 | --- | :---------------: | -------------------------------------------------------------------- | -------------------- |
 | 1   |         =         | All types except BLOB, MEDIUMBLOB, and JSON                             | Equal to |
-| 2   |      <\>, !=      | All types except BLOB, MEDIUMBLOB, and JSON; the primary key (timestamp) is also not supported | Not equal to               |
+| 2   |      &lt;&gt;, !=      | All types except BLOB, MEDIUMBLOB, and JSON; the primary key (timestamp) is also not supported | Not equal to               |
-| 3   |      \>, <       | All types except BLOB, MEDIUMBLOB, and JSON                             | Greater than and less than           |
+| 3   |      &gt;, &lt;       | All types except BLOB, MEDIUMBLOB, and JSON                             | Greater than and less than           |
-| 4   |     \>=, <=      | All types except BLOB, MEDIUMBLOB, and JSON                             | Greater than or equal to and less than or equal to   |
+| 4   |     &gt;=, &lt;=      | All types except BLOB, MEDIUMBLOB, and JSON                             | Greater than or equal to and less than or equal to   |
 | 5   |   IS [NOT] NULL   | All types                                                             | Indicates whether the value is null           |
 | 6   | [NOT] BETWEEN AND | All types except BLOB, MEDIUMBLOB, JSON and GEOMETRY                  | Closed interval comparison           |
 | 7   |        IN         | All types except BLOB, MEDIUMBLOB, and JSON; the primary key (timestamp) is also not supported | Equal to any value in the list |

docs/en/12-taos-sql/29-changes.md

@@ -71,7 +71,7 @@ The following data types can be used in the schema for standard tables.
 | 44 | SHOW STREAMS	| Modified | This statement previously showed continuous queries. The continuous query feature has been replaced with the stream processing feature. This statement now shows streams that have been created.
 | 45 | SHOW SUBSCRIPTIONS | Added | Shows all subscriptions in the current database.
 | 46 | SHOW TABLES | Modified | Only shows table names.
-| 47 | SHOW TABLE DISTRIBUTED | Added | Shows how table data is distributed. This replaces the `SELECT _block_dist() FROM { tb_name | stb_name }` command.
+| 47 | SHOW TABLE DISTRIBUTED | Added | Shows how table data is distributed. This replaces the `SELECT _block_dist() FROM { tb_name | stb_name }` command.
 | 48 | SHOW TOPICS | Added | Shows all subscribed topics in the current database.
 | 49 | SHOW TRANSACTIONS | Added | Shows all running transactions in the system.
 | 50 | SHOW DNODE VARIABLES | Added | Shows the configuration of the specified dnode.

docs/en/13-operation/17-diagnose.md

@@ -15,7 +15,7 @@ Diagnostic steps:
 2. On the server side, execute command `taos -n server -P <port> -l <pktlen>` to monitor the port range starting from the port specified by `-P` parameter with the role of "server".
 3. On the client side, execute command `taos -n client -h <fqdn of server> -P <port> -l <pktlen>` to send a testing package to the specified server and port.
 
--l <pktlen\>: The size of the testing package, in bytes. The value range is [11, 64,000] and default value is 1,000.
+-l &lt;pktlen&gt;: The size of the testing package, in bytes. The value range is [11, 64,000] and default value is 1,000.
 Please note that the package length must be same in the above 2 commands executed on server side and client side respectively.
 
 Output of the server side for the example is below:
@@ -63,7 +63,7 @@ Once this parameter is set to 135 or 143, the log file grows very quickly especi
 
 ## Client Log
 
-An independent log file, named as "taoslog+<seq num\>" is generated for each client program, i.e. a client process. The parameter `debugFlag` is used to control the log level. The default value is 131. For debugging and tracing, it needs to be set to either 135 or 143 respectively.
+An independent log file, named as "taoslog+&lt;seq num&gt;" is generated for each client program, i.e. a client process. The parameter `debugFlag` is used to control the log level. The default value is 131. For debugging and tracing, it needs to be set to either 135 or 143 respectively.
 
 The default value of `debugFlag` is also 131 and only logs at level of INFO/ERROR/WARNING are recorded. As stated above, for debugging and tracing, it needs to be changed to 135 or 143 respectively, so that logs at DEBUG or TRACE level can be recorded.
 

docs/en/14-reference/02-rest-api/02-rest-api.mdx

@@ -81,7 +81,7 @@ Parameter Description:
 
 :::note
 
-URL Encoding. Make sure that parameters are properly encoded. For example, when specifying a timezone you must properly encode special characters. ?tz=Etc/GMT+10 will not work because the <+> plus symbol is recognized as a space in the url. It's best practice to encode all special characters in a parameter. Instead use ?tz=Etc%2FGMT%2B10 for the parameter.
+URL Encoding. Make sure that parameters are properly encoded. For example, when specifying a timezone you must properly encode special characters. ?tz=Etc/GMT+10 will not work because the + plus symbol is recognized as a space in the url. It's best practice to encode all special characters in a parameter. Instead use ?tz=Etc%2FGMT%2B10 for the parameter.
 
 :::
 

docs/en/14-reference/04-taosadapter.md

@@ -166,8 +166,8 @@ See [example/config/taosadapter.toml](https://github.com/taosdata/taosadapter/bl
 - Compatible with InfluxDB v1 write interface
   [https://docs.influxdata.com/influxdb/v2.0/reference/api/influxdb-1x/write/](https://docs.influxdata.com/influxdb/v2.0/reference/api/influxdb-1x/write/)
 - Compatible with OpenTSDB JSON and telnet format writes
-  - <http://opentsdb.net/docs/build/html/api_http/put.html>
+  - [http://opentsdb.net/docs/build/html/api_http/put.html](http://opentsdb.net/docs/build/html/api_http/put.html)
-  - <http://opentsdb.net/docs/build/html/api_telnet/put.html>
+  - [http://opentsdb.net/docs/build/html/api_telnet/put.html](http://opentsdb.net/docs/build/html/api_telnet/put.html)
 - Seamless connection to collectd
   collectd is a system statistics collection daemon, please visit [https://collectd.org/](https://collectd.org/) for more information.
 - Seamless connection with StatsD

docs/en/14-reference/05-taosbenchmark.md

@@ -94,67 +94,67 @@ taosBenchmark -f <json file>
 
 ## Command-line argument in detail
 
-- **-f/--file <json file\>** :
+- **-f/--file &lt;json file&gt;** :
   specify the configuration file to use. This file includes All parameters. Users should not use this parameter with other parameters on the command-line. There is no default value.
 
-- **-c/--config-dir <dir\>** :
+- **-c/--config-dir &lt;dir&gt;** :
   specify the directory where the TDengine cluster configuration file. The default path is `/etc/taos`.
 
-- **-h/--host <host\>** :
+- **-h/--host &lt;host&gt;** :
   Specify the FQDN of the TDengine server to connect to. The default value is localhost.
 
-- **-P/--port <port\>** :
+- **-P/--port &lt;port&gt;** :
   The port number of the TDengine server to connect to, the default value is 6030.
 
-- **-I/--interface <insertMode\>** :
+- **-I/--interface &lt;insertMode&gt;** :
   Insert mode. Options are taosc, rest, stmt, sml, sml-rest, corresponding to normal write, restful interface writing, parameter binding interface writing, schemaless interface writing, RESTful schemaless interface writing (provided by taosAdapter). The default value is taosc.
 
-- **-u/--user <user\>** :
+- **-u/--user &lt;user&gt;** :
   User name to connect to the TDengine server. Default is root.
 
 - **-U/--supplement-insert ** :
   Supplementally insert data without create database and table, optional, default is off.
 
-- **-p/--password <passwd\>** :
+- **-p/--password &lt;passwd&gt;** :
   The default password to connect to the TDengine server is `taosdata`.
 
-- **-o/--output <file\>** :
+- **-o/--output &lt;file&gt;** :
   specify the path of the result output file, the default value is `. /output.txt`.
 
-- **-T/--thread <threadNum\>** :
+- **-T/--thread &lt;threadNum&gt;** :
   The number of threads to insert data. Default is 8.
 
-- **-B/--interlace-rows <rowNum\>** :
+- **-B/--interlace-rows &lt;rowNum&gt;** :
   Enables interleaved insertion mode and specifies the number of rows of data to be inserted into each child table. Interleaved insertion mode means inserting the number of rows specified by this parameter into each sub-table and repeating the process until all sub-tables have been inserted. The default value is 0, i.e., data is inserted into one sub-table before the next sub-table is inserted.
 
-- **-i/--insert-interval <timeInterval\>** :
+- **-i/--insert-interval &lt;timeInterval&gt;** :
   Specify the insert interval in `ms` for interleaved insert mode. The default value is 0. It only works if `-B/--interlace-rows` is greater than 0. After inserting interlaced rows for each child table, the data insertion thread will wait for the interval specified by this value before proceeding to the next round of writes.
 
-- **-r/--rec-per-req <rowNum\>** :
+- **-r/--rec-per-req &lt;rowNum&gt;** :
   Writing the number of rows of records per request to TDengine, the default value is 30000.
 
-- **-t/--tables <tableNum\>** :
+- **-t/--tables &lt;tableNum&gt;** :
   Specify the number of sub-tables. The default is 10000.
 
-- **-S/--timestampstep <stepLength\>** :
+- **-S/--timestampstep &lt;stepLength&gt;** :
   Timestamp step for inserting data in each child table in ms, default is 1.
 
-- **-n/--records <recordNum\>** :
+- **-n/--records &lt;recordNum&gt;** :
   The default value of the number of records inserted in each sub-table is 10000.
 
-- **-d/--database <dbName\>** :
+- **-d/--database &lt;dbName&gt;** :
   The name of the database used, the default value is `test`.
 
-- **-b/--data-type <colType\>** :
+- **-b/--data-type &lt;colType&gt;** :
   specify the type of the data columns of the super table. It defaults to three columns of type FLOAT, INT, and FLOAT if not used.
 
-- **-l/--columns <colNum\>** :
+- **-l/--columns &lt;colNum&gt;** :
   specify the number of columns in the super table. If both this parameter and `-b/--data-type` is set, the final result number of columns is the greater of the two. If the number specified by this parameter is greater than the number of columns specified by `-b/--data-type`, the unspecified column type defaults to INT, for example: `-l 5 -b float,double`, then the final column is `FLOAT,DOUBLE,INT,INT,INT`. If the number of columns specified is less than or equal to the number of columns specified by `-b/--data-type`, then the result is the column and type specified by `-b/--data-type`, e.g.: `-l 3 -b float,double,float,bigint`. The last column is `FLOAT,DOUBLE, FLOAT,BIGINT`.
 
-- **-L/--partial-col-num <colNum\> ** :
+- **-L/--partial-col-num &lt;colNum&gt; ** :
   Specify first numbers of columns has data. Rest of columns' data are NULL. Default is all columns have data.
 
-- **-A/--tag-type <tagType\>** :
+- **-A/--tag-type &lt;tagType&gt;** :
   The tag column type of the super table. nchar and binary types can both set the length, for example:
 
 ```
@@ -168,10 +168,10 @@ Note: In some shells, such as bash, "()" needs to be escaped, so the above comma
 taosBenchmark -A INT,DOUBLE,NCHAR,BINARY\(16\)
 ```
 
-- **-w/--binwidth <length\>**:
+- **-w/--binwidth &lt;length&gt;**:
   specify the default length for nchar and binary types. The default value is 64.
 
-- **-m/--table-prefix <tablePrefix\>** :
+- **-m/--table-prefix &lt;tablePrefix&gt;** :
   The prefix of the sub-table name, the default value is "d".
 
 - **-E/--escape-character** :
@@ -192,25 +192,25 @@ taosBenchmark -A INT,DOUBLE,NCHAR,BINARY\(16\)
 - **-y/--answer-yes** :
   Switch parameter that requires the user to confirm at the prompt to continue. The default value is false.
 
-- **-O/--disorder <Percentage\>** :
+- **-O/--disorder &lt;Percentage&gt;** :
   Specify the percentage probability of disordered data, with a value range of [0,50]. The default is 0, i.e., there is no disordered data.
 
-- **-R/--disorder-range <timeRange\>** :
+- **-R/--disorder-range &lt;timeRange&gt;** :
   Specify the timestamp range for the disordered data. It leads the resulting disorder timestamp as the ordered timestamp minus a random value in this range. Valid only if the percentage of disordered data specified by `-O/--disorder` is greater than 0.
 
-- **-F/--prepared_rand <Num\>** :
+- **-F/--prepared_rand &lt;Num&gt;** :
   Specify the number of unique values in the generated random data. A value of 1 means that all data are equal. The default value is 10000.
 
-- **-a/--replica <replicaNum\>** :
+- **-a/--replica &lt;replicaNum&gt;** :
   Specify the number of replicas when creating the database. The default value is 1.
 
-- **-k/--keep-trying <NUMBER\>** :
+- **-k/--keep-trying &lt;NUMBER&gt;** :
   Keep trying if failed to insert, default is no. Available with v3.0.9+.
 
-- **-z/--trying-interval <NUMBER\>** :
+- **-z/--trying-interval &lt;NUMBER&;gt;** :
   Specify interval between keep trying insert. Valid value is a positive number. Only valid when keep trying be enabled. Available with v3.0.9+.
 
-- **-v/--vgroups <NUMBER\>** :
+- **-v/--vgroups &lt;NUMBER&gt;** :
   Specify vgroups number for creating a database, only valid with daemon version 3.0+
 
 - **-V/--version** :
@@ -226,7 +226,7 @@ taosBenchmark -A INT,DOUBLE,NCHAR,BINARY\(16\)
 The parameters listed in this section apply to all function modes.
 
 - **filetype** : The function to be tested, with optional values `insert`, `query` and `subscribe`. These correspond to the insert, query, and subscribe functions, respectively. Users can specify only one of these in each configuration file.
-**cfgdir**: specify the TDengine client configuration file's directory. The default path is /etc/taos.
+**cfgdir**: specify the TDengine client configuration file's directory. The default path is `/etc/taos`.
 
 - **host**: Specify the FQDN of the TDengine server to connect. The default value is `localhost`.
 

docs/en/14-reference/12-config/index.md

@@ -289,7 +289,7 @@ A specific type "nchar" is provided in TDengine to store non-ASCII characters su
 
 The characters input on the client side are encoded using the default system encoding, which is UTF-8 on Linux/macOS, or GB18030 or GBK on some systems in Chinese, POSIX in docker, CP936 on Windows in Chinese. The encoding of the operating system in use must be set correctly so that the characters in nchar type can be converted to UCS4-LE.
 
-The locale definition standard on Linux/macOS is: <Language\>\_<Region\>.<charset\>, for example, in "zh_CN.UTF-8", "zh" means Chinese, "CN" means China mainland, "UTF-8" means charset. The charset indicates how to display the characters. On Linux/macOS, the charset can be set by locale in the system. On Windows system another configuration parameter `charset` must be used to configure charset because the locale used on Windows is not POSIX standard. Of course, `charset` can also be used on Linux/macOS to specify the charset.
+The locale definition standard on Linux/macOS is: &lt;Language&gt;\_&lt;Region&gt;.&lt;charset&gt;, for example, in "zh_CN.UTF-8", "zh" means Chinese, "CN" means China mainland, "UTF-8" means charset. The charset indicates how to display the characters. On Linux/macOS, the charset can be set by locale in the system. On Windows system another configuration parameter `charset` must be used to configure charset because the locale used on Windows is not POSIX standard. Of course, `charset` can also be used on Linux/macOS to specify the charset.
 
 :::
 

docs/en/14-reference/_collectd.mdx

@@ -36,7 +36,7 @@ LoadPlugin network
 </Plugin>
 ```
 
-where <taosAdapter's host\> fills in the server's domain name or IP address running taosAdapter. <port for collectd direct\> fills in the port that taosAdapter uses to receive collectd data (default is 6045).
+where &lt;taosAdapter's host&gt; fills in the server's domain name or IP address running taosAdapter. &lt;port for collectd direct&gt; fills in the port that taosAdapter uses to receive collectd data (default is 6045).
 
 An example is as follows.
 
@@ -62,7 +62,7 @@ LoadPlugin write_tsdb
 </Plugin>
 ```
 
-Where <taosAdapter's host\> is the domain name or IP address of the server running taosAdapter. <port for collectd write_tsdb plugin\> Fill in the data that taosAdapter uses to receive the collectd write_tsdb plugin (default is 6047).
+Where &lt;taosAdapter's host&gt; is the domain name or IP address of the server running taosAdapter. &lt;port for collectd write_tsdb plugin&gt; Fill in the data that taosAdapter uses to receive the collectd write_tsdb plugin (default is 6047).
 
 ```text
 LoadPlugin write_tsdb

docs/en/14-reference/_icinga2.mdx

@@ -26,7 +26,7 @@ The default database name written by the taosAdapter is `icinga2`. You can also
 ### Configure icinga3
 
 - Enable opentsdb-writer for icinga2 (refer to the link https://icinga.com/docs/icinga-2/latest/doc/14-features/#opentsdb-writer)
-- Modify the configuration file `/etc/icinga2/features-enabled/opentsdb.conf` by filling in <taosAdapter's host\> as the domain name or IP address of the server running taosAdapter and <port for icinga2\> as the corresponding port on which taosAdapter supports receiving icinga2 data (default is 6048)
+- Modify the configuration file `/etc/icinga2/features-enabled/opentsdb.conf` by filling in &lt;taosAdapter's host&gt; as the domain name or IP address of the server running taosAdapter and &lt;port for icinga2&gt; as the corresponding port on which taosAdapter supports receiving icinga2 data (default is 6048)
 
 ```
 object OpenTsdbWriter "opentsdb" {

docs/en/14-reference/_prometheus.mdx

@@ -9,8 +9,8 @@ Point the `remote_read url` and `remote_write url` to the domain name or IP addr
 
 ### Configure Basic authentication
 
-- username: <TDengine's username>
+- username: TDengine's username
-- password: <TDengine's password>
+- password: TDengine's password
 
 ### Example configuration of remote_write and remote_read related sections in prometheus.yml file
 

docs/en/14-reference/_statsd.mdx

@@ -31,7 +31,7 @@ The default database name written by taosAdapter is `statsd`. To specify a diffe
 
 ### Configuring StatsD
 
-To use StatsD, you need to download its [source code](https://github.com/statsd/statsd). Please refer to the example file `exampleConfig.js` in the root directory of the source download to modify the configuration file. In <taosAdapter's host\>, please fill in the domain name or IP address of the server running taosAdapter, and <port for StatsD\>, please fill in the port where taosAdapter receives StatsD data (default is 6044).
+To use StatsD, you need to download its [source code](https://github.com/statsd/statsd). Please refer to the example file `exampleConfig.js` in the root directory of the source download to modify the configuration file. In &lt;taosAdapter's host&gt;, please fill in the domain name or IP address of the server running taosAdapter, and &lt;port for StatsD&gt;, please fill in the port where taosAdapter receives StatsD data (default is 6044).
 
 ```
 backends section add ". /backends/repeater"

docs/en/14-reference/_telegraf.mdx

@@ -10,7 +10,7 @@ In the Telegraf configuration file (default location `/etc/telegraf/telegraf.con
   ...
 ```
 
-Where <taosAdapter's host\> please fill in the server's domain name or IP address running the taosAdapter service. <REST service port\> please fill in the port of the REST service (default is 6041). <TDengine's username\> and <TDengine's password\> please fill in the actual configuration of the currently running TDengine. And <database name\> please fill in the database name where you want to store Telegraf data in TDengine.
+Where &lt;taosAdapter's host&gt; please fill in the server's domain name or IP address running the taosAdapter service. &lt;REST service port&gt; please fill in the port of the REST service (default is 6041). &lt;TDengine's username&gt; and &lt;TDengine's password&gt; please fill in the actual configuration of the currently running TDengine. And &lt;database name&gt; please fill in the database name where you want to store Telegraf data in TDengine.
 
 An example is as follows.
 

docs/en/20-third-party/01-grafana.mdx

@@ -23,7 +23,7 @@ Record these values:
 
 ## Installing Grafana
 
-TDengine currently supports Grafana versions 7.5 and above. Users can go to the Grafana official website to download the installation package and execute the installation according to the current operating system. The download address is as follows: <https://grafana.com/grafana/download>.
+TDengine currently supports Grafana versions 7.5 and above. Users can go to the Grafana official website to download the installation package and execute the installation according to the current operating system. The download address is as follows: [https://grafana.com/grafana/download](https://grafana.com/grafana/download).
 
 ## Configuring Grafana
 
@@ -59,7 +59,7 @@ bash -c "$(curl -fsSL \
   -p taosdata
 ```
 
-Restart Grafana service and open Grafana in web-browser, usually <http://localhost:3000>.
+Restart Grafana service and open Grafana in web-browser, usually `http://localhost:3000`.
 
 Save the script and type `./install.sh --help` for the full usage of the script.
 
@@ -181,7 +181,7 @@ You can setup a zero-configuration stack for TDengine + Grafana by [docker-compo
 
 3. Start TDengine and Grafana services: `docker-compose up -d`.
 
-Open Grafana <http://localhost:3000>, and you can add dashboard with TDengine now.
+Open Grafana (http://localhost:3000), and you can add dashboard with TDengine now.
 
 </TabItem>
 </Tabs>
@@ -202,7 +202,7 @@ As shown above, select the `TDengine` data source in the `Query` and enter the c
 
 :::note
 
-Since the REST connection because is stateless. Grafana plugin can use <db_name>.<table_name> in the SQL command to specify the database name.
+Since the REST connection because is stateless. Grafana plugin can use &lt;db_name&gt;.&lt;table_name&gt; in the SQL command to specify the database name.
 
 :::
 

docs/en/20-third-party/11-kafka.md

@@ -345,7 +345,7 @@ The following configuration items apply to TDengine Sink Connector and TDengine
 ### TDengine Sink Connector specific configuration
 
 1. `connection.database`: The name of the target database. If the specified database does not exist, it will be created automatically. The time precision used for automatic library building is nanoseconds. The default value is null. When it is NULL, refer to the description of the `connection.database.prefix` parameter for the naming rules of the target database
-2. `connection.database.prefix`: When `connection.database` is null, the prefix of the target database. Can contain placeholder '${topic}'. For example, kafka_${topic}, for topic 'orders' will be written to database 'kafka_orders'. Default null. When null, the name of the target database is the same as the name of the topic.
+2. `connection.database.prefix`: When `connection.database` is null, the prefix of the target database. Can contain placeholder '${topic}'. For example, kafka_${topic}, for topic 'orders' will be written to database 'kafka_orders'. Default null. When null, the name of the target database is the same as the name of the topic.
 3. `batch.size`: Write the number of records in each batch in batches. When the data received by the sink connector at one time is larger than this value, it will be written in some batches.
 4. `max.retries`: The maximum number of retries when an error occurs. Defaults to 1.
 5. `retry.backoff.ms`: The time interval for retry when sending an error. The unit is milliseconds. The default is 3000.
@@ -370,12 +370,12 @@ The following configuration items apply to TDengine Sink Connector and TDengine
 
 ## Other notes
 
-1. To use Kafka Connect, refer to <https://kafka.apache.org/documentation/#connect>.
+1. To use Kafka Connect, refer to [https://kafka.apache.org/documentation/#connect](https://kafka.apache.org/documentation/#connect).
 
 ## Feedback
 
-<https://github.com/taosdata/kafka-connect-tdengine/issues>
+[https://github.com/taosdata/kafka-connect-tdengine/issues](https://github.com/taosdata/kafka-connect-tdengine/issues)
 
 ## Reference
 
-1. For more information, see <https://kafka.apache.org/documentation/>
+1. For more information, see [https://kafka.apache.org/documentation/](https://kafka.apache.org/documentation/).