Apply suggestions from code review

Co-authored-by: Yiran <cuiyiran3@gmail.com>
GreptimeTeam · May 20, 2024 · 5193da7 · 5193da7
1 parent d56ae7b
commit 5193da7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/nightly/en/user-guide/continuous-aggregation/overview.md b/docs/nightly/en/user-guide/continuous-aggregation/overview.md
@@ -67,7 +67,7 @@ SELECT * FROM out_num_cnt;
 Let's try to insert more data into `numbers_input` table.
 
 ```sql
-public=> INSERT INTO numbers_input 
+INSERT INTO numbers_input 
 VALUES
  (23,1625097601000),
  (24,1625097601500);

diff --git a/docs/nightly/en/user-guide/continuous-aggregation/query.md b/docs/nightly/en/user-guide/continuous-aggregation/query.md
@@ -6,7 +6,7 @@ Only two kinds of expression are allowed after `SELECT` keyword:
 - Aggregate functions: see the reference in [Expression](./expression.md) for detail.
 - Scalar functions: like `col`, `to_lowercase(col)`, `col + 1`, etc. This part is the same as the normal `SELECT` clause in GreptimeDB.
 
-Then each query should have a `FROM` clause to specify the source table. The referenced source table should be one in the flow's source tables in `CREATE FLOW` clause. Join is currently not supported so each query can reference only one table.
+The query should have a `FROM` clause to identify the source table. As the join clause is currently not supported, the query can only aggregate columns from a single table.
 
 `GROUP BY` clause works as in a normal query. It groups the data by the specified columns. One special thing is the time window functions `hop()` and `tumble()` described in [Define Time Window](./define-time-window.md) part. They are used in the `GROUP BY` clause to define the time window for the aggregation. Other expressions in `GROUP BY` can be either literal, column or scalar expressions.