docs: reference docs in English (#12562)

* docs: reference doc in English

[TD-15603]

* docs: reference docs in English

[TD-15603]

docs-cn/14-reference/13-schemaless/13-schemaless.md

@@ -32,7 +32,7 @@ tag_set 中的所有的数据自动转化为 nchar 数据类型，并不需要
 
 在无模式写入数据行协议中，field_set 中的每个数据项都需要对自身的数据类型进行描述。具体来说：
 
-- 如果两边有英文双引号，表示 BIANRY(32) 类型。例如 `"abc"`。
+- 如果两边有英文双引号，表示 BINARY(32) 类型。例如 `"abc"`。
 - 如果两边有英文双引号而且带有 L 前缀，表示 NCHAR(32) 类型。例如 `L"报错信息"`。
 - 对空格、等号（=）、逗号（,）、双引号（"），前面需要使用反斜杠（\）进行转义。（都指的是英文半角符号）
 - 数值类型将通过后缀来区分数据类型：

docs-en/14-reference/09-support-platform/_category_.yml

-label: 支持平台列表
+label: supported platforms

docs-en/14-reference/09-support-platform/index.md

 ---
-title: 支持平台列表
-description: "TDengine 服务端、客户端和连接器支持的平台列表"
+title: List of supported platforms
+description: "List of platforms supported by TDengine server, client, and connector"
 ---
 
-## TDengine 服务端支持的平台列表
-
-|              | **CentOS 7/8** | **Ubuntu 16/18/20** | **Other Linux** | **统信 UOS** | **银河/中标麒麟** | **凝思 V60/V80** | **华为 EulerOS** |
-| ------------ | -------------- | ------------------- | --------------- | ------------ | ----------------- | ---------------- | ---------------- |
-| X64          | ●              | ●                   |                 | ○            | ●                 | ●                | ●                |
-| 龙芯 MIPS64  |                |                     | ●               |              |                   |                  |                  |
-| 鲲鹏 ARM64   |                | ○                   | ○               |              | ●                 |                  |                  |
-| 申威 Alpha64 |                |                     | ○               | ●            |                   |                  |                  |
-| 飞腾 ARM64   |                | ○ 优麒麟            |                 |              |                   |                  |                  |
-| 海光 X64     | ●              | ●                   | ●               | ○            | ●                 | ●                |                  |
-| 瑞芯微 ARM64 |                |                     | ○               |              |                   |                  |                  |
-| 全志 ARM64   |                |                     | ○               |              |                   |                  |                  |
-| 炬力 ARM64   |                |                     | ○               |              |                   |                  |                  |
-| 华为云 ARM64 |                |                     |                 |              |                   |                  | ●                |
-
-注： ● 表示经过官方测试验证， ○ 表示非官方测试验证。
-
-## TDengine 客户端和连接器支持的平台列表
-
-目前 TDengine 的连接器可支持的平台广泛，目前包括：X64/X86/ARM64/ARM32/MIPS/Alpha 等硬件平台，以及 Linux/Win64/Win32 等开发环境。
-
-对照矩阵如下：
-
-| **CPU**     | **X64 64bit** |           |           | **X86 32bit** | **ARM64** | **ARM32** | **MIPS 龙芯** | **Alpha 申威** | **X64 海光** |
-| ----------- | ------------- | --------- | --------- | ------------- | --------- | --------- | ------------- | -------------- | ------------ |
-| **OS**      | **Linux**     | **Win64** | **Win32** | **Win32**     | **Linux** | **Linux** | **Linux**     | **Linux**      | **Linux**    |
-| **C/C++**   | ●             | ●         | ●         | ○             | ●         | ●         | ●             | ●              | ●            |
-| **JDBC**    | ●             | ●         | ●         | ○             | ●         | ●         | ●             | ●              | ●            |
-| **Python**  | ●             | ●         | ●         | ○             | ●         | ●         | ●             | --             | ●            |
-| **Go**      | ●             | ●         | ●         | ○             | ●         | ●         | ○             | --             | --           |
-| **NodeJs**  | ●             | ●         | ○         | ○             | ●         | ●         | ○             | --             | --           |
-| **C#**      | ●             | ●         | ○         | ○             | ○         | ○         | ○             | --             | --           |
-| **RESTful** | ●             | ●         | ●         | ●             | ●         | ●         | ●             | ●              | ●            |
-
-注：● 表示官方测试验证通过，○ 表示非官方测试验证通过，-- 表示未经验证。
+## List of supported platforms for TDengine server
+
+|              | **CentOS 7/8** | **Ubuntu 16/18/20** | **Other Linux** |
+| ------------ | -------------- | ------------------- | --------------- |
+| X64          | ●              | ●                   |                 |
+| MIPS64       |                |                     | ●               |
+| ARM64        |                | ○                   | ○               |
+| Alpha64      |                |                     | ○               |
+
+Note: ● means officially tested and verified, ○ means unofficially tested and verified.
+
+## List of supported platforms for TDengine clients and connectors
+
+TDengine's connector can support a wide range of platforms, including X64/X86/ARM64/ARM32/MIPS/Alpha hardware platforms and Linux/Win64/Win32 development environments.
+
+The comparison matrix is as follows.
+
+| **CPU**     | **X64 64bit** |           |           | **X86 32bit** | **ARM64** | **ARM32** | **MIPS**  | **Alpha** |
+| ----------- | ------------- | --------- | --------- | ------------- | --------- | --------- | --------- | --------- |
+| **OS**      | **Linux**     | **Win64** | **Win32** | **Win32**     | **Linux** | **Linux** | **Linux** | **Linux** |
+| **C/C++**   | ●             | ●         | ●         | ○             | ●         | ●         | ●         | ●         |
+| **JDBC**    | ●             | ●         | ●         | ○             | ●         | ●         | ●         | ●         |
+| **Python**  | ●             | ●         | ●         | ○             | ●         | ●         | ●         | --        |
+| **Go**      | ●             | ●         | ●         | ○             | ●         | ●         | ○         | --        |
+| **NodeJs**  | ●             | ●         | ○         | ○             | ●         | ●         | ○         | --        |
+| **C#**      | ●             | ●         | ○         | ○             | ○         | ○         | ○         | --        |
+| **RESTful** | ●             | ●         | ●         | ●             | ●         | ●         | ●         | ●         |
+
+Note: ● means the official test is verified, ○ means the unofficial test is verified, -- means not verified.

docs-en/14-reference/11-docker/_category_.yml

-label: TDengine Docker 镜像
\ No newline at end of file
+label: TDengine Docker images
\ No newline at end of file

docs-en/14-reference/11-docker/index.md

 ---
-title: 用 Docker 部署 TDengine
-description: "本章主要介绍如何在容器中启动 TDengine 服务并访问它"
+title: Deploying TDengine with Docker
+Description: "This chapter focuses on starting the TDengine service in a container and accessing it."
 ---
 
-本章主要介绍如何在容器中启动 TDengine 服务并访问它。可以在 docker run 命令行中或者 docker-compose 文件中使用环境变量来控制容器中服务的行为。
+This chapter describes how to start the TDengine service in a container and access it. Users can control the behavior of the service in the container by using environment variables on the docker run command line or in the docker-compose file.
 
-## 启动 TDengine
+## Starting TDengine
 
-TDengine 镜像启动时默认激活 HTTP 服务，使用下列命令
+The TDengine image starts with the HTTP service activated by default, using the following command:
 
 ```shell
 docker run -d --name tdengine -p 6041:6041 tdengine/tdengine
 ```
 
-以上命令启动了一个名为“tdengine”的容器，并把其中的 HTTP 服务的端 6041 映射到了主机端口 6041。使用如下命令可以验证该容器中提供的 HTTP 服务是否可用：
+The above command starts a container named "tdengine" and maps the HTTP service end 6041 to the host port 6041. You can verify that the HTTP service provided in this container is available using the following command.
 
 ```shell
 curl -u root:taosdata -d "show databases" localhost:6041/rest/sql
 ```
 
-使用如下命令可以在该容器中执行 TDengine 的客户端 taos 对 TDengine 进行访问：
+The TDengine client taos can be executed in this container to access TDengine using the following command.
 
 ```shell
 $ docker exec -it tdengine taos
 
 Welcome to the TDengine shell from Linux, Client Version:2.4.0.0
-Copyright (c) 2020 by TAOS Data, Inc. All rights reserved.
+Copyright (c) 2020 by TAOS Data, Inc.
 
 taos> show databases;
-              name              |      created_time       |   ntables   |   vgroups   | replica | quorum |  days  |           keep           |  cache(MB)  |   blocks    |   minrows   |   maxrows   | wallevel |    fsync    | comp | cachelast | precision | update |   status   |
-====================================================================================================================================================================================================================================================================================
- log                            | 2022-01-17 13:57:22.270 |          10 |           1 |       1 |      1 |     10 | 30                       |           1 |           3 |         100 |        4096 |        1 |        3000 |    2 |         0 | us        |      0 | ready      |
+              name | created_time | ntables | vgroups | replica | quorum | days | keep | cache(MB) | blocks | minrows | maxrows | wallevel | fsync | comp | cachelast | precision | update | status | status precision | update | status |
+================================================================================================================================== ================================================================================================================================== ================
+ log | 2022-01-17 13:57:22.270 | 10 | 1 | 1 | 1 | 10 | 30 | 1 | 3 | 100 | 4096 | 1 | 3000 | 2 | 0 | us | 0 | ready |
 Query OK, 1 row(s) in set (0.002843s)
 ```
 
-因为运行在容器中的 TDengine 服务端使用容器的 hostname 建立连接，使用 taos shell 或者各种连接器（例如 JDBC-JNI）从容器外访问容器内的 TDengine 比较复杂，所以上述方式是访问容器中 TDengine 服务的最简单的方法，适用于一些简单场景。如果在一些复杂场景下想要从容器化使用 taos shell 或者各种连接器访问容器中的 TDengine 服务，请参考下一节。
+The TDengine server running in the container uses the container's hostname to establish a connection. Using TDengine CLI or various connectors (such as JDBC-JNI) to access the TDengine inside the container from outside the container is more complicated. So the above is the simplest way to access the TDengine service in the container and is suitable for some simple scenarios. Please refer to the next section if you want to access the TDengine service in the container from containerized using TDengine CLI or various connectors in some complex scenarios.
 
-## 在 host 网络上启动 TDengine
+## Start TDengine on the host network
 
 ```shell
 docker run -d --name tdengine --network host tdengine/tdengine
 ```
 
-上面的命令在 host 网络上启动 TDengine，并使用主机的 FQDN 建立连接而不是使用容器的 hostname 。这种方式和在主机上使用 `systemctl` 启动 TDengine 效果相同。在主机已安装 TDengine 客户端情况下，可以直接使用下面的命令访问它。
+The above command starts TDengine on the host network and uses the host's FQDN to establish a connection instead of the container's hostname. It works too, like using `systemctl` to start TDengine on the host. If the TDengine client is already installed on the host, you can access it directly with the following command.
 
 ```shell
 $ taos
 
 Welcome to the TDengine shell from Linux, Client Version:2.4.0.0
-Copyright (c) 2020 by TAOS Data, Inc. All rights reserved.
+Copyright (c) 2020 by TAOS Data, Inc.
 
 taos> show dnodes;
-   id   |           end_point            | vnodes | cores  |   status   | role  |       create_time       |      offline reason      |
-======================================================================================================================================
-      1 | myhost:6030           |      1 |      8 | ready      | any   | 2022-01-17 22:10:32.619 |                          |
+   id | end_point | vnodes | cores | status | role | create_time | offline reason |
+================================================================================================================================== ====
+      1 | myhost:6030 | 1 | 8 | ready | any | 2022-01-17 22:10:32.619 | |
 Query OK, 1 row(s) in set (0.003233s)
 ```
 
-## 以指定的 hostname 和 port 启动 TDengine
+## Start TDengine with the specified hostname and port
 
-利用 `TAOS_FQDN` 环境变量或者 `taos.cfg` 中的 `fqdn` 配置项可以使 TDengine 在指定的 hostname 上建立连接。这种方式可以为部署提供更大的灵活性。
+The `TAOS_FQDN` environment variable or the `fqdn` configuration item in `taos.cfg` allows TDengine to establish a connection at the specified hostname. This approach provides greater flexibility for deployment.
 
 ```shell
 docker run -d \
@@ -70,35 +70,35 @@ docker run -d \
    tdengine/tdengine
 ```
 
-上面的命令在容器中启动一个 TDengine 服务，其所监听的 hostname 为 tdengine ，并将容器的 6030 到 6049 端口段映射到主机的 6030 到 6049 端口段 （tcp 和 udp 都需要映射)。如果主机上该端口段已经被占用，可以修改上述命令指定一个主机上空闲的端口段。如果 `rpcForceTcp` 被设置为 `1` ，可以只映射 tcp 协议。
+The above command starts a TDengine service in the container, which listens to the hostname tdengine, and maps the container's port segment 6030 to 6049 to the host's port segment 6030 to 6049 (both TCP and UDP ports need to be mapped). If the port segment is already occupied on the host, you can modify the above command to specify a free port segment on the host. If `rpcForceTcp` is set to `1`, you can map only the TCP protocol.
 
-接下来，要确保 "tdengine" 这个 hostname 在 `/etc/hosts` 中可解析。
+Next, ensure the hostname "tdengine" is resolvable in `/etc/hosts`.
 
 ```shell
 echo 127.0.0.1 tdengine |sudo tee -a /etc/hosts
 ```
 
-最后，可以从 taos shell 或者任意连接器以 "tdengine" 为服务端地址访问 TDengine 服务。
+Finally, the TDengine service can be accessed from the taos shell or any connector with "tdengine" as the server address.
 
 ```shell
 taos -h tdengine -P 6030
 ```
 
-如果 `TAOS_FQDN` 被设置为与所在主机名相同，则效果与 “在 host 网络上启动 TDengine” 相同。
+If set `TAOS_FQDN` to the same hostname, the effect is the same as "Start TDengine on host network".
 
-## 在指定网络上启动 TDengine
+## Start TDengine on the specified network
 
-也可以在指定的特定网络上启动 TDengine。下面是详细步骤：
+You can also start TDengine on a specific network.
 
-1. 首先，创建一个 docker 网络，命名为 td-net
+1. First, create a docker network named `td-net`
 
    ```shell
    docker network create td-net
-   ```
+   ``` Create td-net
 
-2. 启动 TDengine
+2. Start TDengine
 
-   以下命令在 td-net 网络上启动 TDengine 服务
+   Start the TDengine service on the `td-net` network with the following command:
 
    ```shell
    docker run -d --name tdengine --network td-net \
@@ -106,17 +106,17 @@ taos -h tdengine -P 6030
       tdengine/tdengine
    ```
 
-3. 在同一网络上的另一容器中启动 TDengine 客户端
+3. Start the TDengine client in another container on the same network
 
    ```shell
    docker run --rm -it --network td-net -e TAOS_FIRST_EP=tdengine tdengine/tdengine taos
    # or
-   #docker run --rm -it --network td-net -e tdengine/tdengine taos -h tdengine
+   # docker run --rm -it --network td-net -e tdengine/tdengine taos -h tdengine
    ```
 
-## 在容器中启动客户端应用
+## Launching a client application in a container
 
-如果想在容器中启动自己的应用的话，需要将相应的对 TDengine 的依赖也要加入到镜像中，例如：
+If you want to start your application in a container, you need to add the corresponding dependencies on TDengine to the image as well, e.g.
 
 ```docker
 FROM ubuntu:20.04
@@ -133,7 +133,7 @@ RUN wget -c https://www.taosdata.com/assets-download/TDengine-client-${TDENGINE_
 #CMD ["app"]
 ```
 
-以下是一个 go 应用程序的示例：
+Here is an example GO program:
 
 ```go
 /*
@@ -218,7 +218,7 @@ func checkErr(err error, prompt string) {
 }
 ```
 
-如下是完整版本的 dockerfile
+Here is the full Dockerfile:
 
 ```docker
 FROM golang:1.17.6-buster as builder

docs-en/14-reference/13-schemaless/_category_.yml

-label: Schemaless 写入
+label: Schemaless writing

docs-en/14-reference/index.md

@@ -2,7 +2,7 @@
 title: Reference
 ---
 
-参考指南是对 TDengine 本身、 TDengine 各语言连接器及自带的工具最详细的介绍。
+The reference guide is the most detailed introduction to TDengine itself, TDengine's various language connectors, and the tools that come with it.
 
 ```mdx-code-block
 import DocCardList from '@theme/DocCardList';