docs: refine 3rd parties in english (#12509)

* docs: 3rd parties doc in English

[TD-15558]

* fix link to broder

* docs: third parties doc in English

[TD-15558]

* docs: 3rd parties doc in English

translate reference doc

* fix img link

* fix img links

* fix build issues

* translate prometheus section

* fix wording

* refine wording

docs-en/20-third-party/02-prometheus.md

@@ -5,7 +5,7 @@ title: Prometheus writing and reading
 
 import Prometheus from "../14-reference/_prometheus.mdx"
 
-Prometheus is a widespread open-source monitoring and alerting system. Prometheus joined the Cloud Native Computing Foundation (CNCF) in 2016 as the second-hosted project after Kubernetes, which has a very active developer and user community.
+Prometheus is a widespread open-source monitoring and alerting system. Prometheus joined the Cloud Native Computing Foundation (CNCF) in 2016 as the second incubated project after Kubernetes, which has a very active developer and user community.
 
 Prometheus provides `remote_write` and `remote_read` interfaces to leverage other database products as its storage engine. To enable users of the Prometheus ecosystem to take advantage of TDengine's efficient writing and querying, TDengine also provides support for these two interfaces.
 

docs-en/20-third-party/03-telegraf.md

@@ -5,7 +5,7 @@ title: Telegraf writing
 
 import Telegraf from "../14-reference/_telegraf.mdx"
 
-Telegraf is a viral metrics collection open-source software. In the data collection and platform monitoring system, Telegraf can collect the operation information of various components without writing their scripts to collect regularly, reducing the difficulty of data acquisition.
+Telegraf is a viral metrics collection open-source software. Telegraf can collect the operation information of various components without writing any scripts to collect regularly, reducing the difficulty of data acquisition.
 
 Telegraf's data can be written to TDengine by simply adding the output configuration of Telegraf to the URL corresponding to taosAdapter and modifying several configuration items. The presence of Telegraf data in TDengine can take advantage of TDengine's efficient storage query performance and clustering capabilities for time-series data.
 

docs-en/20-third-party/05-collectd.md

@@ -6,9 +6,9 @@ title: collectd writing
 import CollectD from "../14-reference/_collectd.mdx"
 
 
-collectd is a daemon used to collect system performance. collectd provides various storage mechanisms to store different values. It periodically counts system-related statistics while the system is running and storing information. You can use this information to help identify current system performance bottlenecks and predict future system load.
+collectd is a daemon used to collect system performance metric data. collectd provides various storage mechanisms to store different values. It periodically counts system performance statistics number while the system is running and storing information. You can use this information to help identify current system performance bottlenecks and predict future system load.
 
-You can write the data collected by collectd to TDengine by simply pointing the configuration of collectd to the domain name (or IP address) and corresponding port of the server running taosAdapter. It can take full advantage of TDengine's efficient storage query performance and clustering capability for time-series data.
+You can write the data collected by collectd to TDengine by simply modifying the configuration of collectd to the domain name (or IP address) and corresponding port of the server running taosAdapter. It can take full advantage of TDengine's efficient storage query performance and clustering capability for time-series data.
 
 ## Prerequisites
 
@@ -28,7 +28,7 @@ Restart collectd
 sudo systemctl restart collectd
 ```
 
-Use the TDengine CLI to verify that data is written to TDengine from collectd and can read out correctly.
+Use the TDengine CLI to verify that collectd's data is written to TDengine and can read out correctly.
 
 ```
 taos> show databases;

docs-en/20-third-party/06-statsd.md

@@ -5,9 +5,9 @@ title: StatsD writing
 
 import StatsD from "../14-reference/_statsd.mdx"
 
-StatsD is a simple daemon for aggregating and summarizing application metrics, which has evolved rapidly in recent years into a unified protocol for collecting application performance metrics.
+StatsD is a simple daemon for aggregating application metrics, which has evolved rapidly in recent years into a unified protocol for collecting application performance metrics.
 
-You can write StatsD data to TDengine by simply filling in the configuration file of StatsD with the domain name (or IP address) of the server running taosAdapter and the corresponding port. It can take full advantage of TDengine's efficient storage query performance and clustering capabilities for time-series data.
+You can write StatsD data to TDengine by simply modifying in the configuration file of StatsD with the domain name (or IP address) of the server running taosAdapter and the corresponding port. It can take full advantage of TDengine's efficient storage query performance and clustering capabilities for time-series data.
 
 ## Prerequisites
 
@@ -36,7 +36,7 @@ Using the utility software `nc` to write data for test:
 $ echo "foo:1|c" | nc -u -w0 127.0.0.1 8125
 ```
 
-Use the TDengine CLI to verify that data is written to TDengine from StatsD and can read out correctly.
+Use the TDengine CLI to verify that StatsD data is written to TDengine and can read out correctly.
 
 ```
 Welcome to the TDengine shell from Linux, Client Version:2.4.0.0

docs-en/20-third-party/07-icinga2.md

@@ -5,7 +5,7 @@ title: icinga2 writing
 
 import Icinga2 from "../14-reference/_icinga2.mdx"
 
-icinga2 is an open-source host, network monitoring software initially developed from the Nagios network monitoring application. Currently, icinga2 is distributed under the GNU GPL v2 license.
+icinga2 is an open-source software monitoring host and network initially developed from the Nagios network monitoring application. Currently, icinga2 is distributed under the GNU GPL v2 license.
 
 You can write the data collected by icinga2 to TDengine by simply modifying the icinga2 configuration to point to the taosAdapter server and the corresponding port, taking advantage of TDengine's efficient storage and query performance and clustering capabilities for time-series data.
 

docs-en/20-third-party/08-tcollector.md

 ---
 sidebar_label: TCollector
-title: TCollector 写入
+title: TCollector writing
 ---
 
 import Tcollector from "../14-reference/_tcollector.mdx"
 
-TCollector is part of openTSDB and collects client logs to send to the database.
+TCollector is part of openTSDB and collects client computer's logs to send to the database.
 
 You can write the data collected by TCollector to TDengine by simply changing the configuration of TCollector to point to the domain name (or IP address) and corresponding port of the server running taosAdapter. It can take full advantage of TDengine's efficient storage query performance and clustering capability for time-series data.
 
 ## Prerequisites
 
-To write TCollector data to TDengine requires the following preparations.
+To write data to the TDengine via TCollector requires the following preparations.
 - The TDengine cluster has been deployed and is working properly
 - taosAdapter is installed and running properly. Please refer to the [taosAdapter manual](/reference/taosadapter) for details.
 - TCollector has been installed. Please refer to [official documentation](http://opentsdb.net/docs/build/html/user_guide/utilities/tcollector.html#installation-of-tcollector) for TCollector installation
@@ -29,7 +29,7 @@ sudo systemctl restart taosadapter
 
 Run `sudo ./tcollector.py`:
 
-Wait for a few seconds and then use the TDengine CLI to query TDengine whether the corresponding database has been created and data are written.
+Wait for a few seconds and then use the TDengine CLI to query whether the corresponding database has been created and data are written in TDengine.
 
 ```
 taos> show databases;

docs-en/20-third-party/09-emq-broker.md

@@ -3,7 +3,7 @@ sidebar_label: EMQ Broker
 title: EMQ Broker writing
 ---
 
-MQTT is a popular IoT data transfer protocol, [EMQ](https://github.com/emqx/emqx) is an open source MQTT Broker software, without any code, only need to use "rules" in EMQ Dashboard to do simple configuration, you can write MQTT data directly to TDengine. EMQ X supports saving data to TDengine by sending to web services, and also provides native TDengine driver for direct saving in the Enterprise Edition. Please refer to the [EMQ official documentation](https://www.emqx.io/docs/en/v4.4/rule/rule-engine.html) for details on how to use it. tdengine).
+MQTT is a popular IoT data transfer protocol, [EMQ](https://github.com/emqx/emqx) is an open-source MQTT Broker software, without any code, only need to use "rules" in EMQ Dashboard to do simple configuration. You can write MQTT data directly to TDengine. EMQ X supports saving data to TDengine by sending it to web services and provides a native TDengine driver for direct saving in the Enterprise Edition. Please refer to the [EMQ official documentation](https://www.emqx.io/docs/en/v4.4/rule/rule-engine.html) for details on how to use it. tdengine).
 
 ## Prerequisites
 
@@ -14,9 +14,9 @@ The following preparations are required for EMQX to add TDengine data sources co
 
 ## Install and start EMQX
 
-Depending on the current operating system, users can download the installation package from the EMQX official website and execute the installation. The download address is as follows: <https://www.emqx.io/zh/downloads>. After installation, use `sudo emqx start` or `sudo systemctl start emqx` to start the EMQX service.
+Depending on the current operating system, users can download the installation package from the [EMQX official website](https://www.emqx.io/downloads) and execute the installation. After installation, use `sudo emqx start` or `sudo systemctl start emqx` to start the EMQX service.
 
-## Create the appropriate database and table structures in TDengine for receiving MQTT data
+## Create the appropriate database and table schema in TDengine for receiving MQTT data
 
 ### Take the Docker installation of TDengine as an example
 
@@ -28,26 +28,25 @@ Depending on the current operating system, users can download the installation p
 ### Create Database and Table
 
 ```sql
-    create database test;
-    use test;
-    create table:
+    CREATE DATABASE test;
+    USE test;
 
     CREATE TABLE sensor_data (ts timestamp, temperature float, humidity float, volume float, PM10 float, pm25 float, SO2 float, NO2 float, CO float, sensor_id NCHAR(255), area TINYINT, coll_time timestamp);
 ```
 
-Note: The table structure is based on the blog [(In Chinese) Data Transfer, Storage, Presentation, EMQ X + TDengine Build MQTT IoT Data Visualization Platform](https://www.taosdata.com/blog/2020/08/04/1722.html) as an example. Subsequent operations are carried out with this blog scenario as an example. Please modify it according to the actual application scenario.
+Note: The table schema is based on the blog [(In Chinese) Data Transfer, Storage, Presentation, EMQ X + TDengine Build MQTT IoT Data Visualization Platform](https://www.taosdata.com/blog/2020/08/04/1722.html) as an example. Subsequent operations are carried out with this blog scenario too. Please modify it according to your actual application scenario.
 
 ## Configuring EMQX Rules
 
-Since the configuration interface of EMQX differs from version to version, here is only v4.4.3 as an example. For other versions, please refer to the corresponding official documentation.
+Since the configuration interface of EMQX differs from version to version, here is v4.4.3 as an example. For other versions, please refer to the corresponding official documentation.
 
 ### Login EMQX Dashboard
 
-Use your browser to open the URL http://IP:18083 and log in to EMQX Dashboard. The initial installation username is `admin` and the password is: `public`.
+Use your browser to open the URL `http://IP:18083` and log in to EMQX Dashboard. The initial installation username is `admin` and the password is: `public`.
 
 ![img](./emqx/login-dashboard.png)
 
-### Creating Rules
+### Creating Rule
 
 Select "Rule" in the "Rule Engine" on the left and click the "Create" button: !
 
@@ -65,17 +64,17 @@ Select "Rule" in the "Rule Engine" on the left and click the "Create" button: !
 
 ![img](./emqx/create-resource.png)
 
-Select "Send Data to Web Service" and click the "New Resource" button.
+Select "Data to Web Service" and click the "New Resource" button.
 
 ### Edit "Resource"
 
-Select "Send Data to Web Service" and fill in the request URL as the address and port of the server running taosAdapter (default is 6041). Leave the other properties at their default values.
+Select "Data to Web Service" and fill in the request URL as the address and port of the server running taosAdapter (default is 6041). Leave the other properties at their default values.
 
 ![img](./emqx/edit-resource.png)
 
 ### Edit "action"
 
-Edit the resource configuration to add the key/value pairing for Authorization authentication. Please refer to the [ TDengine REST API documentation ](https://docs.taosdata.com/reference/rest-api/) for the documentation. Enter the rule engine replacement template in the message body.
+Edit the resource configuration to add the key/value pairing for Authorization. Please refer to the [ TDengine REST API documentation ](https://docs.taosdata.com/reference/rest-api/) for the authorization in details. Enter the rule engine replacement template in the message body.
 
 ![img](./emqx/edit-action.png)
 
@@ -162,7 +161,7 @@ Edit the resource configuration to add the key/value pairing for Authorization a
     }
 ```
 
-Note: CLIENT_NUM in the code can be set to a smaller value at the beginning of the test to avoid hardware performance not being able to handle a more significant number of concurrent clients.
+Note: `CLIENT_NUM` in the code can be set to a smaller value at the beginning of the test to avoid hardware performance be not capable to handle a more significant number of concurrent clients.
 
 ![img](./emqx/client-num.png)
 

docs-en/20-third-party/10-hive-mq-broker.md

@@ -3,4 +3,4 @@ sidebar_label: HiveMQ Broker
 title: HiveMQ Broker writing
 ---
 
-[HiveMQ](https://www.hivemq.com/) is an MQTT broker that provides community and enterprise versions. HiveMQ is mainly for enterprise and emerging machine-to-machine M2M communication and internal transport, meeting scalability, ease of management, and security features. HiveMQ provides an open-source plug-in development kit. MQTT data can be saved to TDengine via HiveMQ extension - TDengine. Please refer to the [HiveMQ extension - TDengine documentation](https://github.com/huskar-t/hivemq-tdengine-extension/blob/b62a26ecc164a310104df57691691b237e091c89/README_EN.md) for details on how to use it.
\ No newline at end of file
+[HiveMQ](https://www.hivemq.com/) is an MQTT broker that provides community and enterprise editions. HiveMQ is mainly for enterprise emerging machine-to-machine M2M communication and internal transport, meeting scalability, ease of management, and security features. HiveMQ provides an open-source plug-in development kit. MQTT data can be saved to TDengine via TDengine extension for HiveMQ. Please refer to the [HiveMQ extension - TDengine documentation](https://github.com/huskar-t/hivemq-tdengine-extension/blob/b62a26ecc164a310104df57691691b237e091c89/README_EN.md) for details on how to use it.
\ No newline at end of file