(doris-website) branch master updated: [fix] correct cluster-management, data-governance, load/query/database/function statement doc errors (#3716)

Wed, 20 May 2026 22:03:44 -0700 

This is an automated email from the ASF dual-hosted git repository.

morningman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 19a3e399b9a [fix] correct cluster-management, data-governance, 
load/query/database/function statement doc errors (#3716)
19a3e399b9a is described below

commit 19a3e399b9a76b4adcc6f88f578c6877f6c8b80e
Author: boluor <[email protected]>
AuthorDate: Wed May 20 22:03:31 2026 -0700

    [fix] correct cluster-management, data-governance, 
load/query/database/function statement doc errors (#3716)
    
    ## Summary
    
    Fixes 25 small documentation issues across cluster-management,
    data-governance, DML, load-and-export, data-query, database, and
    function SQL-statement docs. Each item below is independent.
    
    ### cluster-management
    
    - **MODIFY-BACKEND.md** — table headers `属性` / `影响` were Chinese in the
    English doc; replaced with `Property` / `Effect`.
    - **MODIFY-FRONTEND-HOSTNAME.md** — typo `NOD_PRIV` → `NODE_PRIV`.
    - **ADD-FOLLOWER.md / ADD-OBSERVER.md / DROP-FOLLOWER.md /
    DROP-OBSERVER.md** — a usage note read `use[\`SHOW
    FRONTENDS\`](./SHOW-FRONTENDS.md)command` with no spaces around the
    markdown link; DROP-FOLLOWER also dropped the verb "use". Rewritten with
    proper spacing.
    - **DROP-BROKER.md** — SQL example ended with `.` instead of `;`.
    - **ALTER-STORAGE-POLICY.md** — typo `PROPERTIE` → `PROPERTIES` in the
    syntax block and the inline reference.
    - **ALTER-STORAGE-VAULT.md** — text said the listed hdfs property fields
    were "prohibited"; corrected to "allowed" (the list describes properties
    the user *may* set).
    - **CREATE-STORAGE-POLICY.md** — SQL syntax contained full-width `，` and
    `｜` characters; replaced with ASCII.
    - **CANCEL-WARM-UP.md** — syntax requires the `JOB` keyword but the
    example omitted it; example aligned with syntax.
    - **SHOW-CACHE-HOTSPOT.md** — a `:::info` admonition was unclosed (no
    `:::` before the next `## Syntax`).
    
    ### data-governance
    
    - **CREATE-ROW-POLICY.md** — frontmatter `description` and the body
    Description paragraph said "Explain can view the rewritten execution
    plan." (a leftover from the EXPLAIN doc); rewritten to actually describe
    row policies.
    - **CREATE-ROW-POLICY.md** — two example `CREATE ROW POLICY` statements
    used the same name `test_row_policy_3`; renamed the second to
    `test_row_policy_4`.
    - **CREATE-SQL_BLOCK_RULE.md** — example creates rule `test_rule`, but
    the simulated error message echoed `order_analysis_rule`; corrected.
    - **SHOW-SQL_BLOCK_RULE.md** — stray `|` at the end of a
    parameter-description line; two result tables also had misaligned
    borders.
    
    ### DML / load-and-export / data-query / database / function
    
    - **MERGE-INTO.md** — heading `### Duplicate join behavior¶` ended with
    a stray pilcrow `¶`; removed.
    - **SHOW-LAST-INSERT.md** — keywords line `SHOW, LASR ,INSERT` typo
    corrected to `SHOW, LAST, INSERT`. Informal section markers `grammar:` /
    `illustrate:` replaced with canonical `## Syntax` / `## Return Value`
    headings.
    - **CREATE-ROUTINE-LOAD.md** — a frontmatter link pointed at a
    non-existent anchor `#Example-of-importing-Json-format-data`; corrected
    to the actual anchor in each version (`#import-examples` for current /
    3.x / 4.x; `#load-example` for 2.1). Frontmatter `description` was
    truncated mid-sentence; completed.
    - **ALTER-ROUTINE-LOAD.md / PAUSE-ROUTINE-LOAD.md /
    RESUME-ROUTINE-LOAD.md / STOP-ROUTINE-LOAD.md /
    SHOW-CREATE-ROUTINE-LOAD.md** — each file's access-control note read
    "SHOW ROUTINE LOAD requires…" regardless of the actual statement.
    Replaced with the matching statement name in each file.
    - **CANCEL-LOAD.md** — STATE parameter list included `FINISHED` /
    `CANCELLED`, but the syntax + notes only allow `PENDING` / `ETL` /
    `LOADING`; removed the invalid values. An example used `LABEL like
    "example_"` which, without `%`, doesn't match anything containing
    `example_`; changed to `"%example_%"` to match the prose intent.
    - **SHOW-LOAD.md** — prose said `LOAD = "PENDING"` where it should say
    `STATE = "PENDING"`.
    - **SELECT.md** — typo `JOIN Exampel` → `JOIN Example`; truncated `ome
    additional knowledge` → `Some additional knowledge`; invalid SQL `ORDER
    by LIMIT 10` → `ORDER BY a LIMIT 10`; renumbered a duplicated list item
    `2.`.
    - **SHOW-DATABASES.md** — Chinese heading `## 示例` in the English doc →
    `## Examples`.
    - **SHOW-DATABASE-ID.md** — `### Description` (h3) → `## Description`
    (h2), matching the convention used by sibling docs.
    - **DROP-FUNCTION.md** — syntax `DROP [ GLOBAL ] <function_name>(...)`
    was missing the `FUNCTION` keyword.
    
    ## Test plan
    
    - [ ] CI doc build passes
    - [ ] Spot-check the affected pages render correctly (Chinese → English
    headers, link spacing, fixed SQL examples, completed descriptions, h2
    headings, FUNCTION keyword in DROP syntax)
---
 .../instance-management/ADD-FOLLOWER.md            |  2 +-
 .../instance-management/ADD-OBSERVER.md            |  2 +-
 .../instance-management/DROP-BROKER.md             |  2 +-
 .../instance-management/DROP-FOLLOWER.md           |  2 +-
 .../instance-management/DROP-OBSERVER.md           |  2 +-
 .../instance-management/MODIFY-BACKEND.md          |  2 +-
 .../MODIFY-FRONTEND-HOSTNAME.md                    |  2 +-
 .../storage-management/ALTER-STORAGE-POLICY.md     |  4 ++--
 .../storage-management/ALTER-STORAGE-VAULT.md      |  2 +-
 .../storage-management/CANCEL-WARM-UP.md           |  2 +-
 .../storage-management/CREATE-STORAGE-POLICY.md    |  4 ++--
 .../storage-management/SHOW-CACHE-HOTSPOT.md       |  2 +-
 .../data-governance/CREATE-ROW-POLICY.md           |  4 ++--
 .../data-governance/CREATE-SQL_BLOCK_RULE.md       |  2 +-
 .../data-governance/SHOW-SQL_BLOCK_RULE.md         | 24 +++++++++++-----------
 .../data-modification/DML/MERGE-INTO.md            |  2 +-
 .../data-modification/DML/SHOW-LAST-INSERT.md      |  6 +++---
 .../load-and-export/ALTER-ROUTINE-LOAD.md          |  2 +-
 .../load-and-export/CANCEL-LOAD.md                 |  4 ++--
 .../load-and-export/CREATE-ROUTINE-LOAD.md         |  2 +-
 .../load-and-export/PAUSE-ROUTINE-LOAD.md          |  2 +-
 .../load-and-export/RESUME-ROUTINE-LOAD.md         |  2 +-
 .../load-and-export/SHOW-CREATE-ROUTINE-LOAD.md    |  2 +-
 .../data-modification/load-and-export/SHOW-LOAD.md |  2 +-
 .../load-and-export/STOP-ROUTINE-LOAD.md           |  2 +-
 .../sql-manual/sql-statements/data-query/SELECT.md | 14 ++++++-------
 .../sql-statements/database/SHOW-DATABASE-ID.md    |  2 +-
 .../sql-statements/database/SHOW-DATABASES.md      |  2 +-
 .../sql-statements/function/DROP-FUNCTION.md       |  2 +-
 .../instance-management/ADD-FOLLOWER.md            |  2 +-
 .../instance-management/ADD-OBSERVER.md            |  2 +-
 .../instance-management/DROP-BROKER.md             |  2 +-
 .../instance-management/DROP-FOLLOWER.md           |  2 +-
 .../instance-management/DROP-OBSERVER.md           |  2 +-
 .../instance-management/MODIFY-BACKEND.md          |  2 +-
 .../MODIFY-FRONTEND-HOSTNAME.md                    |  2 +-
 .../storage-management/ALTER-STORAGE-POLICY.md     |  4 ++--
 .../storage-management/CREATE-STORAGE-POLICY.md    |  4 ++--
 .../data-governance/CREATE-ROW-POLICY.md           |  4 ++--
 .../data-governance/CREATE-SQL_BLOCK_RULE.md       |  2 +-
 .../data-governance/SHOW-SQL_BLOCK_RULE.md         | 24 +++++++++++-----------
 .../data-modification/DML/SHOW-LAST-INSERT.md      |  6 +++---
 .../load-and-export/ALTER-ROUTINE-LOAD.md          |  2 +-
 .../load-and-export/CANCEL-LOAD.md                 |  4 ++--
 .../load-and-export/CREATE-ROUTINE-LOAD.md         |  2 +-
 .../load-and-export/PAUSE-ROUTINE-LOAD.md          |  2 +-
 .../load-and-export/RESUME-ROUTINE-LOAD.md         |  2 +-
 .../load-and-export/SHOW-CREATE-ROUTINE-LOAD.md    |  2 +-
 .../data-modification/load-and-export/SHOW-LOAD.md |  2 +-
 .../load-and-export/STOP-ROUTINE-LOAD.md           |  2 +-
 .../sql-manual/sql-statements/data-query/SELECT.md | 14 ++++++-------
 .../sql-statements/database/SHOW-DATABASE-ID.md    |  2 +-
 .../sql-statements/database/SHOW-DATABASES.md      |  2 +-
 .../sql-statements/function/DROP-FUNCTION.md       |  2 +-
 .../instance-management/ADD-FOLLOWER.md            |  2 +-
 .../instance-management/ADD-OBSERVER.md            |  2 +-
 .../instance-management/DROP-BROKER.md             |  2 +-
 .../instance-management/DROP-FOLLOWER.md           |  2 +-
 .../instance-management/DROP-OBSERVER.md           |  2 +-
 .../instance-management/MODIFY-BACKEND.md          |  2 +-
 .../MODIFY-FRONTEND-HOSTNAME.md                    |  2 +-
 .../storage-management/ALTER-STORAGE-POLICY.md     |  4 ++--
 .../storage-management/ALTER-STORAGE-VAULT.md      |  2 +-
 .../storage-management/CANCEL-WARM-UP.md           |  2 +-
 .../storage-management/CREATE-STORAGE-POLICY.md    |  4 ++--
 .../data-governance/CREATE-ROW-POLICY.md           |  4 ++--
 .../data-governance/CREATE-SQL_BLOCK_RULE.md       |  2 +-
 .../data-governance/SHOW-SQL_BLOCK_RULE.md         | 24 +++++++++++-----------
 .../data-modification/DML/SHOW-LAST-INSERT.md      |  6 +++---
 .../load-and-export/ALTER-ROUTINE-LOAD.md          |  2 +-
 .../load-and-export/CANCEL-LOAD.md                 |  4 ++--
 .../load-and-export/CREATE-ROUTINE-LOAD.md         |  2 +-
 .../load-and-export/PAUSE-ROUTINE-LOAD.md          |  2 +-
 .../load-and-export/RESUME-ROUTINE-LOAD.md         |  2 +-
 .../load-and-export/SHOW-CREATE-ROUTINE-LOAD.md    |  2 +-
 .../data-modification/load-and-export/SHOW-LOAD.md |  2 +-
 .../load-and-export/STOP-ROUTINE-LOAD.md           |  2 +-
 .../sql-manual/sql-statements/data-query/SELECT.md | 14 ++++++-------
 .../sql-statements/database/SHOW-DATABASE-ID.md    |  2 +-
 .../sql-statements/database/SHOW-DATABASES.md      |  2 +-
 .../sql-statements/function/DROP-FUNCTION.md       |  2 +-
 .../instance-management/ADD-FOLLOWER.md            |  2 +-
 .../instance-management/ADD-OBSERVER.md            |  2 +-
 .../instance-management/DROP-BROKER.md             |  2 +-
 .../instance-management/DROP-FOLLOWER.md           |  2 +-
 .../instance-management/DROP-OBSERVER.md           |  2 +-
 .../instance-management/MODIFY-BACKEND.md          |  2 +-
 .../MODIFY-FRONTEND-HOSTNAME.md                    |  2 +-
 .../storage-management/ALTER-STORAGE-POLICY.md     |  4 ++--
 .../storage-management/ALTER-STORAGE-VAULT.md      |  2 +-
 .../storage-management/CANCEL-WARM-UP.md           |  2 +-
 .../storage-management/CREATE-STORAGE-POLICY.md    |  4 ++--
 .../storage-management/SHOW-CACHE-HOTSPOT.md       |  2 +-
 .../data-governance/CREATE-ROW-POLICY.md           |  4 ++--
 .../data-governance/CREATE-SQL_BLOCK_RULE.md       |  2 +-
 .../data-governance/SHOW-SQL_BLOCK_RULE.md         | 24 +++++++++++-----------
 .../data-modification/DML/MERGE-INTO.md            |  2 +-
 .../data-modification/DML/SHOW-LAST-INSERT.md      |  6 +++---
 .../load-and-export/ALTER-ROUTINE-LOAD.md          |  2 +-
 .../load-and-export/CANCEL-LOAD.md                 |  4 ++--
 .../load-and-export/CREATE-ROUTINE-LOAD.md         |  2 +-
 .../load-and-export/PAUSE-ROUTINE-LOAD.md          |  2 +-
 .../load-and-export/RESUME-ROUTINE-LOAD.md         |  2 +-
 .../load-and-export/SHOW-CREATE-ROUTINE-LOAD.md    |  2 +-
 .../data-modification/load-and-export/SHOW-LOAD.md |  2 +-
 .../load-and-export/STOP-ROUTINE-LOAD.md           |  2 +-
 .../sql-manual/sql-statements/data-query/SELECT.md | 14 ++++++-------
 .../sql-statements/database/SHOW-DATABASE-ID.md    |  2 +-
 .../sql-statements/database/SHOW-DATABASES.md      |  2 +-
 .../sql-statements/function/DROP-FUNCTION.md       |  2 +-
 110 files changed, 202 insertions(+), 202 deletions(-)

diff --git 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
index c3cba99e4e6..50cbda04a29 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 1. Before adding a new FOLLOWER node, make sure the node is properly 
configured.
 2. Before adding a FOLLOWER node, ensure that the number of FOLLOWER nodes in 
the cluster is an odd number after the addition.
-3. After adding the FOLLOWER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they have been added 
successfully and are in a normal state.
+3. After adding the FOLLOWER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they have been added 
successfully and are in a normal state.
 
 ## Examples
 
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
index 18a62fc345c..c4119d54e63 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
@@ -37,7 +37,7 @@ The user executing this SQL command must have at least the 
following permissions
 ## Usage Notes
 
 1. Before adding a new OBSERVER node, make sure the node is properly 
configured.
-2. After adding the OBSERVER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they have been added 
successfully and are in a normal state.
+2. After adding the OBSERVER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they have been added 
successfully and are in a normal state.
 
 ## Examples
 
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
index c8e464366ab..47d22272f85 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
@@ -43,7 +43,7 @@ The user who executes this operation needs to have the 
NODE_PRIV permission.
 1. Delete all Brokers
 
     ```sql
-    ALTER SYSTEM DROP ALL BROKER broker_name.
+    ALTER SYSTEM DROP ALL BROKER broker_name;
     ```
 
 2. Delete a specific Broker node
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
index 347099b5bc6..05fb780c481 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 1. Before deleting a FOLLOWER node, make sure that the node that needs to be 
taken offline is not a Master node.
 2. Before deleting a FOLLOWER node, ensure that the number of FOLLOWER nodes 
in the cluster is an odd number after they go offline.
-3. After deleting the FOLLOWER node[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they were successfully 
deleted.
+3. After deleting the FOLLOWER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they were successfully 
deleted.
 
 ## Examples
 
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
index 290ff73750b..933725e379f 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
@@ -36,7 +36,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 ## Usage Notes
 
-1. After deleting the OBSERVER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they were successfully 
deleted.
+1. After deleting the OBSERVER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they were successfully 
deleted.
 
 ## Examples
 
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
index 6f37957475b..69c4c399cf7 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
@@ -10,7 +10,7 @@
 
 This statement is used to modify the attributes of BE nodes. After modifying 
the attributes of BE nodes, it will affect the query, write, and data 
distribution of the current node. The following are the attributes that can be 
modified:
 
-| 属性              | 影响                                                         
                                                                                
                                                                                
                                                                                
                                    |
+| Property        | Effect                                                     
                                                                                
                                                                                
                                                                                
                                        |
 
|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `tag.location`  | The resource tag of the BE, with the `default` value being 
default. After modification, it will affect the data balancing of BEs within 
the same tag group and the BE nodes for data distribution during table 
creation. For more information, please refer to[Resource 
Group](../../../../admin-manual/workload-management/resource-group.md) |
 | `disable_query` | Whether to disable queries, with the default value being 
`false`. After setting it to `true`, no new query requests will be scheduled to 
this BE node.                                                                   
                                                                                
                                      |
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
index 0ff4aba66e8..a6e1d84d46f 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
@@ -29,7 +29,7 @@ ALTER SYSTEM MODIFY FRONTEND "<frontend_hostname_port>" 
HOSTNAME "<frontend_new_
 
 ## Access Control Requirements
 
-The user executing this SQL command must have at least NOD_PRIV permissions.
+The user executing this SQL command must have at least NODE_PRIV permissions.
 
 ## Examples
 
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
index 9dc248bd8de..a382e6f9eb4 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
@@ -12,7 +12,7 @@ This statement is used to modify an existing hot-cold tiered 
migration policy. O
 
 ## Syntax
 ```sql
-ALTER STORAGE POLICY  '<policy_name>' PROPERTIE ("<key>"="<value>"[, ... ]);
+ALTER STORAGE POLICY  '<policy_name>' PROPERTIES ("<key>"="<value>"[, ... ]);
 ```
 
 ## Required Parameters
@@ -22,7 +22,7 @@ ALTER STORAGE POLICY  '<policy_name>' PROPERTIE 
("<key>"="<value>"[, ... ]);
 > The name of the storage policy. This is the unique identifier of the storage 
 > policy you want to modify, and an existing policy name must be specified. 
 
 ## Optional Parameters
-`PROPERTIE ("<key>"="<value>"[, ... ])` 
+`PROPERTIES ("<key>"="<value>"[, ... ])` 
 
 1.`retention_days`  
 > Data retention period. Defines the duration for which the data is kept in 
 > storage. Data exceeding this period will be automatically deleted. 
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
index 4235d215ba2..4aca5409f13 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
@@ -30,7 +30,7 @@ PROPERTIES (<storage_vault_property>)
 >- vault_name: The name of the vault. When a vault is set as the default 
 >storage vault using the statement `SET <original_vault_name> DEFAULT STORAGE 
 >VAULT`, its name cannot be modified. To rename the vault, you must first 
 >unset the default storage vault by executing the `UNSET DEFAULT STORAGE 
 >VAULT` command, and then modify its name. Finally, if you need to set the 
 >renamed vault as the default storage vault, you can use the statement `SET 
 ><new_vault_name> DEFAULT STORAGE VAULT`.
 >- use_path_style: Whether to allow path style url, optional values are true, 
 >false. The default value is false.
 
->When type is hdfs, the following fields are prohibited:
+>When type is hdfs, the allowed property fields are as follows:
 >
 >- path_prefix: Storage path prefix
 >- fs.defaultFS: hdfs name
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
index 2de42f558d6..1fadc5e3046 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
@@ -44,7 +44,7 @@ Its result is:
 Then terminate it through `CANCEL WARM UP`:
 
 ```C++
-CANCEL WARM UP WHERE id = 90290165739458;
+CANCEL WARM UP JOB WHERE id = 90290165739458;
 ```
 
 If the following content is returned, it indicates that the warm-up job 
corresponding to the specified id does not exist:
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
index ed68a41beac..c303b644d0e 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
@@ -16,8 +16,8 @@ To create a storage policy, you must first create a storage 
resource, and then a
 CREATE STORAGE POLICY <policy_name>
 PROPERTIES(
     "storage_resource" = "<storage_resource_name>"
-    [{， "cooldown_datetime" = "<cooldown_datetime>"
-    ｜ ， "cooldown_ttl" = "<cooldown_ttl>"}]
+    [{, "cooldown_datetime" = "<cooldown_datetime>"
+    | , "cooldown_ttl" = "<cooldown_ttl>"}]
 );
 ```
 
diff --git 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/SHOW-CACHE-HOTSPOT.md
 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/SHOW-CACHE-HOTSPOT.md
index e313ac9c780..34a9f637632 100644
--- 
a/docs/sql-manual/sql-statements/cluster-management/storage-management/SHOW-CACHE-HOTSPOT.md
+++ 
b/docs/sql-manual/sql-statements/cluster-management/storage-management/SHOW-CACHE-HOTSPOT.md
@@ -15,7 +15,7 @@ This statement is used to display the hotspot information of 
the file cache.
 
 Before version 3.0.4, you could use the `SHOW CACHE HOTSPOT` statement to 
query cache hotspot information statistics. Starting from version 3.0.4, the 
use of the `SHOW CACHE HOTSPOT` statement for cache hotspot information 
statistics is no longer supported. Please directly access the system table 
`__internal_schema.cloud_cache_hotspot` for queries. For detailed usage, refer 
to [MANAGING FILE 
CACHE](../../../../compute-storage-decoupled/file-cache/file-cache).
 
-
+:::
 
 ## Syntax
 
diff --git 
a/docs/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md 
b/docs/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
index 061969cbbeb..b4494b51399 100644
--- a/docs/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
+++ b/docs/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
@@ -2,13 +2,13 @@
 {
     "title": "CREATE ROW POLICY",
     "language": "en",
-    "description": "Explain can view the rewritten execution plan."
+    "description": "Creates a row-level security policy on a table to restrict 
the rows returned to specified users or roles."
 }
 ---
 
 ## Description
 
-Explain can view the rewritten execution plan. 
+Creates a row-level security policy on a table. The policy restricts the rows 
that specified users or roles can see by attaching a filter predicate that is 
applied to queries against the table. 
 
 ## Syntax
 
diff --git 
a/docs/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md 
b/docs/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
index 7c2d724c172..610e1bd60a0 100644
--- a/docs/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
+++ b/docs/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
@@ -81,7 +81,7 @@ The user executing this SQL command must have at least the 
following permissions
 
    ```sql
    mysql> select * from order_analysis;
-   ERROR 1064 (HY000): errCode = 2, detailMessage = sql match regex sql block 
rule: order_analysis_rule
+   ERROR 1064 (HY000): errCode = 2, detailMessage = sql match regex sql block 
rule: test_rule
    ```
 
 2. Create a rule that prevents scanning more than 30 partitions of the same 
table and restricts the query data volume to no more than 10 billion rows
diff --git 
a/docs/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md 
b/docs/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
index e57a06de5fd..e233d783b12 100644
--- a/docs/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
+++ b/docs/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
@@ -18,7 +18,7 @@ SHOW SQL_BLOCK_RULE [FOR <rule_name>];
 
 `<rule_name>`
 
-The name of the SQL blocking rule to display. If omitted, all rules will be 
shown. |
+The name of the SQL blocking rule to display. If omitted, all rules will be 
shown.
 
 ## Access Control Requirements  
 
@@ -36,12 +36,12 @@ SHOW SQL_BLOCK_RULE;
 ```
 
 ```text
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
-| Name       | Sql                        | SqlHash | PartitionNum | TabletNum 
 | Cardinality | Global | Enable |
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
-| test_rule  | select * from order_analysis | NULL    | 0           | 0        
  | 0           | true   | true   |
-| test_rule2 | NULL                        | NULL    | 30          | 0         
 | 10000000000 | false  | true   |
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
+| Name       | Sql                          | SqlHash | PartitionNum | 
TabletNum | Cardinality | Global | Enable |
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
+| test_rule  | select * from order_analysis | NULL    | 0            | 0       
  | 0           | true   | true   |
+| test_rule2 | NULL                         | NULL    | 30           | 0       
  | 10000000000 | false  | true   |
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
 ```
 
 2. Display a specific SQL blocking rule  
@@ -50,9 +50,9 @@ SHOW SQL_BLOCK_RULE FOR test_rule2;
 ```
 
 ```text
-+------------+------+---------+-------------+------------+-------------+--------+--------+
-| Name       | Sql  | SqlHash | PartitionNum | TabletNum  | Cardinality | 
Global | Enable |
-+------------+------+---------+-------------+------------+-------------+--------+--------+
-| test_rule2 | NULL | NULL    | 30          | 0          | 10000000000 | false 
 | true   |
-+------------+------+---------+-------------+------------+-------------+--------+--------+
++------------+------+---------+--------------+-----------+-------------+--------+--------+
+| Name       | Sql  | SqlHash | PartitionNum | TabletNum | Cardinality | 
Global | Enable |
++------------+------+---------+--------------+-----------+-------------+--------+--------+
+| test_rule2 | NULL | NULL    | 30           | 0         | 10000000000 | false 
 | true   |
++------------+------+---------+--------------+-----------+-------------+--------+--------+
 ```
diff --git a/docs/sql-manual/sql-statements/data-modification/DML/MERGE-INTO.md 
b/docs/sql-manual/sql-statements/data-modification/DML/MERGE-INTO.md
index 1889950e735..0b740af7c1e 100644
--- a/docs/sql-manual/sql-statements/data-modification/DML/MERGE-INTO.md
+++ b/docs/sql-manual/sql-statements/data-modification/DML/MERGE-INTO.md
@@ -112,7 +112,7 @@ The 
[user](../../../../admin-manual/auth/authentication-and-authorization.md) ex
 - A single MERGE statement can include multiple matching and not-matching 
clauses (that is, WHEN MATCHED ... and WHEN NOT MATCHED ...).
 - Any matching or not-matching clause that omits the AND subclause (default 
behavior) must be the last of its clause type in the statement (for example, a 
WHEN MATCHED ... clause can’t be followed by a WHEN MATCHED AND ... clause). 
Doing so results in an unreachable case, which returns an error.
 
-### Duplicate join behavior¶
+### Duplicate join behavior
 
 Currently, Doris does not detect whether duplicate join rows occur. If they 
do, the behavior is undefined.
 
diff --git 
a/docs/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md 
b/docs/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
index 0b4a1bb5952..12470e49522 100644
--- a/docs/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
+++ b/docs/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
@@ -10,7 +10,7 @@
 
 This syntax is used to view the result of the latest insert operation in the 
current session connection
 
-grammar:
+## Syntax
 
 ```sql
 SHOW LAST INSERT
@@ -28,7 +28,7 @@ TransactionStatus: VISIBLE
       FilteredRows: 0
 ```
 
-illustrate:
+## Return Value
 
 * TransactionId: transaction id
 * Label: the label corresponding to the insert task
@@ -47,7 +47,7 @@ illustrate:
 
 ## Keywords
 
-    SHOW, LASR ,INSERT
+    SHOW, LAST, INSERT
 
 ## Best Practice
 
diff --git 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
index 091c7d9a737..007a3ce4821 100644
--- 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
+++ 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
@@ -70,7 +70,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | ALTER ROUTINE LOAD requires LOAD privilege on the table |
 
 ## Notes
 
diff --git 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
index fa366e4ab09..7c3a33edfd6 100644
--- 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
+++ 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
@@ -34,7 +34,7 @@ WHERE [LABEL = "<load_label>" | LABEL like "<label_pattern>" 
| STATE = { "PENDIN
 
 > If `LABEL LIKE "<label_pattern>"` is used, it matches import tasks whose 
 > labels contain the `label_pattern`.
 
-**3. STATE = { " PENDING " | " ETL " | " LOADING " | " FINISHED " | " 
CANCELLED " }**
+**3. STATE = { " PENDING " | " ETL " | " LOADING " }**
 
 > Specifying `PENDING` means cancelling jobs with the `STATE = "PENDING"` 
 > status. The same applies to other statuses.
 
@@ -67,7 +67,7 @@ Users executing this SQL command must have at least the 
following permissions:
    ```sql
    CANCEL LOAD
    FROM example_db
-   WHERE LABEL like "example_";
+   WHERE LABEL like "%example_%";
    ```
 
 3. Cancel import jobs in the `LOADING` state.
diff --git 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
index 24a09dcc8cb..ccf11563602 100644
--- 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
+++ 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
@@ -10,7 +10,7 @@
 
 The Routine Load feature allows users to submit a resident import task that 
continuously reads data from a specified data source and imports it into Doris.
 
-Currently, it only supports importing CSV or Json format data from Kafka 
through unauthenticated or SSL authentication methods. [Example of importing 
Json format 
data](../../../../data-operate/import/import-way/routine-load-manual.md#Example-of-importing-Json-format-data)
+Currently, it only supports importing CSV or Json format data from Kafka 
through unauthenticated or SSL authentication methods. [Example of importing 
Json format 
data](../../../../data-operate/import/import-way/routine-load-manual.md#import-examples)
 
 ## Syntax
 
diff --git 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
index b2e71e4ccd8..7ba0f88e314 100644
--- 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
+++ 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
@@ -34,7 +34,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | PAUSE ROUTINE LOAD requires LOAD privilege on the table |
 
 ## Notes
 
diff --git 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
index 1e1215a44d2..b014ffd9f4d 100644
--- 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
+++ 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
@@ -34,7 +34,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | RESUME ROUTINE LOAD requires LOAD privilege on the table 
|
 
 ## Notes
 
diff --git 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
index 28208ed27ff..108ff6f695f 100644
--- 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
+++ 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
@@ -36,7 +36,7 @@ Users executing this SQL command must have at least the 
following permission:
 
 | Privilege  | Object | Notes                                                  
  |
 | :--------- | :----- | 
:------------------------------------------------------- |
-| LOAD_PRIV  | Table  | SHOW ROUTINE LOAD requires LOAD permission on the 
table |
+| LOAD_PRIV  | Table  | SHOW CREATE ROUTINE LOAD requires LOAD permission on 
the table |
 
 ## Examples
 
diff --git 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
index 6e007f19901..d59fc33a185 100644
--- 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
+++ 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
@@ -40,7 +40,7 @@ SHOW LOAD
 
 **4. STATE = { " PENDING " | " ETL " | " LOADING " | " FINISHED " | " 
CANCELLED " }**
 
-> Specifying `PENDING` means matching jobs with the `LOAD = "PENDING"` status. 
The same applies to other status keywords.
+> Specifying `PENDING` means matching jobs with the `STATE = "PENDING"` 
status. The same applies to other status keywords.
 
 **5. `<col_name>`**
 
diff --git 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
index bf8b790f2e8..f47bdafff1d 100644
--- 
a/docs/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
+++ 
b/docs/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
@@ -31,7 +31,7 @@ Users executing this SQL command must have at least the 
following permission:
 
 | Privilege  | Object | Notes                                                  
  |
 | :--------- | :----- | 
:------------------------------------------------------- |
-| LOAD_PRIV  | Table  | SHOW ROUTINE LOAD requires LOAD permission on the 
table |
+| LOAD_PRIV  | Table  | STOP ROUTINE LOAD requires LOAD permission on the 
table |
 
 ## Notes
 
diff --git a/docs/sql-manual/sql-statements/data-query/SELECT.md 
b/docs/sql-manual/sql-statements/data-query/SELECT.md
index 8c9fae32f4e..eb1d82dd99e 100644
--- a/docs/sql-manual/sql-statements/data-query/SELECT.md
+++ b/docs/sql-manual/sql-statements/data-query/SELECT.md
@@ -210,9 +210,9 @@ Recursive CTE is currently not supported.
 10. UNION Example
 
     ```sql
-    SELECT a FROM t1 WHERE a = 10 AND B = 1 ORDER by LIMIT 10
+    SELECT a FROM t1 WHERE a = 10 AND B = 1 ORDER BY a LIMIT 10
     UNION
-    SELECT a FROM t2 WHERE a = 11 AND B = 2 ORDER by LIMIT 10;
+    SELECT a FROM t2 WHERE a = 11 AND B = 2 ORDER BY a LIMIT 10;
     ```
 
 11. WITH clause example
@@ -227,7 +227,7 @@ Recursive CTE is currently not supported.
     SELECT col1, col2 FROM cte;
     ```
 
-12. JOIN Exampel
+12. JOIN Example
 
     ```sql
     SELECT * FROM t1 LEFT JOIN (t2, t3, t4)
@@ -284,7 +284,7 @@ Recursive CTE is currently not supported.
 
 ## Best Practice
 
-1. ome additional knowledge about the SELECT clause
+1. Some additional knowledge about the SELECT clause
 
    - An alias can be specified for select_expr using AS alias_name. Aliases 
are used as column names in expressions and can be used in GROUP BY, ORDER BY 
or HAVING clauses. The AS keyword is a good habit to use when specifying 
aliases for columns.
 
@@ -356,17 +356,17 @@ Recursive CTE is currently not supported.
 
      DISTINCT removes duplicate rows.
 
-2. The main advantage of subqueries
+3. The main advantage of subqueries
 
     - Subqueries allow structured queries so that each part of a statement can 
be isolated.
     - Some operations require complex unions and associations. Subqueries 
provide other ways to perform these operations
 
-3. Speed up queries
+4. Speed up queries
 
     - Use Doris's partition and bucket as data filtering conditions as much as 
possible to reduce the scope of data scanning
     - Make full use of Doris's prefix index fields as data filter conditions 
to speed up query speed
     
-4. UNION
+5. UNION
 
    - Using only the union keyword has the same effect as using union disitnct. 
Since the deduplication work is more memory-intensive, the query speed using 
the union all operation will be faster and the memory consumption will be less. 
If users want to perform order by and limit operations on the returned result 
set, they need to put the union operation in the subquery, then select from 
subquery, and finally put the subquery and order by outside the subquery.
    
diff --git a/docs/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md 
b/docs/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
index f0e3e78eb17..d84fc76d5cf 100644
--- a/docs/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
+++ b/docs/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
@@ -6,7 +6,7 @@
 }
 ---
 
-### Description
+## Description
 
 This statement is used to find the corresponding database name based on the 
database id (only used by administrators)
 
diff --git a/docs/sql-manual/sql-statements/database/SHOW-DATABASES.md 
b/docs/sql-manual/sql-statements/database/SHOW-DATABASES.md
index 1d695b9a327..6a255afae56 100644
--- a/docs/sql-manual/sql-statements/database/SHOW-DATABASES.md
+++ b/docs/sql-manual/sql-statements/database/SHOW-DATABASES.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 |:-----------|:------|:---------------|
 | SELECT_PRIV | Corresponding database | Requires read permission on the 
corresponding database |
 
-## 示例
+## Examples
 
 - Displays the names of all current databases.
 
diff --git a/docs/sql-manual/sql-statements/function/DROP-FUNCTION.md 
b/docs/sql-manual/sql-statements/function/DROP-FUNCTION.md
index 40cb22b55f1..70a6b6c78e0 100644
--- a/docs/sql-manual/sql-statements/function/DROP-FUNCTION.md
+++ b/docs/sql-manual/sql-statements/function/DROP-FUNCTION.md
@@ -13,7 +13,7 @@ Delete a custom function.
 ## Syntax
 
 ```sql
-DROP [ GLOBAL ] <function_name> ( <arg_type> )
+DROP [ GLOBAL ] FUNCTION <function_name> ( <arg_type> )
 ```
 
 ## Required Parameters
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
index c3cba99e4e6..50cbda04a29 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 1. Before adding a new FOLLOWER node, make sure the node is properly 
configured.
 2. Before adding a FOLLOWER node, ensure that the number of FOLLOWER nodes in 
the cluster is an odd number after the addition.
-3. After adding the FOLLOWER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they have been added 
successfully and are in a normal state.
+3. After adding the FOLLOWER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they have been added 
successfully and are in a normal state.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
index 18a62fc345c..c4119d54e63 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
@@ -37,7 +37,7 @@ The user executing this SQL command must have at least the 
following permissions
 ## Usage Notes
 
 1. Before adding a new OBSERVER node, make sure the node is properly 
configured.
-2. After adding the OBSERVER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they have been added 
successfully and are in a normal state.
+2. After adding the OBSERVER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they have been added 
successfully and are in a normal state.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
index c8e464366ab..47d22272f85 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
@@ -43,7 +43,7 @@ The user who executes this operation needs to have the 
NODE_PRIV permission.
 1. Delete all Brokers
 
     ```sql
-    ALTER SYSTEM DROP ALL BROKER broker_name.
+    ALTER SYSTEM DROP ALL BROKER broker_name;
     ```
 
 2. Delete a specific Broker node
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
index 347099b5bc6..05fb780c481 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 1. Before deleting a FOLLOWER node, make sure that the node that needs to be 
taken offline is not a Master node.
 2. Before deleting a FOLLOWER node, ensure that the number of FOLLOWER nodes 
in the cluster is an odd number after they go offline.
-3. After deleting the FOLLOWER node[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they were successfully 
deleted.
+3. After deleting the FOLLOWER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they were successfully 
deleted.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
index 290ff73750b..933725e379f 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
@@ -36,7 +36,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 ## Usage Notes
 
-1. After deleting the OBSERVER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they were successfully 
deleted.
+1. After deleting the OBSERVER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they were successfully 
deleted.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
index bc57653bd27..06ab99cac8a 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
@@ -10,7 +10,7 @@
 
 This statement is used to modify the attributes of BE nodes. After modifying 
the attributes of BE nodes, it will affect the query, write, and data 
distribution of the current node. The following are the attributes that can be 
modified:
 
-| 属性              | 影响                                                         
                                                                                
                                                                                
                                                                                
                                    |
+| Property        | Effect                                                     
                                                                                
                                                                                
                                                                                
                                        |
 
|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `tag.location`  | The resource tag of the BE, with the `default` value being 
default. After modification, it will affect the data balancing of BEs within 
the same tag group and the BE nodes for data distribution during table 
creation. For more information, please refer to[Resource 
Group](../../../../admin-manual/workload-management/resource-group.md) |
 | `disable_query` | Whether to disable queries, with the default value being 
`false`. After setting it to `true`, no new query requests will be scheduled to 
this BE node.                                                                   
                                                                                
                                      |
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
index 0ff4aba66e8..a6e1d84d46f 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
@@ -29,7 +29,7 @@ ALTER SYSTEM MODIFY FRONTEND "<frontend_hostname_port>" 
HOSTNAME "<frontend_new_
 
 ## Access Control Requirements
 
-The user executing this SQL command must have at least NOD_PRIV permissions.
+The user executing this SQL command must have at least NODE_PRIV permissions.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
index 9dc248bd8de..a382e6f9eb4 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
@@ -12,7 +12,7 @@ This statement is used to modify an existing hot-cold tiered 
migration policy. O
 
 ## Syntax
 ```sql
-ALTER STORAGE POLICY  '<policy_name>' PROPERTIE ("<key>"="<value>"[, ... ]);
+ALTER STORAGE POLICY  '<policy_name>' PROPERTIES ("<key>"="<value>"[, ... ]);
 ```
 
 ## Required Parameters
@@ -22,7 +22,7 @@ ALTER STORAGE POLICY  '<policy_name>' PROPERTIE 
("<key>"="<value>"[, ... ]);
 > The name of the storage policy. This is the unique identifier of the storage 
 > policy you want to modify, and an existing policy name must be specified. 
 
 ## Optional Parameters
-`PROPERTIE ("<key>"="<value>"[, ... ])` 
+`PROPERTIES ("<key>"="<value>"[, ... ])` 
 
 1.`retention_days`  
 > Data retention period. Defines the duration for which the data is kept in 
 > storage. Data exceeding this period will be automatically deleted. 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
index 6b5e5111d8c..9c839b92a07 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
@@ -18,8 +18,8 @@ To create a storage policy, you must first create a storage 
resource, and then a
 CREATE STORAGE POLICY <policy_name>
 PROPERTIES(
     "storage_resource" = "<storage_resource_name>"
-    [{， "cooldown_datetime" = "<cooldown_datetime>"
-    ｜ ， "cooldown_ttl" = "<cooldown_ttl>"}]
+    [{, "cooldown_datetime" = "<cooldown_datetime>"
+    | , "cooldown_ttl" = "<cooldown_ttl>"}]
 );
 ```
 ## Required Parameters
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
index 061969cbbeb..b4494b51399 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
@@ -2,13 +2,13 @@
 {
     "title": "CREATE ROW POLICY",
     "language": "en",
-    "description": "Explain can view the rewritten execution plan."
+    "description": "Creates a row-level security policy on a table to restrict 
the rows returned to specified users or roles."
 }
 ---
 
 ## Description
 
-Explain can view the rewritten execution plan. 
+Creates a row-level security policy on a table. The policy restricts the rows 
that specified users or roles can see by attaching a filter predicate that is 
applied to queries against the table. 
 
 ## Syntax
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
index 8d2a1fe7fd4..d12a1ed7da4 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
@@ -81,7 +81,7 @@ The user executing this SQL command must have at least the 
following permissions
 
    ```sql
    mysql> select * from order_analysis;
-   ERROR 1064 (HY000): errCode = 2, detailMessage = sql match regex sql block 
rule: order_analysis_rule
+   ERROR 1064 (HY000): errCode = 2, detailMessage = sql match regex sql block 
rule: test_rule
    ```
 
 2. Create a rule that prevents scanning more than 30 partitions of the same 
table and restricts the query data volume to no more than 10 billion rows
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
index e57a06de5fd..e233d783b12 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
@@ -18,7 +18,7 @@ SHOW SQL_BLOCK_RULE [FOR <rule_name>];
 
 `<rule_name>`
 
-The name of the SQL blocking rule to display. If omitted, all rules will be 
shown. |
+The name of the SQL blocking rule to display. If omitted, all rules will be 
shown.
 
 ## Access Control Requirements  
 
@@ -36,12 +36,12 @@ SHOW SQL_BLOCK_RULE;
 ```
 
 ```text
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
-| Name       | Sql                        | SqlHash | PartitionNum | TabletNum 
 | Cardinality | Global | Enable |
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
-| test_rule  | select * from order_analysis | NULL    | 0           | 0        
  | 0           | true   | true   |
-| test_rule2 | NULL                        | NULL    | 30          | 0         
 | 10000000000 | false  | true   |
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
+| Name       | Sql                          | SqlHash | PartitionNum | 
TabletNum | Cardinality | Global | Enable |
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
+| test_rule  | select * from order_analysis | NULL    | 0            | 0       
  | 0           | true   | true   |
+| test_rule2 | NULL                         | NULL    | 30           | 0       
  | 10000000000 | false  | true   |
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
 ```
 
 2. Display a specific SQL blocking rule  
@@ -50,9 +50,9 @@ SHOW SQL_BLOCK_RULE FOR test_rule2;
 ```
 
 ```text
-+------------+------+---------+-------------+------------+-------------+--------+--------+
-| Name       | Sql  | SqlHash | PartitionNum | TabletNum  | Cardinality | 
Global | Enable |
-+------------+------+---------+-------------+------------+-------------+--------+--------+
-| test_rule2 | NULL | NULL    | 30          | 0          | 10000000000 | false 
 | true   |
-+------------+------+---------+-------------+------------+-------------+--------+--------+
++------------+------+---------+--------------+-----------+-------------+--------+--------+
+| Name       | Sql  | SqlHash | PartitionNum | TabletNum | Cardinality | 
Global | Enable |
++------------+------+---------+--------------+-----------+-------------+--------+--------+
+| test_rule2 | NULL | NULL    | 30           | 0         | 10000000000 | false 
 | true   |
++------------+------+---------+--------------+-----------+-------------+--------+--------+
 ```
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
index 14c75c303cc..b3bff84b7a4 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
@@ -10,7 +10,7 @@
 
 This syntax is used to view the result of the latest insert operation in the 
current session connection
 
-grammar:
+## Syntax
 
 ```sql
 SHOW LAST INSERT
@@ -28,7 +28,7 @@ TransactionStatus: VISIBLE
       FilteredRows: 0
 ```
 
-illustrate:
+## Return Value
 
 * TransactionId: transaction id
 * Label: the label corresponding to the insert task
@@ -47,7 +47,7 @@ illustrate:
 
 ## Keywords
 
-    SHOW, LASR ,INSERT
+    SHOW, LAST, INSERT
 
 ## Best Practice
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
index 091c7d9a737..007a3ce4821 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
@@ -70,7 +70,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | ALTER ROUTINE LOAD requires LOAD privilege on the table |
 
 ## Notes
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
index fa366e4ab09..7c3a33edfd6 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
@@ -34,7 +34,7 @@ WHERE [LABEL = "<load_label>" | LABEL like "<label_pattern>" 
| STATE = { "PENDIN
 
 > If `LABEL LIKE "<label_pattern>"` is used, it matches import tasks whose 
 > labels contain the `label_pattern`.
 
-**3. STATE = { " PENDING " | " ETL " | " LOADING " | " FINISHED " | " 
CANCELLED " }**
+**3. STATE = { " PENDING " | " ETL " | " LOADING " }**
 
 > Specifying `PENDING` means cancelling jobs with the `STATE = "PENDING"` 
 > status. The same applies to other statuses.
 
@@ -67,7 +67,7 @@ Users executing this SQL command must have at least the 
following permissions:
    ```sql
    CANCEL LOAD
    FROM example_db
-   WHERE LABEL like "example_";
+   WHERE LABEL like "%example_%";
    ```
 
 3. Cancel import jobs in the `LOADING` state.
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
index 3f7d86d1849..7fcdb375052 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
@@ -10,7 +10,7 @@
 
 The Routine Load feature allows users to submit a resident import task that 
continuously reads data from a specified data source and imports it into Doris.
 
-Currently, it only supports importing CSV or Json format data from Kafka 
through unauthenticated or SSL authentication methods. [Example of importing 
Json format 
data](../../../../data-operate/import/import-way/routine-load-manual.md#Example-of-importing-Json-format-data)
+Currently, it only supports importing CSV or Json format data from Kafka 
through unauthenticated or SSL authentication methods. [Example of importing 
Json format 
data](../../../../data-operate/import/import-way/routine-load-manual.md#load-example)
 
 ## Syntax
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
index b2e71e4ccd8..7ba0f88e314 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
@@ -34,7 +34,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | PAUSE ROUTINE LOAD requires LOAD privilege on the table |
 
 ## Notes
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
index 1e1215a44d2..b014ffd9f4d 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
@@ -34,7 +34,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | RESUME ROUTINE LOAD requires LOAD privilege on the table 
|
 
 ## Notes
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
index 28208ed27ff..108ff6f695f 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
@@ -36,7 +36,7 @@ Users executing this SQL command must have at least the 
following permission:
 
 | Privilege  | Object | Notes                                                  
  |
 | :--------- | :----- | 
:------------------------------------------------------- |
-| LOAD_PRIV  | Table  | SHOW ROUTINE LOAD requires LOAD permission on the 
table |
+| LOAD_PRIV  | Table  | SHOW CREATE ROUTINE LOAD requires LOAD permission on 
the table |
 
 ## Examples
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
index 6e007f19901..d59fc33a185 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
@@ -40,7 +40,7 @@ SHOW LOAD
 
 **4. STATE = { " PENDING " | " ETL " | " LOADING " | " FINISHED " | " 
CANCELLED " }**
 
-> Specifying `PENDING` means matching jobs with the `LOAD = "PENDING"` status. 
The same applies to other status keywords.
+> Specifying `PENDING` means matching jobs with the `STATE = "PENDING"` 
status. The same applies to other status keywords.
 
 **5. `<col_name>`**
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
index bf8b790f2e8..f47bdafff1d 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
@@ -31,7 +31,7 @@ Users executing this SQL command must have at least the 
following permission:
 
 | Privilege  | Object | Notes                                                  
  |
 | :--------- | :----- | 
:------------------------------------------------------- |
-| LOAD_PRIV  | Table  | SHOW ROUTINE LOAD requires LOAD permission on the 
table |
+| LOAD_PRIV  | Table  | STOP ROUTINE LOAD requires LOAD permission on the 
table |
 
 ## Notes
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/data-query/SELECT.md 
b/versioned_docs/version-2.1/sql-manual/sql-statements/data-query/SELECT.md
index 527c8a29d96..0dfa72cb52e 100644
--- a/versioned_docs/version-2.1/sql-manual/sql-statements/data-query/SELECT.md
+++ b/versioned_docs/version-2.1/sql-manual/sql-statements/data-query/SELECT.md
@@ -210,9 +210,9 @@ Recursive CTE is currently not supported.
 10. UNION Example
 
     ```sql
-    SELECT a FROM t1 WHERE a = 10 AND B = 1 ORDER by LIMIT 10
+    SELECT a FROM t1 WHERE a = 10 AND B = 1 ORDER BY a LIMIT 10
     UNION
-    SELECT a FROM t2 WHERE a = 11 AND B = 2 ORDER by LIMIT 10;
+    SELECT a FROM t2 WHERE a = 11 AND B = 2 ORDER BY a LIMIT 10;
     ```
 
 11. WITH clause example
@@ -227,7 +227,7 @@ Recursive CTE is currently not supported.
     SELECT col1, col2 FROM cte;
     ```
 
-12. JOIN Exampel
+12. JOIN Example
 
     ```sql
     SELECT * FROM t1 LEFT JOIN (t2, t3, t4)
@@ -284,7 +284,7 @@ Recursive CTE is currently not supported.
 
 ## Best Practice
 
-1. ome additional knowledge about the SELECT clause
+1. Some additional knowledge about the SELECT clause
 
    - An alias can be specified for select_expr using AS alias_name. Aliases 
are used as column names in expressions and can be used in GROUP BY, ORDER BY 
or HAVING clauses. The AS keyword is a good habit to use when specifying 
aliases for columns.
 
@@ -356,17 +356,17 @@ Recursive CTE is currently not supported.
 
      DISTINCT removes duplicate rows.
 
-2. The main advantage of subqueries
+3. The main advantage of subqueries
 
     - Subqueries allow structured queries so that each part of a statement can 
be isolated.
     - Some operations require complex unions and associations. Subqueries 
provide other ways to perform these operations
 
-3. Speed up queries
+4. Speed up queries
 
     - Use Doris's partition and bucket as data filtering conditions as much as 
possible to reduce the scope of data scanning
     - Make full use of Doris's prefix index fields as data filter conditions 
to speed up query speed
     
-4. UNION
+5. UNION
 
    - Using only the union keyword has the same effect as using union disitnct. 
Since the deduplication work is more memory-intensive, the query speed using 
the union all operation will be faster and the memory consumption will be less. 
If users want to perform order by and limit operations on the returned result 
set, they need to put the union operation in the subquery, then select from 
subquery, and finally put the subquery and order by outside the subquery.
    
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
index 962455f95d1..8f128df64cf 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
@@ -6,7 +6,7 @@
 }
 ---
 
-### Description
+## Description
 
 This statement is used to find the corresponding database name based on the 
database id (only used by administrators)
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/database/SHOW-DATABASES.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/database/SHOW-DATABASES.md
index 1d695b9a327..6a255afae56 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/database/SHOW-DATABASES.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/database/SHOW-DATABASES.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 |:-----------|:------|:---------------|
 | SELECT_PRIV | Corresponding database | Requires read permission on the 
corresponding database |
 
-## 示例
+## Examples
 
 - Displays the names of all current databases.
 
diff --git 
a/versioned_docs/version-2.1/sql-manual/sql-statements/function/DROP-FUNCTION.md
 
b/versioned_docs/version-2.1/sql-manual/sql-statements/function/DROP-FUNCTION.md
index 40cb22b55f1..70a6b6c78e0 100644
--- 
a/versioned_docs/version-2.1/sql-manual/sql-statements/function/DROP-FUNCTION.md
+++ 
b/versioned_docs/version-2.1/sql-manual/sql-statements/function/DROP-FUNCTION.md
@@ -13,7 +13,7 @@ Delete a custom function.
 ## Syntax
 
 ```sql
-DROP [ GLOBAL ] <function_name> ( <arg_type> )
+DROP [ GLOBAL ] FUNCTION <function_name> ( <arg_type> )
 ```
 
 ## Required Parameters
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
index c3cba99e4e6..50cbda04a29 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 1. Before adding a new FOLLOWER node, make sure the node is properly 
configured.
 2. Before adding a FOLLOWER node, ensure that the number of FOLLOWER nodes in 
the cluster is an odd number after the addition.
-3. After adding the FOLLOWER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they have been added 
successfully and are in a normal state.
+3. After adding the FOLLOWER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they have been added 
successfully and are in a normal state.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
index 18a62fc345c..c4119d54e63 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
@@ -37,7 +37,7 @@ The user executing this SQL command must have at least the 
following permissions
 ## Usage Notes
 
 1. Before adding a new OBSERVER node, make sure the node is properly 
configured.
-2. After adding the OBSERVER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they have been added 
successfully and are in a normal state.
+2. After adding the OBSERVER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they have been added 
successfully and are in a normal state.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
index c8e464366ab..47d22272f85 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
@@ -43,7 +43,7 @@ The user who executes this operation needs to have the 
NODE_PRIV permission.
 1. Delete all Brokers
 
     ```sql
-    ALTER SYSTEM DROP ALL BROKER broker_name.
+    ALTER SYSTEM DROP ALL BROKER broker_name;
     ```
 
 2. Delete a specific Broker node
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
index 347099b5bc6..05fb780c481 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 1. Before deleting a FOLLOWER node, make sure that the node that needs to be 
taken offline is not a Master node.
 2. Before deleting a FOLLOWER node, ensure that the number of FOLLOWER nodes 
in the cluster is an odd number after they go offline.
-3. After deleting the FOLLOWER node[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they were successfully 
deleted.
+3. After deleting the FOLLOWER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they were successfully 
deleted.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
index 290ff73750b..933725e379f 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
@@ -36,7 +36,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 ## Usage Notes
 
-1. After deleting the OBSERVER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they were successfully 
deleted.
+1. After deleting the OBSERVER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they were successfully 
deleted.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
index 6f37957475b..69c4c399cf7 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
@@ -10,7 +10,7 @@
 
 This statement is used to modify the attributes of BE nodes. After modifying 
the attributes of BE nodes, it will affect the query, write, and data 
distribution of the current node. The following are the attributes that can be 
modified:
 
-| 属性              | 影响                                                         
                                                                                
                                                                                
                                                                                
                                    |
+| Property        | Effect                                                     
                                                                                
                                                                                
                                                                                
                                        |
 
|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `tag.location`  | The resource tag of the BE, with the `default` value being 
default. After modification, it will affect the data balancing of BEs within 
the same tag group and the BE nodes for data distribution during table 
creation. For more information, please refer to[Resource 
Group](../../../../admin-manual/workload-management/resource-group.md) |
 | `disable_query` | Whether to disable queries, with the default value being 
`false`. After setting it to `true`, no new query requests will be scheduled to 
this BE node.                                                                   
                                                                                
                                      |
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
index 0ff4aba66e8..a6e1d84d46f 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
@@ -29,7 +29,7 @@ ALTER SYSTEM MODIFY FRONTEND "<frontend_hostname_port>" 
HOSTNAME "<frontend_new_
 
 ## Access Control Requirements
 
-The user executing this SQL command must have at least NOD_PRIV permissions.
+The user executing this SQL command must have at least NODE_PRIV permissions.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
index 9dc248bd8de..a382e6f9eb4 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
@@ -12,7 +12,7 @@ This statement is used to modify an existing hot-cold tiered 
migration policy. O
 
 ## Syntax
 ```sql
-ALTER STORAGE POLICY  '<policy_name>' PROPERTIE ("<key>"="<value>"[, ... ]);
+ALTER STORAGE POLICY  '<policy_name>' PROPERTIES ("<key>"="<value>"[, ... ]);
 ```
 
 ## Required Parameters
@@ -22,7 +22,7 @@ ALTER STORAGE POLICY  '<policy_name>' PROPERTIE 
("<key>"="<value>"[, ... ]);
 > The name of the storage policy. This is the unique identifier of the storage 
 > policy you want to modify, and an existing policy name must be specified. 
 
 ## Optional Parameters
-`PROPERTIE ("<key>"="<value>"[, ... ])` 
+`PROPERTIES ("<key>"="<value>"[, ... ])` 
 
 1.`retention_days`  
 > Data retention period. Defines the duration for which the data is kept in 
 > storage. Data exceeding this period will be automatically deleted. 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
index 4235d215ba2..4aca5409f13 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
@@ -30,7 +30,7 @@ PROPERTIES (<storage_vault_property>)
 >- vault_name: The name of the vault. When a vault is set as the default 
 >storage vault using the statement `SET <original_vault_name> DEFAULT STORAGE 
 >VAULT`, its name cannot be modified. To rename the vault, you must first 
 >unset the default storage vault by executing the `UNSET DEFAULT STORAGE 
 >VAULT` command, and then modify its name. Finally, if you need to set the 
 >renamed vault as the default storage vault, you can use the statement `SET 
 ><new_vault_name> DEFAULT STORAGE VAULT`.
 >- use_path_style: Whether to allow path style url, optional values are true, 
 >false. The default value is false.
 
->When type is hdfs, the following fields are prohibited:
+>When type is hdfs, the allowed property fields are as follows:
 >
 >- path_prefix: Storage path prefix
 >- fs.defaultFS: hdfs name
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
index 2de42f558d6..1fadc5e3046 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
@@ -44,7 +44,7 @@ Its result is:
 Then terminate it through `CANCEL WARM UP`:
 
 ```C++
-CANCEL WARM UP WHERE id = 90290165739458;
+CANCEL WARM UP JOB WHERE id = 90290165739458;
 ```
 
 If the following content is returned, it indicates that the warm-up job 
corresponding to the specified id does not exist:
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
index ed68a41beac..c303b644d0e 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
@@ -16,8 +16,8 @@ To create a storage policy, you must first create a storage 
resource, and then a
 CREATE STORAGE POLICY <policy_name>
 PROPERTIES(
     "storage_resource" = "<storage_resource_name>"
-    [{， "cooldown_datetime" = "<cooldown_datetime>"
-    ｜ ， "cooldown_ttl" = "<cooldown_ttl>"}]
+    [{, "cooldown_datetime" = "<cooldown_datetime>"
+    | , "cooldown_ttl" = "<cooldown_ttl>"}]
 );
 ```
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
index 061969cbbeb..b4494b51399 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
@@ -2,13 +2,13 @@
 {
     "title": "CREATE ROW POLICY",
     "language": "en",
-    "description": "Explain can view the rewritten execution plan."
+    "description": "Creates a row-level security policy on a table to restrict 
the rows returned to specified users or roles."
 }
 ---
 
 ## Description
 
-Explain can view the rewritten execution plan. 
+Creates a row-level security policy on a table. The policy restricts the rows 
that specified users or roles can see by attaching a filter predicate that is 
applied to queries against the table. 
 
 ## Syntax
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
index aedf7f3aafe..1671f57e71a 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
@@ -83,7 +83,7 @@ The user executing this SQL command must have at least the 
following permissions
 
    ```sql
    mysql> select * from order_analysis;
-   ERROR 1064 (HY000): errCode = 2, detailMessage = sql match regex sql block 
rule: order_analysis_rule
+   ERROR 1064 (HY000): errCode = 2, detailMessage = sql match regex sql block 
rule: test_rule
    ```
 
 2. Create a rule that prevents scanning more than 30 partitions of the same 
table and restricts the query data volume to no more than 10 billion rows
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
index e57a06de5fd..e233d783b12 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
@@ -18,7 +18,7 @@ SHOW SQL_BLOCK_RULE [FOR <rule_name>];
 
 `<rule_name>`
 
-The name of the SQL blocking rule to display. If omitted, all rules will be 
shown. |
+The name of the SQL blocking rule to display. If omitted, all rules will be 
shown.
 
 ## Access Control Requirements  
 
@@ -36,12 +36,12 @@ SHOW SQL_BLOCK_RULE;
 ```
 
 ```text
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
-| Name       | Sql                        | SqlHash | PartitionNum | TabletNum 
 | Cardinality | Global | Enable |
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
-| test_rule  | select * from order_analysis | NULL    | 0           | 0        
  | 0           | true   | true   |
-| test_rule2 | NULL                        | NULL    | 30          | 0         
 | 10000000000 | false  | true   |
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
+| Name       | Sql                          | SqlHash | PartitionNum | 
TabletNum | Cardinality | Global | Enable |
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
+| test_rule  | select * from order_analysis | NULL    | 0            | 0       
  | 0           | true   | true   |
+| test_rule2 | NULL                         | NULL    | 30           | 0       
  | 10000000000 | false  | true   |
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
 ```
 
 2. Display a specific SQL blocking rule  
@@ -50,9 +50,9 @@ SHOW SQL_BLOCK_RULE FOR test_rule2;
 ```
 
 ```text
-+------------+------+---------+-------------+------------+-------------+--------+--------+
-| Name       | Sql  | SqlHash | PartitionNum | TabletNum  | Cardinality | 
Global | Enable |
-+------------+------+---------+-------------+------------+-------------+--------+--------+
-| test_rule2 | NULL | NULL    | 30          | 0          | 10000000000 | false 
 | true   |
-+------------+------+---------+-------------+------------+-------------+--------+--------+
++------------+------+---------+--------------+-----------+-------------+--------+--------+
+| Name       | Sql  | SqlHash | PartitionNum | TabletNum | Cardinality | 
Global | Enable |
++------------+------+---------+--------------+-----------+-------------+--------+--------+
+| test_rule2 | NULL | NULL    | 30           | 0         | 10000000000 | false 
 | true   |
++------------+------+---------+--------------+-----------+-------------+--------+--------+
 ```
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
index 0b4a1bb5952..12470e49522 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
@@ -10,7 +10,7 @@
 
 This syntax is used to view the result of the latest insert operation in the 
current session connection
 
-grammar:
+## Syntax
 
 ```sql
 SHOW LAST INSERT
@@ -28,7 +28,7 @@ TransactionStatus: VISIBLE
       FilteredRows: 0
 ```
 
-illustrate:
+## Return Value
 
 * TransactionId: transaction id
 * Label: the label corresponding to the insert task
@@ -47,7 +47,7 @@ illustrate:
 
 ## Keywords
 
-    SHOW, LASR ,INSERT
+    SHOW, LAST, INSERT
 
 ## Best Practice
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
index 091c7d9a737..007a3ce4821 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
@@ -70,7 +70,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | ALTER ROUTINE LOAD requires LOAD privilege on the table |
 
 ## Notes
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
index fa366e4ab09..7c3a33edfd6 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
@@ -34,7 +34,7 @@ WHERE [LABEL = "<load_label>" | LABEL like "<label_pattern>" 
| STATE = { "PENDIN
 
 > If `LABEL LIKE "<label_pattern>"` is used, it matches import tasks whose 
 > labels contain the `label_pattern`.
 
-**3. STATE = { " PENDING " | " ETL " | " LOADING " | " FINISHED " | " 
CANCELLED " }**
+**3. STATE = { " PENDING " | " ETL " | " LOADING " }**
 
 > Specifying `PENDING` means cancelling jobs with the `STATE = "PENDING"` 
 > status. The same applies to other statuses.
 
@@ -67,7 +67,7 @@ Users executing this SQL command must have at least the 
following permissions:
    ```sql
    CANCEL LOAD
    FROM example_db
-   WHERE LABEL like "example_";
+   WHERE LABEL like "%example_%";
    ```
 
 3. Cancel import jobs in the `LOADING` state.
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
index 3f7d86d1849..c63dc806030 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
@@ -10,7 +10,7 @@
 
 The Routine Load feature allows users to submit a resident import task that 
continuously reads data from a specified data source and imports it into Doris.
 
-Currently, it only supports importing CSV or Json format data from Kafka 
through unauthenticated or SSL authentication methods. [Example of importing 
Json format 
data](../../../../data-operate/import/import-way/routine-load-manual.md#Example-of-importing-Json-format-data)
+Currently, it only supports importing CSV or Json format data from Kafka 
through unauthenticated or SSL authentication methods. [Example of importing 
Json format 
data](../../../../data-operate/import/import-way/routine-load-manual.md#import-examples)
 
 ## Syntax
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
index b2e71e4ccd8..7ba0f88e314 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
@@ -34,7 +34,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | PAUSE ROUTINE LOAD requires LOAD privilege on the table |
 
 ## Notes
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
index 1e1215a44d2..b014ffd9f4d 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
@@ -34,7 +34,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | RESUME ROUTINE LOAD requires LOAD privilege on the table 
|
 
 ## Notes
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
index 28208ed27ff..108ff6f695f 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
@@ -36,7 +36,7 @@ Users executing this SQL command must have at least the 
following permission:
 
 | Privilege  | Object | Notes                                                  
  |
 | :--------- | :----- | 
:------------------------------------------------------- |
-| LOAD_PRIV  | Table  | SHOW ROUTINE LOAD requires LOAD permission on the 
table |
+| LOAD_PRIV  | Table  | SHOW CREATE ROUTINE LOAD requires LOAD permission on 
the table |
 
 ## Examples
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
index 6e007f19901..d59fc33a185 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
@@ -40,7 +40,7 @@ SHOW LOAD
 
 **4. STATE = { " PENDING " | " ETL " | " LOADING " | " FINISHED " | " 
CANCELLED " }**
 
-> Specifying `PENDING` means matching jobs with the `LOAD = "PENDING"` status. 
The same applies to other status keywords.
+> Specifying `PENDING` means matching jobs with the `STATE = "PENDING"` 
status. The same applies to other status keywords.
 
 **5. `<col_name>`**
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
index bf8b790f2e8..f47bdafff1d 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
@@ -31,7 +31,7 @@ Users executing this SQL command must have at least the 
following permission:
 
 | Privilege  | Object | Notes                                                  
  |
 | :--------- | :----- | 
:------------------------------------------------------- |
-| LOAD_PRIV  | Table  | SHOW ROUTINE LOAD requires LOAD permission on the 
table |
+| LOAD_PRIV  | Table  | STOP ROUTINE LOAD requires LOAD permission on the 
table |
 
 ## Notes
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/data-query/SELECT.md 
b/versioned_docs/version-3.x/sql-manual/sql-statements/data-query/SELECT.md
index 8c9fae32f4e..eb1d82dd99e 100644
--- a/versioned_docs/version-3.x/sql-manual/sql-statements/data-query/SELECT.md
+++ b/versioned_docs/version-3.x/sql-manual/sql-statements/data-query/SELECT.md
@@ -210,9 +210,9 @@ Recursive CTE is currently not supported.
 10. UNION Example
 
     ```sql
-    SELECT a FROM t1 WHERE a = 10 AND B = 1 ORDER by LIMIT 10
+    SELECT a FROM t1 WHERE a = 10 AND B = 1 ORDER BY a LIMIT 10
     UNION
-    SELECT a FROM t2 WHERE a = 11 AND B = 2 ORDER by LIMIT 10;
+    SELECT a FROM t2 WHERE a = 11 AND B = 2 ORDER BY a LIMIT 10;
     ```
 
 11. WITH clause example
@@ -227,7 +227,7 @@ Recursive CTE is currently not supported.
     SELECT col1, col2 FROM cte;
     ```
 
-12. JOIN Exampel
+12. JOIN Example
 
     ```sql
     SELECT * FROM t1 LEFT JOIN (t2, t3, t4)
@@ -284,7 +284,7 @@ Recursive CTE is currently not supported.
 
 ## Best Practice
 
-1. ome additional knowledge about the SELECT clause
+1. Some additional knowledge about the SELECT clause
 
    - An alias can be specified for select_expr using AS alias_name. Aliases 
are used as column names in expressions and can be used in GROUP BY, ORDER BY 
or HAVING clauses. The AS keyword is a good habit to use when specifying 
aliases for columns.
 
@@ -356,17 +356,17 @@ Recursive CTE is currently not supported.
 
      DISTINCT removes duplicate rows.
 
-2. The main advantage of subqueries
+3. The main advantage of subqueries
 
     - Subqueries allow structured queries so that each part of a statement can 
be isolated.
     - Some operations require complex unions and associations. Subqueries 
provide other ways to perform these operations
 
-3. Speed up queries
+4. Speed up queries
 
     - Use Doris's partition and bucket as data filtering conditions as much as 
possible to reduce the scope of data scanning
     - Make full use of Doris's prefix index fields as data filter conditions 
to speed up query speed
     
-4. UNION
+5. UNION
 
    - Using only the union keyword has the same effect as using union disitnct. 
Since the deduplication work is more memory-intensive, the query speed using 
the union all operation will be faster and the memory consumption will be less. 
If users want to perform order by and limit operations on the returned result 
set, they need to put the union operation in the subquery, then select from 
subquery, and finally put the subquery and order by outside the subquery.
    
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
index f0e3e78eb17..d84fc76d5cf 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
@@ -6,7 +6,7 @@
 }
 ---
 
-### Description
+## Description
 
 This statement is used to find the corresponding database name based on the 
database id (only used by administrators)
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/database/SHOW-DATABASES.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/database/SHOW-DATABASES.md
index 1d695b9a327..6a255afae56 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/database/SHOW-DATABASES.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/database/SHOW-DATABASES.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 |:-----------|:------|:---------------|
 | SELECT_PRIV | Corresponding database | Requires read permission on the 
corresponding database |
 
-## 示例
+## Examples
 
 - Displays the names of all current databases.
 
diff --git 
a/versioned_docs/version-3.x/sql-manual/sql-statements/function/DROP-FUNCTION.md
 
b/versioned_docs/version-3.x/sql-manual/sql-statements/function/DROP-FUNCTION.md
index 40cb22b55f1..70a6b6c78e0 100644
--- 
a/versioned_docs/version-3.x/sql-manual/sql-statements/function/DROP-FUNCTION.md
+++ 
b/versioned_docs/version-3.x/sql-manual/sql-statements/function/DROP-FUNCTION.md
@@ -13,7 +13,7 @@ Delete a custom function.
 ## Syntax
 
 ```sql
-DROP [ GLOBAL ] <function_name> ( <arg_type> )
+DROP [ GLOBAL ] FUNCTION <function_name> ( <arg_type> )
 ```
 
 ## Required Parameters
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
index c3cba99e4e6..50cbda04a29 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-FOLLOWER.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 1. Before adding a new FOLLOWER node, make sure the node is properly 
configured.
 2. Before adding a FOLLOWER node, ensure that the number of FOLLOWER nodes in 
the cluster is an odd number after the addition.
-3. After adding the FOLLOWER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they have been added 
successfully and are in a normal state.
+3. After adding the FOLLOWER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they have been added 
successfully and are in a normal state.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
index 18a62fc345c..c4119d54e63 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/ADD-OBSERVER.md
@@ -37,7 +37,7 @@ The user executing this SQL command must have at least the 
following permissions
 ## Usage Notes
 
 1. Before adding a new OBSERVER node, make sure the node is properly 
configured.
-2. After adding the OBSERVER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they have been added 
successfully and are in a normal state.
+2. After adding the OBSERVER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they have been added 
successfully and are in a normal state.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
index c8e464366ab..47d22272f85 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-BROKER.md
@@ -43,7 +43,7 @@ The user who executes this operation needs to have the 
NODE_PRIV permission.
 1. Delete all Brokers
 
     ```sql
-    ALTER SYSTEM DROP ALL BROKER broker_name.
+    ALTER SYSTEM DROP ALL BROKER broker_name;
     ```
 
 2. Delete a specific Broker node
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
index 347099b5bc6..05fb780c481 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-FOLLOWER.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 1. Before deleting a FOLLOWER node, make sure that the node that needs to be 
taken offline is not a Master node.
 2. Before deleting a FOLLOWER node, ensure that the number of FOLLOWER nodes 
in the cluster is an odd number after they go offline.
-3. After deleting the FOLLOWER node[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they were successfully 
deleted.
+3. After deleting the FOLLOWER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they were successfully 
deleted.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
index 290ff73750b..933725e379f 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/DROP-OBSERVER.md
@@ -36,7 +36,7 @@ The user executing this SQL command must have at least the 
following permissions
 
 ## Usage Notes
 
-1. After deleting the OBSERVER node, use[`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md)command to verify that they were successfully 
deleted.
+1. After deleting the OBSERVER node, use the [`SHOW 
FRONTENDS`](./SHOW-FRONTENDS.md) command to verify that they were successfully 
deleted.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
index 6f37957475b..69c4c399cf7 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-BACKEND.md
@@ -10,7 +10,7 @@
 
 This statement is used to modify the attributes of BE nodes. After modifying 
the attributes of BE nodes, it will affect the query, write, and data 
distribution of the current node. The following are the attributes that can be 
modified:
 
-| 属性              | 影响                                                         
                                                                                
                                                                                
                                                                                
                                    |
+| Property        | Effect                                                     
                                                                                
                                                                                
                                                                                
                                        |
 
|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `tag.location`  | The resource tag of the BE, with the `default` value being 
default. After modification, it will affect the data balancing of BEs within 
the same tag group and the BE nodes for data distribution during table 
creation. For more information, please refer to[Resource 
Group](../../../../admin-manual/workload-management/resource-group.md) |
 | `disable_query` | Whether to disable queries, with the default value being 
`false`. After setting it to `true`, no new query requests will be scheduled to 
this BE node.                                                                   
                                                                                
                                      |
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
index 0ff4aba66e8..a6e1d84d46f 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/instance-management/MODIFY-FRONTEND-HOSTNAME.md
@@ -29,7 +29,7 @@ ALTER SYSTEM MODIFY FRONTEND "<frontend_hostname_port>" 
HOSTNAME "<frontend_new_
 
 ## Access Control Requirements
 
-The user executing this SQL command must have at least NOD_PRIV permissions.
+The user executing this SQL command must have at least NODE_PRIV permissions.
 
 ## Examples
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
index 9dc248bd8de..a382e6f9eb4 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-POLICY.md
@@ -12,7 +12,7 @@ This statement is used to modify an existing hot-cold tiered 
migration policy. O
 
 ## Syntax
 ```sql
-ALTER STORAGE POLICY  '<policy_name>' PROPERTIE ("<key>"="<value>"[, ... ]);
+ALTER STORAGE POLICY  '<policy_name>' PROPERTIES ("<key>"="<value>"[, ... ]);
 ```
 
 ## Required Parameters
@@ -22,7 +22,7 @@ ALTER STORAGE POLICY  '<policy_name>' PROPERTIE 
("<key>"="<value>"[, ... ]);
 > The name of the storage policy. This is the unique identifier of the storage 
 > policy you want to modify, and an existing policy name must be specified. 
 
 ## Optional Parameters
-`PROPERTIE ("<key>"="<value>"[, ... ])` 
+`PROPERTIES ("<key>"="<value>"[, ... ])` 
 
 1.`retention_days`  
 > Data retention period. Defines the duration for which the data is kept in 
 > storage. Data exceeding this period will be automatically deleted. 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
index 4235d215ba2..4aca5409f13 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/ALTER-STORAGE-VAULT.md
@@ -30,7 +30,7 @@ PROPERTIES (<storage_vault_property>)
 >- vault_name: The name of the vault. When a vault is set as the default 
 >storage vault using the statement `SET <original_vault_name> DEFAULT STORAGE 
 >VAULT`, its name cannot be modified. To rename the vault, you must first 
 >unset the default storage vault by executing the `UNSET DEFAULT STORAGE 
 >VAULT` command, and then modify its name. Finally, if you need to set the 
 >renamed vault as the default storage vault, you can use the statement `SET 
 ><new_vault_name> DEFAULT STORAGE VAULT`.
 >- use_path_style: Whether to allow path style url, optional values are true, 
 >false. The default value is false.
 
->When type is hdfs, the following fields are prohibited:
+>When type is hdfs, the allowed property fields are as follows:
 >
 >- path_prefix: Storage path prefix
 >- fs.defaultFS: hdfs name
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
index 2de42f558d6..1fadc5e3046 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/CANCEL-WARM-UP.md
@@ -44,7 +44,7 @@ Its result is:
 Then terminate it through `CANCEL WARM UP`:
 
 ```C++
-CANCEL WARM UP WHERE id = 90290165739458;
+CANCEL WARM UP JOB WHERE id = 90290165739458;
 ```
 
 If the following content is returned, it indicates that the warm-up job 
corresponding to the specified id does not exist:
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
index ed68a41beac..c303b644d0e 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/CREATE-STORAGE-POLICY.md
@@ -16,8 +16,8 @@ To create a storage policy, you must first create a storage 
resource, and then a
 CREATE STORAGE POLICY <policy_name>
 PROPERTIES(
     "storage_resource" = "<storage_resource_name>"
-    [{， "cooldown_datetime" = "<cooldown_datetime>"
-    ｜ ， "cooldown_ttl" = "<cooldown_ttl>"}]
+    [{, "cooldown_datetime" = "<cooldown_datetime>"
+    | , "cooldown_ttl" = "<cooldown_ttl>"}]
 );
 ```
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/SHOW-CACHE-HOTSPOT.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/SHOW-CACHE-HOTSPOT.md
index e313ac9c780..34a9f637632 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/SHOW-CACHE-HOTSPOT.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/cluster-management/storage-management/SHOW-CACHE-HOTSPOT.md
@@ -15,7 +15,7 @@ This statement is used to display the hotspot information of 
the file cache.
 
 Before version 3.0.4, you could use the `SHOW CACHE HOTSPOT` statement to 
query cache hotspot information statistics. Starting from version 3.0.4, the 
use of the `SHOW CACHE HOTSPOT` statement for cache hotspot information 
statistics is no longer supported. Please directly access the system table 
`__internal_schema.cloud_cache_hotspot` for queries. For detailed usage, refer 
to [MANAGING FILE 
CACHE](../../../../compute-storage-decoupled/file-cache/file-cache).
 
-
+:::
 
 ## Syntax
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
index 061969cbbeb..b4494b51399 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY.md
@@ -2,13 +2,13 @@
 {
     "title": "CREATE ROW POLICY",
     "language": "en",
-    "description": "Explain can view the rewritten execution plan."
+    "description": "Creates a row-level security policy on a table to restrict 
the rows returned to specified users or roles."
 }
 ---
 
 ## Description
 
-Explain can view the rewritten execution plan. 
+Creates a row-level security policy on a table. The policy restricts the rows 
that specified users or roles can see by attaching a filter predicate that is 
applied to queries against the table. 
 
 ## Syntax
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
index 7c2d724c172..610e1bd60a0 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/CREATE-SQL_BLOCK_RULE.md
@@ -81,7 +81,7 @@ The user executing this SQL command must have at least the 
following permissions
 
    ```sql
    mysql> select * from order_analysis;
-   ERROR 1064 (HY000): errCode = 2, detailMessage = sql match regex sql block 
rule: order_analysis_rule
+   ERROR 1064 (HY000): errCode = 2, detailMessage = sql match regex sql block 
rule: test_rule
    ```
 
 2. Create a rule that prevents scanning more than 30 partitions of the same 
table and restricts the query data volume to no more than 10 billion rows
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
index e57a06de5fd..e233d783b12 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-governance/SHOW-SQL_BLOCK_RULE.md
@@ -18,7 +18,7 @@ SHOW SQL_BLOCK_RULE [FOR <rule_name>];
 
 `<rule_name>`
 
-The name of the SQL blocking rule to display. If omitted, all rules will be 
shown. |
+The name of the SQL blocking rule to display. If omitted, all rules will be 
shown.
 
 ## Access Control Requirements  
 
@@ -36,12 +36,12 @@ SHOW SQL_BLOCK_RULE;
 ```
 
 ```text
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
-| Name       | Sql                        | SqlHash | PartitionNum | TabletNum 
 | Cardinality | Global | Enable |
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
-| test_rule  | select * from order_analysis | NULL    | 0           | 0        
  | 0           | true   | true   |
-| test_rule2 | NULL                        | NULL    | 30          | 0         
 | 10000000000 | false  | true   |
-+------------+----------------------------+---------+-------------+------------+-------------+--------+--------+
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
+| Name       | Sql                          | SqlHash | PartitionNum | 
TabletNum | Cardinality | Global | Enable |
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
+| test_rule  | select * from order_analysis | NULL    | 0            | 0       
  | 0           | true   | true   |
+| test_rule2 | NULL                         | NULL    | 30           | 0       
  | 10000000000 | false  | true   |
++------------+------------------------------+---------+--------------+-----------+-------------+--------+--------+
 ```
 
 2. Display a specific SQL blocking rule  
@@ -50,9 +50,9 @@ SHOW SQL_BLOCK_RULE FOR test_rule2;
 ```
 
 ```text
-+------------+------+---------+-------------+------------+-------------+--------+--------+
-| Name       | Sql  | SqlHash | PartitionNum | TabletNum  | Cardinality | 
Global | Enable |
-+------------+------+---------+-------------+------------+-------------+--------+--------+
-| test_rule2 | NULL | NULL    | 30          | 0          | 10000000000 | false 
 | true   |
-+------------+------+---------+-------------+------------+-------------+--------+--------+
++------------+------+---------+--------------+-----------+-------------+--------+--------+
+| Name       | Sql  | SqlHash | PartitionNum | TabletNum | Cardinality | 
Global | Enable |
++------------+------+---------+--------------+-----------+-------------+--------+--------+
+| test_rule2 | NULL | NULL    | 30           | 0         | 10000000000 | false 
 | true   |
++------------+------+---------+--------------+-----------+-------------+--------+--------+
 ```
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/DML/MERGE-INTO.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/DML/MERGE-INTO.md
index 1889950e735..0b740af7c1e 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/DML/MERGE-INTO.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/DML/MERGE-INTO.md
@@ -112,7 +112,7 @@ The 
[user](../../../../admin-manual/auth/authentication-and-authorization.md) ex
 - A single MERGE statement can include multiple matching and not-matching 
clauses (that is, WHEN MATCHED ... and WHEN NOT MATCHED ...).
 - Any matching or not-matching clause that omits the AND subclause (default 
behavior) must be the last of its clause type in the statement (for example, a 
WHEN MATCHED ... clause can’t be followed by a WHEN MATCHED AND ... clause). 
Doing so results in an unreachable case, which returns an error.
 
-### Duplicate join behavior¶
+### Duplicate join behavior
 
 Currently, Doris does not detect whether duplicate join rows occur. If they 
do, the behavior is undefined.
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
index 0b4a1bb5952..12470e49522 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/DML/SHOW-LAST-INSERT.md
@@ -10,7 +10,7 @@
 
 This syntax is used to view the result of the latest insert operation in the 
current session connection
 
-grammar:
+## Syntax
 
 ```sql
 SHOW LAST INSERT
@@ -28,7 +28,7 @@ TransactionStatus: VISIBLE
       FilteredRows: 0
 ```
 
-illustrate:
+## Return Value
 
 * TransactionId: transaction id
 * Label: the label corresponding to the insert task
@@ -47,7 +47,7 @@ illustrate:
 
 ## Keywords
 
-    SHOW, LASR ,INSERT
+    SHOW, LAST, INSERT
 
 ## Best Practice
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
index 091c7d9a737..007a3ce4821 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/ALTER-ROUTINE-LOAD.md
@@ -70,7 +70,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | ALTER ROUTINE LOAD requires LOAD privilege on the table |
 
 ## Notes
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
index fa366e4ab09..7c3a33edfd6 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/CANCEL-LOAD.md
@@ -34,7 +34,7 @@ WHERE [LABEL = "<load_label>" | LABEL like "<label_pattern>" 
| STATE = { "PENDIN
 
 > If `LABEL LIKE "<label_pattern>"` is used, it matches import tasks whose 
 > labels contain the `label_pattern`.
 
-**3. STATE = { " PENDING " | " ETL " | " LOADING " | " FINISHED " | " 
CANCELLED " }**
+**3. STATE = { " PENDING " | " ETL " | " LOADING " }**
 
 > Specifying `PENDING` means cancelling jobs with the `STATE = "PENDING"` 
 > status. The same applies to other statuses.
 
@@ -67,7 +67,7 @@ Users executing this SQL command must have at least the 
following permissions:
    ```sql
    CANCEL LOAD
    FROM example_db
-   WHERE LABEL like "example_";
+   WHERE LABEL like "%example_%";
    ```
 
 3. Cancel import jobs in the `LOADING` state.
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
index 24a09dcc8cb..ccf11563602 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/CREATE-ROUTINE-LOAD.md
@@ -10,7 +10,7 @@
 
 The Routine Load feature allows users to submit a resident import task that 
continuously reads data from a specified data source and imports it into Doris.
 
-Currently, it only supports importing CSV or Json format data from Kafka 
through unauthenticated or SSL authentication methods. [Example of importing 
Json format 
data](../../../../data-operate/import/import-way/routine-load-manual.md#Example-of-importing-Json-format-data)
+Currently, it only supports importing CSV or Json format data from Kafka 
through unauthenticated or SSL authentication methods. [Example of importing 
Json format 
data](../../../../data-operate/import/import-way/routine-load-manual.md#import-examples)
 
 ## Syntax
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
index b2e71e4ccd8..7ba0f88e314 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/PAUSE-ROUTINE-LOAD.md
@@ -34,7 +34,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | PAUSE ROUTINE LOAD requires LOAD privilege on the table |
 
 ## Notes
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
index 1e1215a44d2..b014ffd9f4d 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/RESUME-ROUTINE-LOAD.md
@@ -34,7 +34,7 @@ Users executing this SQL command must have at least the 
following privileges:
 
 | Privilege | Object | Notes |
 | :-------- | :----- | :---- |
-| LOAD_PRIV | Table | SHOW ROUTINE LOAD requires LOAD privilege on the table |
+| LOAD_PRIV | Table | RESUME ROUTINE LOAD requires LOAD privilege on the table 
|
 
 ## Notes
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
index 28208ed27ff..108ff6f695f 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-CREATE-ROUTINE-LOAD.md
@@ -36,7 +36,7 @@ Users executing this SQL command must have at least the 
following permission:
 
 | Privilege  | Object | Notes                                                  
  |
 | :--------- | :----- | 
:------------------------------------------------------- |
-| LOAD_PRIV  | Table  | SHOW ROUTINE LOAD requires LOAD permission on the 
table |
+| LOAD_PRIV  | Table  | SHOW CREATE ROUTINE LOAD requires LOAD permission on 
the table |
 
 ## Examples
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
index 6e007f19901..d59fc33a185 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/SHOW-LOAD.md
@@ -40,7 +40,7 @@ SHOW LOAD
 
 **4. STATE = { " PENDING " | " ETL " | " LOADING " | " FINISHED " | " 
CANCELLED " }**
 
-> Specifying `PENDING` means matching jobs with the `LOAD = "PENDING"` status. 
The same applies to other status keywords.
+> Specifying `PENDING` means matching jobs with the `STATE = "PENDING"` 
status. The same applies to other status keywords.
 
 **5. `<col_name>`**
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
index bf8b790f2e8..f47bdafff1d 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-modification/load-and-export/STOP-ROUTINE-LOAD.md
@@ -31,7 +31,7 @@ Users executing this SQL command must have at least the 
following permission:
 
 | Privilege  | Object | Notes                                                  
  |
 | :--------- | :----- | 
:------------------------------------------------------- |
-| LOAD_PRIV  | Table  | SHOW ROUTINE LOAD requires LOAD permission on the 
table |
+| LOAD_PRIV  | Table  | STOP ROUTINE LOAD requires LOAD permission on the 
table |
 
 ## Notes
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/data-query/SELECT.md 
b/versioned_docs/version-4.x/sql-manual/sql-statements/data-query/SELECT.md
index 8c9fae32f4e..eb1d82dd99e 100644
--- a/versioned_docs/version-4.x/sql-manual/sql-statements/data-query/SELECT.md
+++ b/versioned_docs/version-4.x/sql-manual/sql-statements/data-query/SELECT.md
@@ -210,9 +210,9 @@ Recursive CTE is currently not supported.
 10. UNION Example
 
     ```sql
-    SELECT a FROM t1 WHERE a = 10 AND B = 1 ORDER by LIMIT 10
+    SELECT a FROM t1 WHERE a = 10 AND B = 1 ORDER BY a LIMIT 10
     UNION
-    SELECT a FROM t2 WHERE a = 11 AND B = 2 ORDER by LIMIT 10;
+    SELECT a FROM t2 WHERE a = 11 AND B = 2 ORDER BY a LIMIT 10;
     ```
 
 11. WITH clause example
@@ -227,7 +227,7 @@ Recursive CTE is currently not supported.
     SELECT col1, col2 FROM cte;
     ```
 
-12. JOIN Exampel
+12. JOIN Example
 
     ```sql
     SELECT * FROM t1 LEFT JOIN (t2, t3, t4)
@@ -284,7 +284,7 @@ Recursive CTE is currently not supported.
 
 ## Best Practice
 
-1. ome additional knowledge about the SELECT clause
+1. Some additional knowledge about the SELECT clause
 
    - An alias can be specified for select_expr using AS alias_name. Aliases 
are used as column names in expressions and can be used in GROUP BY, ORDER BY 
or HAVING clauses. The AS keyword is a good habit to use when specifying 
aliases for columns.
 
@@ -356,17 +356,17 @@ Recursive CTE is currently not supported.
 
      DISTINCT removes duplicate rows.
 
-2. The main advantage of subqueries
+3. The main advantage of subqueries
 
     - Subqueries allow structured queries so that each part of a statement can 
be isolated.
     - Some operations require complex unions and associations. Subqueries 
provide other ways to perform these operations
 
-3. Speed up queries
+4. Speed up queries
 
     - Use Doris's partition and bucket as data filtering conditions as much as 
possible to reduce the scope of data scanning
     - Make full use of Doris's prefix index fields as data filter conditions 
to speed up query speed
     
-4. UNION
+5. UNION
 
    - Using only the union keyword has the same effect as using union disitnct. 
Since the deduplication work is more memory-intensive, the query speed using 
the union all operation will be faster and the memory consumption will be less. 
If users want to perform order by and limit operations on the returned result 
set, they need to put the union operation in the subquery, then select from 
subquery, and finally put the subquery and order by outside the subquery.
    
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
index f0e3e78eb17..d84fc76d5cf 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/database/SHOW-DATABASE-ID.md
@@ -6,7 +6,7 @@
 }
 ---
 
-### Description
+## Description
 
 This statement is used to find the corresponding database name based on the 
database id (only used by administrators)
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/database/SHOW-DATABASES.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/database/SHOW-DATABASES.md
index 1d695b9a327..6a255afae56 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/database/SHOW-DATABASES.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/database/SHOW-DATABASES.md
@@ -38,7 +38,7 @@ The user executing this SQL command must have at least the 
following permissions
 |:-----------|:------|:---------------|
 | SELECT_PRIV | Corresponding database | Requires read permission on the 
corresponding database |
 
-## 示例
+## Examples
 
 - Displays the names of all current databases.
 
diff --git 
a/versioned_docs/version-4.x/sql-manual/sql-statements/function/DROP-FUNCTION.md
 
b/versioned_docs/version-4.x/sql-manual/sql-statements/function/DROP-FUNCTION.md
index 40cb22b55f1..70a6b6c78e0 100644
--- 
a/versioned_docs/version-4.x/sql-manual/sql-statements/function/DROP-FUNCTION.md
+++ 
b/versioned_docs/version-4.x/sql-manual/sql-statements/function/DROP-FUNCTION.md
@@ -13,7 +13,7 @@ Delete a custom function.
 ## Syntax
 
 ```sql
-DROP [ GLOBAL ] <function_name> ( <arg_type> )
+DROP [ GLOBAL ] FUNCTION <function_name> ( <arg_type> )
 ```
 
 ## Required Parameters


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to