docs: replace application with client driver

docs-en/03-get-started/03-get-started.md

@@ -10,7 +10,7 @@ import AptGetInstall from "./\_apt_get_install.mdx";
 
 ## Quick Install
 
-The full package of TDengine includes server(taosd), taosAdapter for connecting with third-party systems and providing RESTful interface, application driver(taosc), command line program(CLI, taos) and some tools. For current version, the server taosd and taosAdapter can only be installed and run on Linux systems, and will support Windows, macOS and other systems in the future. The application driver taosc and TDengine CLI can be installed and run on Windows or Linux. In addition to the RESTful interface, TDengine also provides connectors for a number of programming languages. In versions before 2.4, there is no taosAdapter, and the RESTfule interface is provided by the built-in http service of taosd.
+The full package of TDengine includes server(taosd), taosAdapter for connecting with third-party systems and providing RESTful interface, client driver(taosc), command line program(CLI, taos) and some tools. For current version, the server taosd and taosAdapter can only be installed and run on Linux systems, and will support Windows, macOS and other systems in the future. The client driver taosc and TDengine CLI can be installed and run on Windows or Linux. In addition to the RESTful interface, TDengine also provides connectors for a number of programming languages. In versions before 2.4, there is no taosAdapter, and the RESTfule interface is provided by the built-in http service of taosd.
 
 TDengine supports X64/ARM64/MIPS64/Alpha64 hardware platforms, and will support ARM32, RISC-V and other CPU architectures in the future.
 
@@ -119,7 +119,7 @@ select * from t;
  2019-07-15 01:00:00.000 |          20 |
 Query OK, 2 row(s) in set (0.003128s)
 ```
-Besides executing SQL commands, system administrator can check running status, add/drop user accounts and manage the running instances. TAOS CLI with application driver can be installed and run on either Linux or windows machine. For more details on CLI, please [check here](../reference/taos-shell/).
+Besides executing SQL commands, system administrator can check running status, add/drop user accounts and manage the running instances. TAOS CLI with client driver can be installed and run on either Linux or windows machine. For more details on CLI, please [check here](../reference/taos-shell/).
 
 ## Experience the blazing fast speed
 

docs-en/04-develop/01-connect/index.md

@@ -26,18 +26,18 @@ Any application programs running on any kind of platforms can access TDengine th
 There are two ways for a connector to establish connections to TDengine:
 
 1. Connection through the REST API provided by taosAdapter component, this way is called "REST connection" hereinafter.
-2. Connection through the TDengine application driver taosc, this way is called "Native connection" hereinafter.
+2. Connection through the TDengine client driver (taosc), this way is called "Native connection" hereinafter.
 
 Either way, same or similar APIs are provided by connectors to access database or execute SQL statements, no obvious difference can be observed.
 
 Key differences：
 
-1. With REST connection, it's not necessary to install TDengine application driver taosc, it's more friendly for cross-platform with the cost of 30% performance downgrade. When taosc has an upgrade, application does not need to make changes. 
+1. With REST connection, it's not necessary to install TDengine client driver (taosc), it's more friendly for cross-platform with the cost of 30% performance downgrade. When taosc has an upgrade, application does not need to make changes. 
 2. With native connection, full compatibility of TDengine can be utilized, like [Parameter Binding](/reference/connector/cpp#Parameter Binding-api), [Subscription](reference/connector/cpp#Subscription), etc. But taosc has to be installed, some platforms may not be supported.
 
 ## Install Client Driver taosc
 
-If choosing to use native connection and the application is not on the same host as TDengine server, TDengine application driver taosc needs to be installed on the host where the application is. If choosing to use REST connection or the application is on the same host as server side, this step can be skipped. It's better to use same version of taosc as the server.
+If choosing to use native connection and the application is not on the same host as TDengine server, TDengine client driver taosc needs to be installed on the host where the application is. If choosing to use REST connection or the application is on the same host as server side, this step can be skipped. It's better to use same version of taosc as the server.
 
 ### Install
 
@@ -198,7 +198,7 @@ install.packages("RJDBC")
 </TabItem>
 <TabItem label="C" value="c">
 
-If the client driver taosc is already installed, then the C connector is already available.
+If the client driver (taosc) is already installed, then the C connector is already available.
 <br/>
 
 </TabItem>

docs-en/14-reference/03-connector/_linux_install.mdx

@@ -15,8 +15,8 @@ import PkgList from "/components/PkgList";
 
    Once the package is unzipped, you will see the following files in the directory:
    - _ install_client.sh_: install script
-   - _ taos.tar.gz_: application driver package
-   - _ driver_: TDengine application driver
+   - _ taos.tar.gz_: client driver package
+   - _ driver_: TDengine client driver
    - _examples_: some example programs of different programming languages (C/C#/go/JDBC/MATLAB/python/R)
 
    You can run `install_client.sh`  to install it.
@@ -27,7 +27,7 @@ import PkgList from "/components/PkgList";
 
 :::tip
 
-1. If the computer does not run the TDengine service but installs the TDengine application driver, then you need to config `firstEP` in  `taos.cfg` only, and there is no need to configure `FQDN`;
+1. If the computer does not run the TDengine service but installs the TDengine client driver, then you need to config `firstEP` in  `taos.cfg` only, and there is no need to configure `FQDN`;
 
 2. If you encounter the "Unable to resolve FQDN" error, please make sure the FQDN in the `/etc/hosts` file of the current computer is correctly configured, or the DNS service is correctly configured.
 

docs-en/14-reference/03-connector/_windows_install.mdx

@@ -13,7 +13,7 @@ import PkgList from "/components/PkgList";
 
    - _taos.exe_ : TDengine CLI command line program
    - _cfg_ : configuration file directory
-   - _driver_: application driver dynamic link library
+   - _driver_: client driver dynamic link library
    - _examples_: sample programs bash/C/C#/go/JDBC/Python/Node.js
    - _include_: header files
    - _log_ : log file
@@ -26,6 +26,6 @@ import PkgList from "/components/PkgList";
 :::tip
 
 1. If you use FQDN to connect to the server, you must ensure the local network environment DNS is configured, or add FQDN addressing records in the `hosts` file, e.g., edit C:\Windows\system32\drivers\etc\hosts and add a record like the following: `192.168.1.99 h1.tados.com`..
-2. Uninstall: Run unins000.exe to uninstall the TDengine application driver.
+2. Uninstall: Run unins000.exe to uninstall the TDengine client driver.
 
 :::

docs-en/21-tdinternal/01-arch.md

@@ -14,7 +14,7 @@ Logical structure diagram of TDengine distributed architecture as following:
 ![TDengine architecture diagram](structure.png)
 <center> Figure 1: TDengine architecture diagram </center>
 
-A complete TDengine system runs on one or more physical nodes. Logically, it includes data node (dnode), TDengine application driver (TAOSC) and application (app). There are one or more data nodes in the system, which form a cluster. The application interacts with the TDengine cluster through TAOSC's API. The following is a brief introduction to each logical unit.
+A complete TDengine system runs on one or more physical nodes. Logically, it includes data node (dnode), TDengine client driver (TAOSC) and application (app). There are one or more data nodes in the system, which form a cluster. The application interacts with the TDengine cluster through TAOSC's API. The following is a brief introduction to each logical unit.
 
 **Physical node (pnode)**: A pnode is a computer that runs independently and has its own computing, storage and network capabilities. It can be a physical machine, virtual machine, or Docker container installed with OS. The physical node is identified by its configured FQDN (Fully Qualified Domain Name). TDengine relies entirely on FQDN for network communication. If you don't know about FQDN, please check [wikipedia](https://en.wikipedia.org/wiki/Fully_qualified_domain_name).
 
@@ -30,7 +30,7 @@ A complete TDengine system runs on one or more physical nodes. Logically, it inc
 
 ### Node Communication
 
-**Communication mode**: The communication among each data node of TDengine system, and among the application driver and each data node is carried out through TCP/UDP. Considering an IoT scenario, the data writing packets are generally not large, so TDengine uses UDP in addition to TCP for transmission, because UDP is more efficient and is not limited by the number of connections. TDengine implements its own timeout, retransmission, confirmation and other mechanisms to ensure reliable transmission of UDP. For packets with a data volume of less than 15K, UDP is adopted for transmission, and TCP is automatically adopted for transmission of packets with a data volume of more than 15K or query operations. At the same time, TDengine will automatically compress/decompress the data, digital sign/authenticate the data according to the configuration and data packet. For data replication among data nodes, only TCP is used for data transportation.
+**Communication mode**: The communication among each data node of TDengine system, and among the client driver and each data node is carried out through TCP/UDP. Considering an IoT scenario, the data writing packets are generally not large, so TDengine uses UDP in addition to TCP for transmission, because UDP is more efficient and is not limited by the number of connections. TDengine implements its own timeout, retransmission, confirmation and other mechanisms to ensure reliable transmission of UDP. For packets with a data volume of less than 15K, UDP is adopted for transmission, and TCP is automatically adopted for transmission of packets with a data volume of more than 15K or query operations. At the same time, TDengine will automatically compress/decompress the data, digital sign/authenticate the data according to the configuration and data packet. For data replication among data nodes, only TCP is used for data transportation.
 
 **FQDN configuration:** A data node has one or more FQDNs, which can be specified in the system configuration file taos.cfg with the parameter “fqdn”. If it is not specified, the system will automatically use the hostname of the computer as its FQDN. If the node is not configured with FQDN, you can directly set the configuration parameter “fqdn” of the node to its IP address. However, IP is not recommended because IP address may be changed, and once it changes, the cluster will not work properly. The EP (End Point) of a data node consists of FQDN + Port. With FQDN, it is necessary to ensure the DNS service is running, or hosts files on nodes are configured properly.