From 457ace590543864408c6c42ba661d3d3f4335339 Mon Sep 17 00:00:00 2001 From: Oliver Sanders Date: Thu, 25 Jan 2024 13:09:58 +0000 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com> --- cylc/flow/etc/examples/datetime-cycling/flow.cylc | 2 +- cylc/flow/etc/examples/inter-workflow-triggers/index.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/cylc/flow/etc/examples/datetime-cycling/flow.cylc b/cylc/flow/etc/examples/datetime-cycling/flow.cylc index 34badbf05b6..76945349987 100644 --- a/cylc/flow/etc/examples/datetime-cycling/flow.cylc +++ b/cylc/flow/etc/examples/datetime-cycling/flow.cylc @@ -12,7 +12,7 @@ """ [scheduling] - # start the workflow cycling at 00:00 this morning + # set the start of the graph to 00:00 this morning initial cycle point = previous(T00) [[graph]] diff --git a/cylc/flow/etc/examples/inter-workflow-triggers/index.rst b/cylc/flow/etc/examples/inter-workflow-triggers/index.rst index 185b8b70e54..0fd70b17d21 100644 --- a/cylc/flow/etc/examples/inter-workflow-triggers/index.rst +++ b/cylc/flow/etc/examples/inter-workflow-triggers/index.rst @@ -24,5 +24,5 @@ Inter-Workflow Triggering This pattern is useful where you have workflows that you want to keep decoupled from one another, but still need to exchange data. E.G. in operational meteorology we might have a global model (covering the whole Earth) and a - regional model (just covering a little bit of of) where the regional model + regional model (just covering a little bit of it) where the regional model obtains its boundary condition from the global model.