apache · morningman · May 22, 2026 · May 21, 2026
diff --git a/docs/admin-manual/system-tables/overview.md b/docs/admin-manual/system-tables/overview.md
@@ -1,7 +1,7 @@
 ---
 {
     "title": "Overview | System Tables",
-    "language": "zh-CN",
+    "language": "en",
     "description": "Apache Doris cluster has multiple built-in system databases to store metadata information about the Doris system itself.",
     "sidebar_label": "Overview"
 }

diff --git a/docs/data-operate/import/data-source/local-file.md b/docs/data-operate/import/data-source/local-file.md
@@ -241,7 +241,7 @@ MySQL Load is a synchronous import method. The result is returned to the user on
 The following is the result of a successful import, which returns the number of imported rows:
 
 ```SQL
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/docs/data-operate/import/import-way/mysql-load-manual.md b/docs/data-operate/import/import-way/mysql-load-manual.md
@@ -123,7 +123,7 @@ MySQL Load is a synchronous import method, so the import result is returned dire
 When the import **succeeds**, the number of imported rows is returned:
 
 ```sql
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/docs/data-operate/transaction.md b/docs/data-operate/transaction.md
@@ -362,7 +362,7 @@ mysql> SELECT * FROM dt3;
 |    1 | Emily    |    25 |
 |    2 | Benjamin |    35 |
 |    3 | Olivia   |    28 |
-|    4 | Alexande |    60 |
+|    4 | Alexander |    60 |
 |    5 | Ava      |    17 |
 |    7 | Sophia   |    32 |
 +------+----------+-------+

diff --git a/docs/data-operate/update/update-of-aggregate-model.md b/docs/data-operate/update/update-of-aggregate-model.md
@@ -21,7 +21,7 @@ This document describes the two update methods that the Doris Aggregate model su
 | Update method | Applicable scenario | Supported load methods | Behavior |
 | --- | --- | --- | --- |
 | Whole-row update | Write a complete row, and merge the new and old values according to each column's aggregate function | Stream Load, Broker Load, Routine Load, Insert Into, and others | The new value and the old value are combined by the aggregate function to produce a new aggregate value |
-| Partial-column update | Update only some columns while the other columns retain their existing aggregate results | See [Partial Column Update](./partial-column-update.md#聚合模型的列更新) | Only the specified columns participate in aggregate merging |
+| Partial-column update | Update only some columns while the other columns retain their existing aggregate results | See [Partial Column Update](./partial-column-update.md#column-update-on-the-aggregate-key-model) | Only the specified columns participate in aggregate merging |
 
 ## Whole-Row Update
 
@@ -40,4 +40,4 @@ No matter at which stage the aggregate value is produced, the result returned to
 
 <!-- Knowledge type: Capability index -->
 
-The Aggregate Key Model supports updating only some columns in the table while the other columns retain their existing aggregate results. For details on table creation, data write examples, and usage notes, see the [Partial Column Update](./partial-column-update.md#聚合模型的列更新) document.
+The Aggregate Key Model supports updating only some columns in the table while the other columns retain their existing aggregate results. For details on table creation, data write examples, and usage notes, see the [Partial Column Update](./partial-column-update.md#column-update-on-the-aggregate-key-model) document.
diff --git a/docs/data-operate/update/update-of-unique-model.md b/docs/data-operate/update/update-of-unique-model.md
@@ -40,4 +40,4 @@ Supported load methods include:
 
 <!-- Knowledge type: Capability definition -->
 
-When only some fields need to be updated, you can use the partial column update capability of the Unique model to avoid assembling the full record. For detailed information (including usage examples, flexible partial column updates, and handling of new rows), see the [Column update](./partial-column-update.md#column-update-for-the-unique-model) document.
+When only some fields need to be updated, you can use the partial column update capability of the Unique model to avoid assembling the full record. For detailed information (including usage examples, flexible partial column updates, and handling of new rows), see the [Column update](./partial-column-update.md#column-update-on-the-unique-key-model) document.
diff --git a/docs/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md b/docs/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
@@ -83,7 +83,7 @@ spec:
       memory: 8Gi
 ```
 
-Update the configuration above into the [`DorisDisaggregatedCluster` resource](./install-doris-cluster.md#3-配置-dorisdisaggregatedcluster-资源) to be deployed for it to take effect.
+Update the configuration above into the [`DorisDisaggregatedCluster` resource](./install-doris-cluster.md#2-modify-key-configurations) to be deployed for it to take effect.
 
 ## Scenario 4: Configure the Access Method of a Compute Group
 
@@ -228,7 +228,7 @@ Parameter descriptions:
 
 ### Step 3: Update the DorisDisaggregatedCluster Resource
 
-Update the [`DorisDisaggregatedCluster` resource](./install-doris-cluster.md#3-配置-dorisdisaggregatedcluster-资源) to mount the ConfigMap. The configuration is as follows:
+Update the [`DorisDisaggregatedCluster` resource](./install-doris-cluster.md#2-modify-key-configurations) to mount the ConfigMap. The configuration is as follows:
 
 ```yaml
 spec:

diff --git a/docs/install/deploy-on-kubernetes/separating-storage-compute/config-cluster.md b/docs/install/deploy-on-kubernetes/separating-storage-compute/config-cluster.md
@@ -108,7 +108,7 @@ func main() {
 
 ### Step 2: Configure the encrypted password in fe.conf
 
-Configure the encrypted password from the previous step into `fe.conf` according to the configuration file's requirements. Following the instructions in the [FE startup parameter configuration chapter](config-fe#自定义启动配置), deliver the configuration file to the Kubernetes cluster as a `ConfigMap`.
+Configure the encrypted password from the previous step into `fe.conf` according to the configuration file's requirements. Following the instructions in the [FE startup parameter configuration chapter](config-fe#custom-startup-configuration), deliver the configuration file to the Kubernetes cluster as a `ConfigMap`.
 
 ### Step 3: Configure management credentials in DorisDisaggregatedCluster
 

diff --git a/docs/install/deploy-on-kubernetes/separating-storage-compute/config-ms.md b/docs/install/deploy-on-kubernetes/separating-storage-compute/config-ms.md
@@ -105,7 +105,7 @@ spec:
       memory: 4Gi
 ```
 
-Apply the above configuration to the [DorisDisaggregatedCluster resource you want to deploy](./install-doris-cluster.md#3-配置-dorisdisaggregatedcluster-资源).
+Apply the above configuration to the [DorisDisaggregatedCluster resource you want to deploy](./install-doris-cluster.md#2-modify-key-configurations).
 
 ## 4. Customize startup configuration
 
@@ -175,7 +175,7 @@ Parameter description:
 - `${msConfigMapName}`: the name of the ConfigMap that contains the MetaService startup configuration
 - `mountPath`: the mount point must be `/etc/doris`
 
-Apply the above configuration to the [DorisDisaggregatedCluster resource](./install-doris-cluster.md#3-配置-dorisdisaggregatedcluster-资源) you want to deploy.
+Apply the above configuration to the [DorisDisaggregatedCluster resource](./install-doris-cluster.md#2-modify-key-configurations) you want to deploy.
 
 ## 5. Configure service probe timeouts
 

diff --git a/docs/query-acceleration/tuning/tuning-execution/parallelism-tuning.md b/docs/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
@@ -177,7 +177,7 @@ HASH_JOIN_OPERATOR (id=3 , nereids_id=448):
     - PeakMemoryUsage: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
     - ProbeKeyArena: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
   - OpenTime: avg 2.967us, max 4.120us, min 1.562us
-  - ProbeRows: sum 1.4662330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
+  - ProbeRows: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
   - ProjectionTime: avg 165.392ms, max 169.762ms, min 161.727ms
   - RowsProduced: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
 ```

diff --git a/docs/sql-manual/basic-element/literal/numeric-literal.md b/docs/sql-manual/basic-element/literal/numeric-literal.md
@@ -16,11 +16,11 @@ Doris determines the type used to store integer literals based on the input valu
 
 | Value Range         | Type     |
 | :------------------ | :------- |
-| -2^8 to 2^8 - 1     | TINYINT  |
-| -2^16 to 2^16 - 1   | SMALLINT |
-| -2^32 to 2^32 - 1   | INT      |
-| -2^64 to 2^64 - 1   | BIGINT   |
-| -2^128 to 2^128 - 1 | LARGEINT |
+| -2^7 to 2^7 - 1     | TINYINT  |
+| -2^15 to 2^15 - 1   | SMALLINT |
+| -2^31 to 2^31 - 1   | INT      |
+| -2^63 to 2^63 - 1   | BIGINT   |
+| -2^127 to 2^127 - 1 | LARGEINT |
 
 ## Fixed and Floating Point Numeric Literals
 

diff --git a/docs/sql-manual/basic-element/sql-data-types/conversion/datetime-conversion.md b/docs/sql-manual/basic-element/sql-data-types/conversion/datetime-conversion.md
@@ -8,7 +8,7 @@
 
 Valid range for DATETIME type:
 
-`[0000-01-01 00:00:00.0000000, 9999-12-31 23:59:59.999999]`
+`[0000-01-01 00:00:00.000000, 9999-12-31 23:59:59.999999]`
 
 The DATETIME type includes a type parameter `p`, which represents the number of decimal places. The complete representation is `DATETIME(p)` type. For example, DATETIME(6) indicates a DATETIME type that supports microsecond precision.
 

diff --git a/docs/sql-manual/sql-functions/scalar-functions/array-functions/array-count.md b/docs/sql-manual/sql-functions/scalar-functions/array-functions/array-count.md
@@ -10,7 +10,7 @@
 
 <version since="2.0.0">
 
-
+</version>
 
 ## Description
 

diff --git a/...aurus-plugin-content-docs/current/data-operate/import/data-source/local-file.md b/...aurus-plugin-content-docs/current/data-operate/import/data-source/local-file.md
@@ -241,7 +241,7 @@ MySQL Load 是一种同步的导入方式，导入后结果会在命令行中返
 如下是导入成功的结果显示，会返回导入的行数：
 
 ```SQL
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/...plugin-content-docs/current/data-operate/import/import-way/mysql-load-manual.md b/...plugin-content-docs/current/data-operate/import/import-way/mysql-load-manual.md
@@ -123,7 +123,7 @@ MySQL Load 是一种同步导入方式，导入结果会在命令行中直接返
 **导入成功**时返回导入的行数：
 
 ```sql
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/transaction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/transaction.md
@@ -362,7 +362,7 @@ mysql> SELECT * FROM dt3;
 |    1 | Emily    |    25 |
 |    2 | Benjamin |    35 |
 |    3 | Olivia   |    28 |
-|    4 | Alexande |    60 |
+|    4 | Alexander |    60 |
 |    5 | Ava      |    17 |
 |    7 | Sophia   |    32 |
 +------+----------+-------+

diff --git a/...t-docs/current/query-acceleration/tuning/tuning-execution/parallelism-tuning.md b/...t-docs/current/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
@@ -177,7 +177,7 @@ HASH_JOIN_OPERATOR (id=3 , nereids_id=448):
     - PeakMemoryUsage: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
     - ProbeKeyArena: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
   - OpenTime: avg 2.967us, max 4.120us, min 1.562us
-  - ProbeRows: sum 1.4662330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
+  - ProbeRows: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
   - ProjectionTime: avg 165.392ms, max 169.762ms, min 161.727ms
   - RowsProduced: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
 ```

diff --git a/...rrent/sql-manual/basic-element/sql-data-types/conversion/datetime-conversion.md b/...rrent/sql-manual/basic-element/sql-data-types/conversion/datetime-conversion.md
@@ -8,7 +8,7 @@
 
 DATETIME 类型支持的合法时间上下界：
 
-`[0000-01-01 00:00:00.0000000, 9999-12-31 23:59:59.999999]`
+`[0000-01-01 00:00:00.000000, 9999-12-31 23:59:59.999999]`
 
 DATETIME 类型包含类型参数 `p`，即小数位数。完整表示为 `DATETIME(p)` 类型。例如 DATETIME(6) 表示支持到微秒精度的 DATETIME 类型。
 

diff --git a/...s-plugin-content-docs/version-2.1/data-operate/import/data-source/local-file.md b/...s-plugin-content-docs/version-2.1/data-operate/import/data-source/local-file.md
@@ -1,4 +1,4 @@
 ---
 {
    "title": "本地文件",
    "language": "zh-CN",
@@ -18,7 +18,7 @@

 - **MySQL Load**

 Doris 兼容 MySQL 协议，可以使用 MySQL 标准的 [LOAD DATA](https://dev.mysql.com/doc/refman/8.0/en/load-data.html) 语法导入本地文件。MySQL Load 是一种同步导入方式，执行导入后即返回导入结果，主要适用于导入客户端本地 CSV 文件。更多文档参考[MySQL Load](../import-way/mysql-load-manual.md)。

 ## 使用 Stream Load 导入

@@ -225,6 +225,6 @@
 如下是导入成功的结果显示，会返回导入的行数：
 
 ```SQL
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
diff --git a/...in-content-docs/version-2.1/data-operate/import/import-way/mysql-load-manual.md b/...in-content-docs/version-2.1/data-operate/import/import-way/mysql-load-manual.md
@@ -6,7 +6,7 @@
 }
 ---

 Doris 兼容 MySQL 协议，可以使用 MySQL 标准的 [LOAD DATA](https://dev.mysql.com/doc/refman/8.0/en/load-data.html) 语法导入本地文件。MySQL Load 是一种同步导入方式，执行导入后即返回导入结果。可以通过 LOAD DATA 语句的返回结果判断导入是否成功。一般来说，可以使用 MySQL Load 导入 10GB 以下的文件，如果文件过大，建议将文件进行切分后使用 MySQL Load 进行导入。MySQL Load 可以保证一批导入任务的原子性，要么全部导入成功，要么全部导入失败。

 ## 使用场景

@@ -103,7 +103,7 @@
 如下是导入成功的结果显示，会返回导入的行数：
 
 ```sql
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/...cs/version-2.1/query-acceleration/tuning/tuning-execution/parallelism-tuning.md b/...cs/version-2.1/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
@@ -118,7 +118,7 @@ HASH_JOIN_OPERATOR (id=3 , nereids_id=448):
     - PeakMemoryUsage: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
     - ProbeKeyArena: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
   - OpenTime: avg 2.967us, max 4.120us, min 1.562us
-  - ProbeRows: sum 1.4662330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
+  - ProbeRows: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
   - ProjectionTime: avg 165.392ms, max 169.762ms, min 161.727ms
   - RowsProduced: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
 ```

diff --git a/...s-plugin-content-docs/version-3.x/data-operate/import/data-source/local-file.md b/...s-plugin-content-docs/version-3.x/data-operate/import/data-source/local-file.md
@@ -1,4 +1,4 @@
 ---
 {
    "title": "本地文件",
    "language": "zh-CN",
@@ -18,7 +18,7 @@

 - **MySQL Load**

 Doris 兼容 MySQL 协议，可以使用 MySQL 标准的 [LOAD DATA](https://dev.mysql.com/doc/refman/8.0/en/load-data.html) 语法导入本地文件。MySQL Load 是一种同步导入方式，执行导入后即返回导入结果，主要适用于导入客户端本地 CSV 文件。更多文档参考[MySQL Load](../import-way/mysql-load-manual.md)。

 ## 使用 Stream Load 导入

@@ -225,6 +225,6 @@
 如下是导入成功的结果显示，会返回导入的行数：
 
 ```SQL
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
diff --git a/...in-content-docs/version-3.x/data-operate/import/import-way/mysql-load-manual.md b/...in-content-docs/version-3.x/data-operate/import/import-way/mysql-load-manual.md
@@ -6,7 +6,7 @@
 }
 ---

 Doris 兼容 MySQL 协议，可以使用 MySQL 标准的 [LOAD DATA](https://dev.mysql.com/doc/refman/8.0/en/load-data.html) 语法导入本地文件。MySQL Load 是一种同步导入方式，执行导入后即返回导入结果。可以通过 LOAD DATA 语句的返回结果判断导入是否成功。一般来说，可以使用 MySQL Load 导入 10GB 以下的文件，如果文件过大，建议将文件进行切分后使用 MySQL Load 进行导入。MySQL Load 可以保证一批导入任务的原子性，要么全部导入成功，要么全部导入失败。

 ## 使用场景

@@ -103,7 +103,7 @@
 如下是导入成功的结果显示，会返回导入的行数：
 
 ```sql
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/transaction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/data-operate/transaction.md
@@ -1,4 +1,4 @@
 ---
 {
    "title": "事务",
    "language": "zh-CN",
@@ -52,7 +52,7 @@

 #### StreamLoad 2PC

 [StreamLoad 2PC](#stream-load)，主要用于支持 Flink 写入 Doris 时的 EOS 语义。

 ## 显式事务操作

@@ -362,7 +362,7 @@
 |    1 | Emily    |    25 |
 |    2 | Benjamin |    35 |
 |    3 | Olivia   |    28 |
-|    4 | Alexande |    60 |
+|    4 | Alexander |    60 |
 |    5 | Ava      |    17 |
 |    7 | Sophia   |    32 |
 +------+----------+-------+

diff --git a/...cs/version-3.x/query-acceleration/tuning/tuning-execution/parallelism-tuning.md b/...cs/version-3.x/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
@@ -118,7 +118,7 @@ HASH_JOIN_OPERATOR (id=3 , nereids_id=448):
     - PeakMemoryUsage: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
     - ProbeKeyArena: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
   - OpenTime: avg 2.967us, max 4.120us, min 1.562us
-  - ProbeRows: sum 1.4662330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
+  - ProbeRows: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
   - ProjectionTime: avg 165.392ms, max 169.762ms, min 161.727ms
   - RowsProduced: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
 ```

diff --git a/...s-plugin-content-docs/version-4.x/data-operate/import/data-source/local-file.md b/...s-plugin-content-docs/version-4.x/data-operate/import/data-source/local-file.md
@@ -34,7 +34,7 @@

 - **Stream Load**：通过 HTTP 协议将本地文件或数据流导入 Doris；执行后直接返回导入结果，可通过返回值判断是否成功。
 - **Streamloader**：Doris 官方专用客户端工具，底层基于 Stream Load 实现，支持多文件、多并发导入，可显著降低大数据量导入耗时。
 - **MySQL Load**：兼容 MySQL 标准的 [LOAD DATA](https://dev.mysql.com/doc/refman/8.0/en/load-data.html) 语法，主要适用于通过 MySQL 客户端导入本地 CSV 文件。

 ## 使用 Stream Load 导入

@@ -241,7 +241,7 @@
 如下是导入成功的结果显示，会返回导入的行数：
 
 ```SQL
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/...in-content-docs/version-4.x/data-operate/import/import-way/mysql-load-manual.md b/...in-content-docs/version-4.x/data-operate/import/import-way/mysql-load-manual.md
@@ -1,4 +1,4 @@
 ---
 {
    "title": "MySQL Load",
    "language": "zh-CN",
@@ -19,7 +19,7 @@
 <!-- 知识类型: 操作步骤 + 配置参数 -->
 <!-- 适用场景: 客户端本地 CSV 文件导入 / 程序数据流导入 -->

 Doris 兼容 MySQL 协议，可以使用 MySQL 标准的 [LOAD DATA](https://dev.mysql.com/doc/refman/8.0/en/load-data.html) 语法导入本地文件。MySQL Load 是一种**同步导入方式**，执行导入后即返回导入结果，可以通过 LOAD DATA 语句的返回结果判断导入是否成功。

 一般来说，可以使用 MySQL Load 导入 10GB 以下的文件。如果文件过大，建议先将文件进行切分后再使用 MySQL Load 进行导入。MySQL Load 可以保证一批导入任务的**原子性**，要么全部导入成功，要么全部导入失败。

@@ -123,7 +123,7 @@
 **导入成功**时返回导入的行数：
 
 ```sql
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/transaction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/transaction.md
@@ -52,7 +52,7 @@

 #### StreamLoad 2PC

 [StreamLoad 2PC](#stream-load)，主要用于支持 Flink 写入 Doris 时的 EOS 语义。

 ## 显式事务操作

@@ -362,7 +362,7 @@
 |    1 | Emily    |    25 |
 |    2 | Benjamin |    35 |
 |    3 | Olivia   |    28 |
-|    4 | Alexande |    60 |
+|    4 | Alexander |    60 |
 |    5 | Ava      |    17 |
 |    7 | Sophia   |    32 |
 +------+----------+-------+

diff --git a/...cs/version-4.x/query-acceleration/tuning/tuning-execution/parallelism-tuning.md b/...cs/version-4.x/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
@@ -177,7 +177,7 @@ HASH_JOIN_OPERATOR (id=3 , nereids_id=448):
     - PeakMemoryUsage: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
     - ProbeKeyArena: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
   - OpenTime: avg 2.967us, max 4.120us, min 1.562us
-  - ProbeRows: sum 1.4662330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
+  - ProbeRows: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
   - ProjectionTime: avg 165.392ms, max 169.762ms, min 161.727ms
   - RowsProduced: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
 ```

diff --git a/...n-4.x/sql-manual/basic-element/sql-data-types/conversion/datetime-conversion.md b/...n-4.x/sql-manual/basic-element/sql-data-types/conversion/datetime-conversion.md
@@ -8,7 +8,7 @@
 
 DATETIME 类型支持的合法时间上下界：
 
-`[0000-01-01 00:00:00.0000000, 9999-12-31 23:59:59.999999]`
+`[0000-01-01 00:00:00.000000, 9999-12-31 23:59:59.999999]`
 
 DATETIME 类型包含类型参数 `p`，即小数位数。完整表示为 `DATETIME(p)` 类型。例如 DATETIME(6) 表示支持到微秒精度的 DATETIME 类型。
 
@@ -157,7 +157,7 @@

     * `ZULU`：+00:00

  3. 长格式时区名：IANA 管理的 [Timezone Database](https://www.iana.org/time-zones) 包含的所有合法时区名，如 `Europe/Paris`，`Etc/GMT+2` 等，不区分大小写。

     * 时区名的可用性，详情见于[时区](../../../../admin-manual/cluster-management/time-zone)文档。

@@ -348,7 +348,7 @@

     * `ZULU`：+00:00

  3. 长格式时区名：IANA 管理的 [Timezone Database](https://www.iana.org/time-zones) 包含的所有合法时区名，如 `Europe/Paris`，`Etc/GMT+2` 等，不区分大小写。

     * 时区名的可用性，详情见于[时区](../../../../admin-manual/cluster-management/time-zone)文档。

@@ -486,7 +486,7 @@
 | `20150102030405.123456`      | `2015-01-02 03:04:05.123456` | 14 位数字 + 小数       |
 | `20151231235959.99999999999` | `2016-01-01 00:00:00.000000` | 14 位数字，小数合法，进位到年  |
 | `1000`                       | NULL                         | 2000-10-00 中的日不合法 |
 | `-123.123`                   | NULL                         | 负数时间无法得到合法日期      |

 ## From Datelike Types


diff --git a/versioned_docs/version-2.1/admin-manual/system-tables/overview.md b/versioned_docs/version-2.1/admin-manual/system-tables/overview.md
@@ -1,9 +1,9 @@
 ---
 {
     "title": "Overview | System Tables",
-    "language": "zh-CN",
+    "language": "en",
     "description": "Apache Doris cluster has multiple built-in system databases to store metadata information about the Doris system itself.",
     "sidebar_label": "Overview"
 }
 ---


diff --git a/versioned_docs/version-2.1/data-operate/import/data-source/local-file.md b/versioned_docs/version-2.1/data-operate/import/data-source/local-file.md
@@ -18,7 +18,7 @@

 ### 3. MySQL Load

 Doris is compatible with MySQL protocol and supports using the standard [LOAD DATA](https://dev.mysql.com/doc/refman/8.0/en/load-data.html) syntax to load local files, suitable for loading CSV files.

 ## Using Stream Load to Load Data

@@ -164,6 +164,6 @@
 If the load is successful, the result will be displayed as follows:
 
 ```SQL
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
diff --git a/versioned_docs/version-2.1/data-operate/import/import-way/mysql-load-manual.md b/versioned_docs/version-2.1/data-operate/import/import-way/mysql-load-manual.md
@@ -6,7 +6,7 @@
 }
 ---

 Apache Doris is compatible with the MySQL protocol and supports the use of the standard MySQL [LOAD DATA](https://dev.mysql.com/doc/refman/8.0/en/load-data.html) syntax to import local files. MySQL Load is a synchronous import method where the import result is returned upon completion. That means users can tell whether the import suceeds from the returned result. Generally, the MySQL Load method can be used to ingest files smaller than 10GB in size. For files larger than 10GB, it is recommended to split them into smaller ones. MySQL Load ensures the atomicity of a batch of import tasks, meaning that either all imports succeed or all imports fail.

 ## Applicable scenarios

@@ -99,7 +99,7 @@
 Below is an example of a successful import result, which returns the number of imported rows:
 
 ```SQL
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/...cs/version-2.1/query-acceleration/tuning/tuning-execution/parallelism-tuning.md b/...cs/version-2.1/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
@@ -118,7 +118,7 @@ HASH_JOIN_OPERATOR (id=3, nereids_id=448):
                   - PeakMemoryUsage: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
                   - ProbeKeyArena: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
                 - OpenTime: avg 2.967us, max 4.120us, min 1.562us
-                - ProbeRows: sum 1.4662330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
+                - ProbeRows: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
                 - ProjectionTime: avg 165.392ms, max 169.762ms, min 161.727ms
                 - RowsProduced: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
 ```

diff --git a/versioned_docs/version-2.1/sql-manual/basic-element/literal/numeric-literal.md b/versioned_docs/version-2.1/sql-manual/basic-element/literal/numeric-literal.md
@@ -16,11 +16,11 @@ Doris determines the type used to store integer literals based on the input valu
 
 | Value Range         | Type     |
 | :------------------ | :------- |
-| -2^8 to 2^8 - 1     | TINYINT  |
-| -2^16 to 2^16 - 1   | SMALLINT |
-| -2^32 to 2^32 - 1   | INT      |
-| -2^64 to 2^64 - 1   | BIGINT   |
-| -2^128 to 2^128 - 1 | LARGEINT |
+| -2^7 to 2^7 - 1     | TINYINT  |
+| -2^15 to 2^15 - 1   | SMALLINT |
+| -2^31 to 2^31 - 1   | INT      |
+| -2^63 to 2^63 - 1   | BIGINT   |
+| -2^127 to 2^127 - 1 | LARGEINT |
 
 ## Fixed and Floating Point Numeric Literals
 

diff --git a/versioned_docs/version-3.x/admin-manual/system-tables/overview.md b/versioned_docs/version-3.x/admin-manual/system-tables/overview.md
@@ -1,9 +1,9 @@
 ---
 {
     "title": "Overview | System Tables",
-    "language": "zh-CN",
+    "language": "en",
     "description": "Apache Doris cluster has multiple built-in system databases to store metadata information about the Doris system itself.",
     "sidebar_label": "Overview"
 }
 ---


diff --git a/versioned_docs/version-3.x/data-operate/import/data-source/local-file.md b/versioned_docs/version-3.x/data-operate/import/data-source/local-file.md
@@ -164,6 +164,6 @@ LINES TERMINATED BY '\n';
 If the load is successful, the result will be displayed as follows:
 
 ```SQL
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
diff --git a/versioned_docs/version-3.x/data-operate/import/import-way/mysql-load-manual.md b/versioned_docs/version-3.x/data-operate/import/import-way/mysql-load-manual.md
@@ -99,7 +99,7 @@ MySQL Load is a synchronous import method, and the results of the import are ret
 Below is an example of a successful import result, which returns the number of imported rows:
 
 ```SQL
-Query OK, 6 row affected (0.17 sec)
+Query OK, 6 rows affected (0.17 sec)
 Records: 6  Deleted: 0  Skipped: 0  Warnings: 0
 ```
 

diff --git a/versioned_docs/version-3.x/data-operate/transaction.md b/versioned_docs/version-3.x/data-operate/transaction.md
@@ -55,7 +55,7 @@

 #### StreamLoad 2PC

 [StreamLoad 2PC](#stream-load) is mainly used to support exactly-once semantics (EOS) when writing to Doris with Flink.

 ## Transaction Operations

@@ -367,7 +367,7 @@
 |    1 | Emily    |    25 |
 |    2 | Benjamin |    35 |
 |    3 | Olivia   |    28 |
-|    4 | Alexande |    60 |
+|    4 | Alexander |    60 |
 |    5 | Ava      |    17 |
 |    7 | Sophia   |    32 |
 +------+----------+-------+

diff --git a/...cs/version-3.x/query-acceleration/tuning/tuning-execution/parallelism-tuning.md b/...cs/version-3.x/query-acceleration/tuning/tuning-execution/parallelism-tuning.md
@@ -121,7 +121,7 @@ HASH_JOIN_OPERATOR (id=3, nereids_id=448):
                   - PeakMemoryUsage: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
                   - ProbeKeyArena: sum 1.16 MB, avg 148.00 KB, max 148.00 KB, min 148.00 KB
                 - OpenTime: avg 2.967us, max 4.120us, min 1.562us
-                - ProbeRows: sum 1.4662330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
+                - ProbeRows: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
                 - ProjectionTime: avg 165.392ms, max 169.762ms, min 161.727ms
                 - RowsProduced: sum 1.462330332B (1462330332), avg 182.791291M (182791291), max 182.811875M (182811875), min 182.782658M (182782658)
 ```
Original file line number	Diff line number	Diff line change
Expand Up		@@ -40,4 +40,4 @@ Supported load methods include:

		<!-- Knowledge type: Capability definition -->

		When only some fields need to be updated, you can use the partial column update capability of the Unique model to avoid assembling the full record. For detailed information (including usage examples, flexible partial column updates, and handling of new rows), see the [Column update](./partial-column-update.md#column-update-for-the-unique-model) document.
		When only some fields need to be updated, you can use the partial column update capability of the Unique model to avoid assembling the full record. For detailed information (including usage examples, flexible partial column updates, and handling of new rows), see the [Column update](./partial-column-update.md#column-update-on-the-unique-key-model) document.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -10,7 +10,7 @@

		<version since="2.0.0">


		</version>

		## Description

Expand Down