apache · CritasWang · Jun 10, 2026 · Jun 10, 2026 · Jun 10, 2026
diff --git a/...ide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/...ide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md
@@ -55,7 +55,7 @@ To ensure the AINode installation package you obtained is complete and correct,
 
 **Preparation:**
 
-- Obtain the official SHA512 checksum: Please contact Timecho staff.
+- Obtain the official SHA512 checksum: Please contact commercial support.
 
 **Verification Steps (using Linux as an example):**
 
@@ -77,7 +77,7 @@ To ensure the AINode installation package you obtained is complete and correct,
 
 **Notes:**
 
-- If the verification results do not match, please contact Timecho staff to obtain a new installation package.
+- If the verification results do not match, please contact commercial support to obtain a new installation package.
 - If you encounter a "file not found" prompt during verification, check if the file path is correct or if the installation package was downloaded completely.
 
 ### 2.3 Environment Requirements
@@ -116,7 +116,7 @@ AINode supports modifying some necessary parameters. You can find the following
 ### 3.3 Importing Built-in Weight Files
 
 *If the deployment environment has network connectivity and can access HuggingFace, the system will automatically pull the built-in model weight files. This step can be skipped.*
-*For offline environments, contact Timecho staff to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.*
+*For offline environments, contact commercial support to obtain the model weight folder and place it under the `/IOTDB_AINODE_HOME/data/ainode/models/builtin` directory.*
 **NOTE:** Pay attention to the directory hierarchy. The parent directory for all built-in model weights should be `builtin`.
 
 ### 3.4 Starting AINode
@@ -228,7 +228,7 @@ If you need to upgrade the version of the current AINode, you can refer to the f
 
 3. Update built-in model weights (optional)
 
-   * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact Timecho staff to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory.
+   * If the new version involves updates to built-in models, relevant information will be updated in the [Release History](../IoTDB-Introduction/Release-history_apache.md). You may contact commercial support to obtain the latest weight package and replace it in the `data/ainode/models/builtin` directory.
 
 4. After the upgrade is completed, you can start the AINode service and check the node status. For specific commands, refer to Sections 3.4 and 3.5.
 

diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/AINode_Deployment_apache.md
@@ -69,7 +69,7 @@ To ensure the AINode installation package you obtained is complete and valid, we
       ```
 2. Execute the following command to calculate the hash value:
    ```Bash
-      sha512sum timechodb-{version}-ainode-bin.zip
+      sha512sum apache-iotdb-{version}-ainode-bin.zip
       ```
 3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):
 
@@ -129,7 +129,7 @@ AINode supports modifying some necessary parameters. You can find the following
 
 > Offline environment only (Online environments can skip this step)
 >
-Contact Timecho team to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
+Contact commercial support to obtain the model weight files, then place them in the /IOTDB_AINODE_HOME/data/ainode/models/weights/ directory.
 
 ### 3.4 Start AINode
 

diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Database-Resources_apache.md
@@ -72,11 +72,11 @@
             <td>48core</td>
             <td>1</td>
             <td>2</td>
-            <td>Please contact Timecho Business for consultation</td>
+            <td>Please contact commercial support for consultation</td>
       </tr>
       <tr>
             <td>Over 10000000</td>
-            <td colspan="4">Please contact Timecho Business for consultation</td>
+            <td colspan="4">Please contact commercial support for consultation</td>
       </tr>
 </tbody>
 </table>
@@ -136,11 +136,11 @@
             <td>128G</td>
             <td>1</td>
             <td>2</td>
-            <td>Please contact Timecho Business for consultation</td>
+            <td>Please contact commercial support for consultation</td>
       </tr>
       <tr>
             <td>Over 10000000</td>
-            <td colspan="4">Please contact Timecho Business for consultation</td>
+            <td colspan="4">Please contact commercial support for consultation</td>
       </tr>
 </tbody>
 </table>

diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Environment-Requirements.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Environment-Requirements.md
@@ -80,7 +80,7 @@ IoTDB does not have strict operational requirements for disk array configuration
 
 ### 2.1 Version Requirements
 
-IoTDB supports operating systems such as Linux, Windows, and MacOS. TimechoDB also supports Chinese CPUs like Loongson, Phytium, and Kunpeng, as well as Chinese operating systems like Kylin, UOS, and NingSi.
+IoTDB supports operating systems such as Linux, Windows, and MacOS. IoTDB also supports Chinese CPUs like Loongson, Phytium, and Kunpeng, as well as Chinese operating systems like Kylin, UOS, and NingSi.
 
 ### 2.2 Hard Disk Partitioning
 

diff --git a/...serGuide/Master/Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md b/...serGuide/Master/Table/Deployment-and-Maintenance/Monitoring-panel-deployment.md
@@ -20,19 +20,19 @@
 -->
 # Monitoring Panel Deployment
 
-The monitoring panel is one of the supporting tools for TimechoDB. It aims to solve the monitoring problems of TimechoDB and its operating system, mainly including operating system resource monitoring, TimechoDB performance monitoring, and hundreds of kernel monitoring metrics, in order to help users monitor cluster health, optimize performance, and perform maintenance. This guide demonstrates how to enable the system monitoring module in a TimechoDB instance and visualize monitoring metrics using Prometheus + Grafana, using a typical 3C3D cluster (3 ConfigNodes and 3 DataNodes) as an example.
+The monitoring panel is one of the supporting tools for IoTDB. It aims to solve the monitoring problems of IoTDB and its operating system, mainly including operating system resource monitoring, IoTDB performance monitoring, and hundreds of kernel monitoring metrics, in order to help users monitor cluster health, optimize performance, and perform maintenance. This guide demonstrates how to enable the system monitoring module in a IoTDB instance and visualize monitoring metrics using Prometheus + Grafana, using a typical 3C3D cluster (3 ConfigNodes and 3 DataNodes) as an example.
 
 ## 1. Installation Preparation
 
-1. Installing TimechoDB: Install TimechoDB V1.0 or above. Contact sales or technical support to obtain the installation package.
+1. Installing IoTDB: Install IoTDB V1.0 or above. Contact sales or technical support to obtain the installation package.
 
-2. Obtain the monitoring panel installation package: The monitoring panel is exclusive to the enterprise-grade TimechoDB. Contact sales or technical support to obtain it.
+2. Obtain the monitoring panel installation package: The monitoring panel is exclusive to the enterprise-grade IoTDB. Contact sales or technical support to obtain it.
 
 ## 2. Installation Steps
 
-### 2.1 Enable Monitoring Metrics Collection in TimechoDB
+### 2.1 Enable Monitoring Metrics Collection in IoTDB
 
-1. Enable related configuration options. The configuration options related to monitoring in TimechoDB are disabled by default. Before deploying the monitoring panel, you need to enable certain configuration options (note that the service needs to be restarted after enabling monitoring configuration).
+1. Enable related configuration options. The configuration options related to monitoring in IoTDB are disabled by default. Before deploying the monitoring panel, you need to enable certain configuration options (note that the service needs to be restarted after enabling monitoring configuration).
 
 | **Configuration**                  | **Configuration File**           | **Description**                                              |
 | :--------------------------------- | :------------------------------- | :----------------------------------------------------------- |

diff --git a/...rGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md b/...rGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md
@@ -20,7 +20,7 @@
 -->
 # Stand-Alone Deployment
 
-This guide introduces how to set up a standalone TimechoDB instance, which includes one ConfigNode and one DataNode (commonly referred to as 1C1D).
+This guide introduces how to set up a standalone IoTDB instance, which includes one ConfigNode and one DataNode (commonly referred to as 1C1D).
 
 ## 1. Prerequisites
 

diff --git a/src/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md b/src/UserGuide/Master/Table/Ecosystem-Integration/DataGrip.md
@@ -43,9 +43,9 @@ Ensure DataGrip and IoTDB are installed:
 
 Select the appropriate version of the JAR package (choose the `jar-with-dependencies.jar` variant):
 
-- Option 1: https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/iotdb-jdbc-2.0.3.3-jar-with-dependencies.jar
+- Option 1: https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/iotdb-jdbc-2.0.3-jar-with-dependencies.jar
 
-- Option 2: https://repo1.maven.org/maven2/com/timecho/iotdb/iotdb-jdbc/2.0.3.3/
+- Option 2: https://repo1.maven.org/maven2/org/apache/iotdb/iotdb-jdbc/2.0.3/
 
 ![](/img/datagrip-2.png)
 

diff --git a/src/UserGuide/Master/Table/QuickStart/QuickStart_apache.md b/src/UserGuide/Master/Table/QuickStart/QuickStart_apache.md
@@ -31,7 +31,7 @@ This guide will assist you in quickly installing and deploying IoTDB. You can qu
 
 2. Complete system configuration preparations: IoTDB's system configuration involves multiple aspects. For an introduction to key system configurations, please see [System Requirements](../Deployment-and-Maintenance/Environment-Requirements.md)
 
-3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain TimechoDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md)
+3. Obtain the installation package: You can obtain the IoTDB installation package on the [Apache IoTDB official website](https://iotdb.apache.org/zh/Download/).For the specific structure of the installation package, please refer to[Obtain IoTDB](../Deployment-and-Maintenance/IoTDB-Package_apache.md)
 
 4. Install the database and activate it: Depending on your actual deployment architecture, you can choose from the following tutorials for installation and deployment:
 

diff --git a/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md b/src/UserGuide/Master/Table/Tools-System/Monitor-Tool_apache.md
@@ -99,7 +99,7 @@ For more details, refer to the following documents:
 
 ## 4. Apache IoTDB Dashboard
 
-The `Apache IoTDB Dashboard` is a companion product of TimechoDB, supporting unified centralized operation and maintenance management. It allows monitoring multiple clusters through a single monitoring panel. You can contact the business team to obtain the Dashboard's JSON file.
+The `Apache IoTDB Dashboard` is a companion product of IoTDB, supporting unified centralized operation and maintenance management. It allows monitoring multiple clusters through a single monitoring panel. You can contact the business team to obtain the Dashboard's JSON file.
 
 ![Apache IoTDB Dashboard](/img/%E7%9B%91%E6%8E%A7%20default%20cluster.png)
 

diff --git a/src/UserGuide/Master/Table/User-Manual/Load-Balance.md b/src/UserGuide/Master/Table/User-Manual/Load-Balance.md
@@ -137,18 +137,18 @@ echo "192.168.1.3  iotdb-1" >> /etc/hosts
 
 #### 1.3.2 Scaling Operation
 
-1. To ensure the TimechoDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment.
+1. To ensure the IoTDB installation package you obtained is complete and correct, it is recommended to perform an SHA512 checksum before installation and deployment.
 2. Unzip the installation package and enter the installation directory.
 
 ```
-unzip  timechodb-{version}-bin.zip
-cd  timechodb-{version}-bin
+unzip  apache-iotdb-{version}-bin.zip
+cd  apache-iotdb-{version}-bin
 ```
 
 3. Modify the relevant configuration.
 
 ```
-cd  timechodb-{version}-bin/conf
+cd  apache-iotdb-{version}-bin/conf
 vim iotdb-system.properties
 ```
 
@@ -175,10 +175,10 @@ Navigate to the `sbin`directory under IoTDB and start the datanode:
 
 ```
 # Linux or macOS
-  ./timechodb-{version}-bin/sbin/start-cli.sh
+  ./apache-iotdb-{version}-bin/sbin/start-cli.sh
 
   # Windows
-  .\timechodb-{version}-bin\sbin\start-cli.bat
+  .\apache-iotdb-{version}-bin\sbin\start-cli.bat
 ```
 
 6. Execute commands for verification.