Remove references to reflow (now 'new flow').

cylc · Mar 17, 2022 · e8f9857 · e8f9857
1 parent b1158d2
commit e8f9857
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 9 deletions.
diff --git a/src/7-to-8/caveats.rst b/src/7-to-8/caveats.rst
@@ -13,10 +13,9 @@ Trigger Edit
 
    * https://github.com/cylc/cylc-flow/issues/3751
 
-Reflow
-   The new "reflow" functionality, which allows multiple
-   (potentially concurrent) executions of the same workflow in a single
-   :term:`scheduler`, is not fully supported by all commands
+Multiple Flows
+   The new :term:`scheduler` can manage multiple flows in the workflow graph.
+   Commands and options for interacting with flows are still being refined.
 
 
 Browser Based UI

diff --git a/src/7-to-8/major-changes/cli.rst b/src/7-to-8/major-changes/cli.rst
@@ -32,7 +32,7 @@ renamed or removed.
 ``cylc checkpoint``
   - Database checkpoints are no longer needed.
   - All task state changes are written to the database when they occur.
-  - Remaining use cases can be handled by :term:`reflows <reflow>`
+  - Remaining use cases can be handled by starting a new :term:`flow`
     which allow a new execution of the graph to be started from an
     arbitrary point in the graph.
 ``cylc conditions``

diff --git a/src/7-to-8/major-changes/play-pause-stop.rst b/src/7-to-8/major-changes/play-pause-stop.rst
@@ -41,7 +41,8 @@ The ``cylc play`` command will always pick up where it left off (a
 If you want to re-run the entire workflow again from the start either:
 
 * :ref:`Install a new run<Using Cylc Install>`.
-* Or if you want to keep the data from the old run start a :term:`reflow`.
+* Or if you want to keep the data from the old run start a new :term:`flow` at
+  the beginning of the graph, and stop the original flow.
 
 It is still possible to re-run workflows in-place in the Cylc 7 manner, however,
 this is discouraged.

diff --git a/src/7-to-8/major-changes/scheduling.rst b/src/7-to-8/major-changes/scheduling.rst
@@ -37,9 +37,7 @@ Cylc 8 has a new scheduling algorithm that:
 
   - (to fully understand which tasks appeared in the Cylc 7 GUI you had to
     understand the scheduling algorithm)
-- Supports a powerful new capability called :term:`reflow`: you can trigger
-  multiple concurrent flows in the same graph at once, managed by the same
-  scheduler
+- Supports multiple concurrent :term:`flows<flow>` within the same workflow.
 - Can start a workflow from any task or tasks in the graph (no need for
   checkpoint restart)
 - Can limit activity within as well as across cycles, without risking a stall