Skip to content

Commit b949d08

Browse files
committed
docs: add further readings
1 parent bd97fdf commit b949d08

File tree

2 files changed

+10
-3
lines changed

2 files changed

+10
-3
lines changed

docs/docs/core/flow_methods.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
title: Run a Flow
2+
title: Operate a Flow
33
toc_max_heading_level: 4
4-
description: Run a CocoIndex Flow, including build / update data in the target and evaluate the flow without changing the target.
4+
description: Operate a CocoIndex Flow, including build / update data in the target and evaluate the flow without changing the target.
55
---
66

77
import Tabs from '@theme/Tabs';
88
import TabItem from '@theme/TabItem';
99

10-
# Run a CocoIndex Flow
10+
# Operate a CocoIndex Flow
1111

1212
After a flow is defined as discussed in [Flow Definition](/docs/core/flow_def), you can start to transform data with it.
1313

docs/docs/tutorials/manage_flow_dynamically.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -293,3 +293,10 @@ From this tutorial, we walked through major flow management / operation APIs pro
293293
For simplicity, we use an in-memory `dict` as source of truth for the flow parameters.
294294
You can replace it with your own mechanism, e.g. table from a database, a configuration file, etc.
295295
You can trigger these APIs from your applications specific to your use case, e.g. from a specific API endpoint of a web server.
296+
297+
## Further readings
298+
299+
You can see the following documents for more details:
300+
301+
* [CocoIndex Flow Definition: Entry Point](/docs/core/flow_def#entry-point)
302+
* [Operate a Flow](/docs/core/flow_methods)

0 commit comments

Comments
 (0)