add description about time and timestamp when inserting data in tree mode

Author: leto-bbq

src/UserGuide/Master/Tree/Basic-Concept/Write-Data_apache.md

@@ -58,6 +58,8 @@ In addition, The INSERT statement support insert multi-rows at once. The sample
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+When writing data to the tree model, both timestamp and time can be used as time column identifiers in INSERT statements, and there is no need to deliberately distinguish between them when writing statements. However, in query results, the time column is uniformly displayed as Time (a fixed name) to ensure a consistent result format.
+
 After inserting the data, we can simply query the inserted data using the SELECT statement:
 
 ```sql

src/UserGuide/Master/Tree/Basic-Concept/Write-Data_timecho.md

@@ -58,6 +58,8 @@ In addition, The INSERT statement support insert multi-rows at once. The sample
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+When writing data to the tree model, both timestamp and time can be used as time column identifiers in INSERT statements, and there is no need to deliberately distinguish between them when writing statements. However, in query results, the time column is uniformly displayed as Time (a fixed name) to ensure a consistent result format.
+
 After inserting the data, we can simply query the inserted data using the SELECT statement:
 
 ```sql

src/UserGuide/V1.3.x/Basic-Concept/Write-Data.md

@@ -58,6 +58,8 @@ In addition, The INSERT statement support insert multi-rows at once. The sample
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+When writing data to the tree model, both timestamp and time can be used as time column identifiers in INSERT statements, and there is no need to deliberately distinguish between them when writing statements. However, in query results, the time column is uniformly displayed as Time (a fixed name) to ensure a consistent result format.
+
 After inserting the data, we can simply query the inserted data using the SELECT statement:
 
 ```sql

src/UserGuide/dev-1.3/Basic-Concept/Write-Data.md

@@ -58,6 +58,8 @@ In addition, The INSERT statement support insert multi-rows at once. The sample
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+When writing data to the tree model, both timestamp and time can be used as time column identifiers in INSERT statements, and there is no need to deliberately distinguish between them when writing statements. However, in query results, the time column is uniformly displayed as Time (a fixed name) to ensure a consistent result format.
+
 After inserting the data, we can simply query the inserted data using the SELECT statement:
 
 ```sql

src/UserGuide/latest/Basic-Concept/Write-Data_apache.md

@@ -58,6 +58,8 @@ In addition, The INSERT statement support insert multi-rows at once. The sample
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+When writing data to the tree model, both timestamp and time can be used as time column identifiers in INSERT statements, and there is no need to deliberately distinguish between them when writing statements. However, in query results, the time column is uniformly displayed as Time (a fixed name) to ensure a consistent result format.
+
 After inserting the data, we can simply query the inserted data using the SELECT statement:
 
 ```sql

src/UserGuide/latest/Basic-Concept/Write-Data_timecho.md

@@ -58,6 +58,8 @@ In addition, The INSERT statement support insert multi-rows at once. The sample
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+When writing data to the tree model, both timestamp and time can be used as time column identifiers in INSERT statements, and there is no need to deliberately distinguish between them when writing statements. However, in query results, the time column is uniformly displayed as Time (a fixed name) to ensure a consistent result format.
+
 After inserting the data, we can simply query the inserted data using the SELECT statement:
 
 ```sql

src/zh/UserGuide/Master/Tree/Basic-Concept/Write-Data_apache.md

@@ -58,6 +58,8 @@ IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) values (2, fa
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+在树模型写入数据时，timestamp 与 time 均可作为时间列标识用于 INSERT 语句，书写时无需刻意区分；但查询结果中，时间列统一展示为 Time（固定名称），保证结果格式统一。
+
 插入数据后我们可以使用 SELECT 语句简单查询已插入的数据。
 
 ```sql

src/zh/UserGuide/Master/Tree/Basic-Concept/Write-Data_timecho.md

@@ -58,6 +58,8 @@ IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) values (2, fa
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+在树模型写入数据时，timestamp 与 time 均可作为时间列标识用于 INSERT 语句，书写时无需刻意区分；但查询结果中，时间列统一展示为 Time（固定名称），保证结果格式统一。
+
 插入数据后我们可以使用 SELECT 语句简单查询已插入的数据。
 
 ```sql

src/zh/UserGuide/V1.3.x/Basic-Concept/Write-Data.md

@@ -58,6 +58,8 @@ IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) values (2, fa
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+在树模型写入数据时，timestamp 与 time 均可作为时间列标识用于 INSERT 语句，书写时无需刻意区分；但查询结果中，时间列统一展示为 Time（固定名称），保证结果格式统一。
+
 插入数据后我们可以使用 SELECT 语句简单查询已插入的数据。
 
 ```sql

src/zh/UserGuide/dev-1.3/Basic-Concept/Write-Data.md

@@ -58,6 +58,8 @@ IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) values (2, fa
 IoTDB > insert into root.ln.wf02.wt02(timestamp, status, hardware) VALUES (3, false, 'v3'),(4, true, 'v4')
 ```
 
+在树模型写入数据时，timestamp 与 time 均可作为时间列标识用于 INSERT 语句，书写时无需刻意区分；但查询结果中，时间列统一展示为 Time（固定名称），保证结果格式统一。
+
 插入数据后我们可以使用 SELECT 语句简单查询已插入的数据。
 
 ```sql