refactor: continuous aggregation to flow computation

docs/getting-started/quick-start.md

@@ -313,7 +313,7 @@ ORDER BY
 
 ### Continuous aggregation
 
-For further analysis or reduce the scan cost when aggregating data frequently, you can save the aggregation results to another tables. This can be implemented by using the [continuous aggregation](/user-guide/continuous-aggregation/overview.md) feature of GreptimeDB.
+For further analysis or reduce the scan cost when aggregating data frequently, you can save the aggregation results to another tables. This can be implemented by using the [continuous aggregation](/user-guide/flow-computation/overview.md) feature of GreptimeDB.
 
 For example, aggregate the API error number by 5-second and save the data to table `api_error_count`.
 

docs/reference/sql/create.md

@@ -138,7 +138,7 @@ The `ttl` value can be one of the following:
     - `months`, `month`, `M` – defined as 30.44 days
     - `years`, `year`, `y` – defined as 365.25 days
 - `forever`, `NULL`, an empty string `''` and `0s` (or any zero length duration, like `0d`), means the data will never be deleted.
-- `instant`, note that database's TTL can't be set to `instant`. `instant` means the data will be deleted instantly when inserted, useful if you want to send input to a flow task without saving it, see more details in [flow management documents](/user-guide/continuous-aggregation/manage-flow.md#manage-flows).
+- `instant`, note that database's TTL can't be set to `instant`. `instant` means the data will be deleted instantly when inserted, useful if you want to send input to a flow task without saving it, see more details in [flow management documents](/user-guide/flow-computation/manage-flow.md#manage-flows).
 - Unset, `ttl` can be unset by using `ALTER TABLE <table-name> UNSET 'ttl'`, which means the table will inherit the database's ttl policy (if any).
 
 If a table has its own TTL policy, it will take precedence over the database TTL policy.
@@ -420,7 +420,7 @@ AS
 <SQL>;
 ```
 
-For the statement to create or update a flow, please read the [flow management documents](/user-guide/continuous-aggregation/manage-flow.md#create-a-flow).
+For the statement to create or update a flow, please read the [flow management documents](/user-guide/flow-computation/manage-flow.md#create-a-flow).
 
 ## CREATE VIEW
 

docs/user-guide/concepts/features-that-you-concern.md

@@ -41,7 +41,7 @@ GreptimeDB resolves this issue by:
 
 ## Does GreptimeDB support continuous aggregate or downsampling?
 
-Since 0.8, GreptimeDB added a new function called `Flow`, which is used for continuous aggregation.  Please read the [user guide](/user-guide/continuous-aggregation/overview.md).
+Since 0.8, GreptimeDB added a new function called `Flow`, which is used for continuous aggregation.  Please read the [user guide](/user-guide/flow-computation/overview.md).
 
 ## Can I store data in object storage in the cloud?
 

docs/user-guide/concepts/key-concepts.md

@@ -52,4 +52,4 @@ The data displayed in a view is retrieved dynamically from the underlying tables
 
 ## Flow
 
-A `flow` in GreptimeDB refers to a [continuous aggregation](/user-guide/continuous-aggregation/overview.md) process that continuously updates and materializes aggregated data based on incoming data.
+A `flow` in GreptimeDB refers to a [continuous aggregation](/user-guide/flow-computation/overview.md) process that continuously updates and materializes aggregated data based on incoming data.