fix broken link

Author: BohuTANG

docs/doc/14-sql-commands/00-ddl/20-table/10-ddl-create-table.md

@@ -80,7 +80,7 @@ AS SELECT query
 
 Creates a transient table. 
 
-Transient tables are used to hold transitory data that does not require a data protection or recovery mechanism. Dataebend does not hold historical data for a transient table so you will not be able to query from a previous version of the transient table with the Time Travel feature, for example, the [AT](./../../20-query-syntax/03-dml-at.md) clause in the SELECT statement will not work for transient tables. Please note that you can still [drop](./20-ddl-drop-table.md) and [undrop](./21-ddl-undrop-table.md) a transient table.
+Transient tables are used to hold transitory data that does not require a data protection or recovery mechanism. Dataebend does not hold historical data for a transient table so you will not be able to query from a previous version of the transient table with the Time Travel feature, for example, the [AT](./../../20-query-syntax/03-query-at.md) clause in the SELECT statement will not work for transient tables. Please note that you can still [drop](./20-ddl-drop-table.md) and [undrop](./21-ddl-undrop-table.md) a transient table.
 
 Transient tables help save your storage expenses because they do not need extra space for historical data compared to non-transient tables. See [example](#create-transient-table-1) for detailed explanations.
 

docs/doc/14-sql-commands/00-ddl/20-table/60-optimize-table.md

@@ -14,7 +14,7 @@ Snapshot, segment, and block are the concepts Databend uses for data storage. Da
 
 Databend automatically creates table snapshots upon data updates. A snapshot represents a version of the table's segment metadata.
 
-When working with Databend, you're most likely to access a snapshot with the snapshot ID when you retrieve and query a previous version of the table's data with the [AT](../../20-query-syntax/03-dml-at.md) clause.
+When working with Databend, you're most likely to access a snapshot with the snapshot ID when you retrieve and query a previous version of the table's data with the [AT](../../20-query-syntax/03-query-at.md) clause.
 
 A snapshot is a JSON file that does not save the table's data but indicate the segments the snapshot links to. If you run [FUSE_SNAPSHOT](../../../15-sql-functions/111-system-functions/fuse_snapshot.md) against a table, you can find the saved snapshots for the table.
 

docs/doc/14-sql-commands/00-ddl/20-table/70-ddl-restore-table.md

@@ -14,7 +14,7 @@ The capability to restore a table is subject to these conditions:
 
 - You cannot roll back after restoring a table to a prior state, but you can restore the table again to an earlier state.
 
-- Databend recommends this command for emergency recovery only. To query the history data of a table, use the [AT](../../20-query-syntax/03-dml-at.md) clause.
+- Databend recommends this command for emergency recovery only. To query the history data of a table, use the [AT](../../20-query-syntax/03-query-at.md) clause.
 
 ## Syntax
 

docs/doc/14-sql-commands/20-query-syntax/06-query-group-by.md

@@ -2,9 +2,9 @@
 title: GROUP BY
 ---
 
-The GROUP BY clause in Databend SQL allows you to group rows sharing the same group-by-item expressions and apply aggregate functions to the resulting groups. A group-by-item expression can be a column name, a number referencing a position in the [SELECT](./01-select.md) list, or a general expression.
+The GROUP BY clause in Databend SQL allows you to group rows sharing the same group-by-item expressions and apply aggregate functions to the resulting groups. A group-by-item expression can be a column name, a number referencing a position in the [SELECT](./01-query-select.md) list, or a general expression.
 
-Extensions include [GROUP BY CUBE](./08-group-by-cube.md), [GROUP BY GROUPING SETS](./07-group-by-grouping-sets.md), and [GROUP BY ROLLUP](./09-group-by-rollup.md).
+Extensions include [GROUP BY CUBE](./08-query-group-by-cube.md), [GROUP BY GROUPING SETS](./07-query-group-by-grouping-sets.md), and [GROUP BY ROLLUP](./09-query-group-by-rollup.md).
 
 ## Syntax
 

docs/doc/14-sql-commands/20-query-syntax/07-query-group-by-grouping-sets.md

@@ -2,7 +2,7 @@
 title: GROUP BY GROUPING SETS
 ---
 
-`GROUP BY GROUPING SETS` is a powerful extension of the [GROUP BY](./06-group-by.md) clause that allows computing multiple group-by clauses in a single statement. The group set is a set of dimension columns.
+`GROUP BY GROUPING SETS` is a powerful extension of the [GROUP BY](./06-query-group-by.md) clause that allows computing multiple group-by clauses in a single statement. The group set is a set of dimension columns.
 
 `GROUP BY GROUPING SETS` is equivalent to the UNION of two or more GROUP BY operations in the same result set:
 

docs/doc/14-sql-commands/20-query-syntax/08-query-group-by-cube.md

@@ -2,7 +2,7 @@
 title: GROUP BY CUBE
 ---
 
-`GROUP BY CUBE` is an extension of the [GROUP BY](./06-group-by.md) clause similar to [GROUP BY ROLLUP](./09-group-by-rollup.md). In addition to producing all the rows of a `GROUP BY ROLLUP`, `GROUP BY CUBE` adds all the "cross-tabulations" rows. Sub-total rows are rows that further aggregate whose values are derived by computing the same aggregate functions that were used to produce the grouped rows.
+`GROUP BY CUBE` is an extension of the [GROUP BY](./06-query-group-by.md) clause similar to [GROUP BY ROLLUP](./09-query-group-by-rollup.md). In addition to producing all the rows of a `GROUP BY ROLLUP`, `GROUP BY CUBE` adds all the "cross-tabulations" rows. Sub-total rows are rows that further aggregate whose values are derived by computing the same aggregate functions that were used to produce the grouped rows.
 
 A `CUBE` grouping is equivalent to a series of grouping sets and is essentially a shorter specification. The N elements of a CUBE specification correspond to `2^N GROUPING SETS`.
 

docs/doc/14-sql-commands/20-query-syntax/09-query-group-by-rollup.md

@@ -3,7 +3,7 @@ title: GROUP BY ROLLUP
 ---
 
 
-`GROUP BY ROLLUP` is an extension of the [GROUP BY](./06-group-by.md) clause that produces sub-total rows (in addition to the grouped rows). Sub-total rows are rows that further aggregate whose values are derived by computing the same aggregate functions that were used to produce the grouped rows.
+`GROUP BY ROLLUP` is an extension of the [GROUP BY](./06-query-group-by.md) clause that produces sub-total rows (in addition to the grouped rows). Sub-total rows are rows that further aggregate whose values are derived by computing the same aggregate functions that were used to produce the grouped rows.
 
 ## Syntax
 

docs/doc/14-sql-commands/20-query-syntax/index.md

@@ -3,7 +3,7 @@ title: Query Syntax
 slug: ./
 ---
 
-Databend supports querying using [SELECT](./01-dml-select.md) and the following basic syntax:
+Databend supports querying using [SELECT](./01-query-select.md) and the following basic syntax:
 
 ```sql
 [WITH]

website/blog/2022-07-19-databend-new-planner.md

@@ -37,7 +37,7 @@ You can also get a better experience when coding complex queries:
 
 The new SQL planner supports JOIN queries (INNER JOIN, OUTER JOIN, CROSS JOIN) and correlated subqueries, and provides a Hash Join algorithm to execute JOIN queries.
 
-For more information about how to use JOIN in Databend, go to https://databend.rs/doc/reference/sql/query-syntax/dml-join
+For more information about how to use JOIN in Databend, go to https://databend.rs/doc/reference/sql/query-syntax/query-join
 
 JOIN is a very important part of the OLAP query. In traditional star and snowflake schemas, we join dimensional tables with fact tables through the JOIN query to generate the resulting report.
 

website/blog/2022-09-08-find-peter.md

@@ -46,7 +46,7 @@ select snapshot_id,previous_snapshot_id, timestamp from fuse_snapshot('default',
 +----------------------------------+----------------------------------+----------------------------+
 ```
 
-You can now query the history data with a snapshot or timestamp by including the [AT](https://databend.rs/doc/reference/sql/query-syntax/dml-at) clause in the SELECT statement:
+You can now query the history data with a snapshot or timestamp by including the [AT](https://databend.rs/doc/reference/sql/query-syntax/query-at) clause in the SELECT statement:
 
 ```sql
 select * from spiderman at(snapshot=>'a2801ed9656d42c9812f2921214f0795');