Skip to content

Commit 339b6de

Browse files
Apply suggestions from code review
Co-authored-by: Oliver Sanders <[email protected]>
1 parent e40c760 commit 339b6de

File tree

2 files changed

+3
-5
lines changed

2 files changed

+3
-5
lines changed

src/tutorial/furthertopics/message-triggers.rst

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,10 +53,8 @@ In order to get our workflow to trigger messages, we need to:
5353

5454
.. note::
5555

56-
Messages are recorded in the Workflow's scheduler log. Make sure that
57-
they convey useful information for users reading the log file. See
58-
:ref:`scheduler logs.cylc message` for details of how messages appear in
59-
the log file.
56+
The message will be recorded in the workflow's scheduler log.
57+
See :ref:`scheduler logs.cylc message` for details of how messages appear.
6058

6159
These outputs are then triggered during the running of the task.
6260
We can use these to manage tasks dependent on partially completed tasks.

src/user-guide/running-workflows/scheduler-log-files.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The information logged here includes:
3939
Cylc Message
4040
^^^^^^^^^^^^
4141

42-
The Scheduler Log also records messages sent by ``cylc message`` allowing users
42+
The Scheduler Log also records messages sent by ``cylc message`` allowing you
4343
to add custom messages to this log.
4444

4545
For example, if your task contained the following code:

0 commit comments

Comments
 (0)