Remove enterprise-only docs and wording

src/UserGuide/Master/Table/Deployment-and-Maintenance/Docker-Deployment_apache.md

@@ -275,7 +275,7 @@ On each server, create two YML files: `confignode.yml` and `datanode.yml`. Examp
 version: "3"
 services:
   iotdb-confignode:
-    image: iotdb-enterprise:2.0.x-standalone #The image used
+    image: apache/iotdb:2.0.x-standalone #The image used
     hostname: iotdb-1|iotdb-2|iotdb-3 #Choose from three options based on the actual situation
     container_name: iotdb-confignode
     command: ["bash", "-c", "entrypoint.sh confignode"]
@@ -310,7 +310,7 @@ services:
 version: "3"
 services:
   iotdb-datanode:
-    image: iotdb-enterprise:2.0.x-standalone #The image used
+    image: apache/iotdb:2.0.x-standalone #The image used
     hostname: iotdb-1|iotdb-2|iotdb-3 #Choose from three options based on the actual situation
     container_name: iotdb-datanode
     command: ["bash", "-c", "entrypoint.sh datanode"]

src/UserGuide/Master/Table/IoTDB-Introduction/Commercial-Support_apache.md

@@ -33,7 +33,7 @@ The information provided here was provided by the entities named, and is not ver
 
 |                                                                                                                                                                                                                                                                                   | Name                                                       | <span style="display:block;min-width:360px;">Description</span>                                                                                                                                                                                                 | Contact Person(s) | Contact Email(s)                  | Contact Phone(s) | Involvement Level |
 | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | ----------------------------------- | ------------------ | ------------------- |
-| <span style="display:inline-flex;width:88px;height:34px;align-items:center;justify-content:center;"><img src="/img/commercial-support-timecho.png" alt="Timecho logo" style="max-width:80px;max-height:28px;width:auto;height:auto;object-fit:contain;" /></span> | [Timecho Europe GmbH](https://www.timecho-global.com/)        | <span style="display:block;min-width:360px;line-height:1.55;">Enterprise-grade products and solutions, technical support/ consulting/ training, deployment and migration, performance tuning, training, custom development, protocol/ connector/ driver development, time-series foundation model services, and AI services.</span> | Pengchen Zheng    | pengcheng.zheng@timecho.com       | -                | Committer         |
+| <span style="display:inline-flex;width:88px;height:34px;align-items:center;justify-content:center;"><img src="/img/commercial-support-timecho.png" alt="Timecho logo" style="max-width:80px;max-height:28px;width:auto;height:auto;object-fit:contain;" /></span> | [Timecho Europe GmbH](https://www.timecho-global.com/)        | <span style="display:block;min-width:360px;line-height:1.55;">Enterprise-grade products and solutions, technical support/ consulting/ training, deployment and migration, performance tuning, training, custom development, protocol/ connector/ driver development, time-series foundation model services, and AI services.</span> | Pengcheng Zheng    | pengcheng.zheng@timecho.com       | -                | Committer         |
 | <span style="display:inline-flex;width:88px;height:34px;align-items:center;justify-content:center;"><img src="/img/commercial-support-pragmatic.png" alt="pragmatic industries logo" style="max-width:80px;max-height:28px;width:auto;height:auto;object-fit:contain;" /></span> | [pragmatic industries GmbH](https://pragmaticindustries.com/)| <span style="display:block;min-width:360px;line-height:1.55;">Technical support/ consulting/ training, deployment and migration, custom development</span>                                                                                                                                                                          | Julian Feinauer   | j.feinauer@pragmaticindustries.de | -                | PMC Member        |
 | <span style="display:inline-flex;width:88px;height:34px;align-items:center;justify-content:center;"><img src="/img/commercial-support-toddy.png" alt="ToddySoft logo" style="max-width:80px;max-height:28px;width:auto;height:auto;object-fit:contain;" /></span> | [ToddySoft GmbH](https://toddysoft.com/)| <span style="display:block;min-width:360px;line-height:1.55;">Technical support/ consulting/ training, deployment and migration, protocol/ connector/ driver development, custom development</span>                                                                                                                                 | Christofer Dutz   | christofer.dutz@toddysoft.com     | -                | PMC Member        |
 

src/UserGuide/Master/Table/Reference/System-Tables_apache.md

@@ -524,7 +524,6 @@ IoTDB> select * from information_schema.keywords limit 10
 | internal\_port                             | INT32     | ATTRIBUTE       | Internal port        |
 | version                                    | STRING    | ATTRIBUTE       | Version number       |
 | build\_info                                | STRING    | ATTRIBUTE       | Commit ID            |
-| activate\_status (Enterprise Edition only) | STRING    | ATTRIBUTE       | Activation status    |
 
 * Only administrators are allowed to perform operations on this table.
 * Query example:

src/UserGuide/Master/Table/User-Manual/Load-Balance.md

@@ -211,7 +211,7 @@ Total line number = 4
 It costs 0.110s
 ```
 
-7. Repeat the above steps for other nodes. It is important to note that for a new node to join the original cluster successfully, the original cluster must have sufficient allowance for additional DataNode nodes. Otherwise, you will need to contact the support team to reapply for activation code information.
+7. Repeat the above steps for other nodes. It is important to note that for a new node to join the original cluster successfully, the original cluster must have sufficient allowance for additional DataNode nodes.
 
 #### 1.3.3 Manual Load Balancing (Optional)
 

src/UserGuide/Master/Tree/Deployment-and-Maintenance/Docker-Deployment_apache.md

@@ -274,7 +274,7 @@ On each server, two yml files need to be written, namely confignnode. yml and da
 version: "3"
 services:
   iotdb-confignode:
-    image: iotdb-enterprise:2.0.x-standalone #The image used
+    image: apache/iotdb:2.0.x-standalone #The image used
     hostname: iotdb-1|iotdb-2|iotdb-3 #Choose from three options based on the actual situation
     container_name: iotdb-confignode
     command: ["bash", "-c", "entrypoint.sh confignode"]
@@ -309,7 +309,7 @@ services:
 version: "3"
 services:
   iotdb-datanode:
-    image: iotdb-enterprise:2.0.x-standalone #The image used
+    image: apache/iotdb:2.0.x-standalone #The image used
     hostname: iotdb-1|iotdb-2|iotdb-3 #Choose from three options based on the actual situation
     container_name: iotdb-datanode
     command: ["bash", "-c", "entrypoint.sh datanode"]