Skip to content

Commit 666800d

Browse files
authored
whilst -> while (#757)
1 parent b1f6188 commit 666800d

File tree

5 files changed

+7
-7
lines changed

5 files changed

+7
-7
lines changed

src/tutorial/furthertopics/broadcast.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ running workflow, on-the-fly.
1111
Purpose
1212
-------
1313

14-
``cylc broadcast`` can be used to change any ``[runtime]`` setting whilst the
14+
``cylc broadcast`` can be used to change any ``[runtime]`` setting while the
1515
workflow is running.
1616

1717
The standard use of ``cylc broadcast`` is to update the workflow to an
@@ -57,7 +57,7 @@ the log entry will look like this::
5757
10120101T0000Z - We are the knights who say "ni"!
5858

5959
The ``cylc broadcast`` command enables us to change runtime configuration
60-
whilst the workflow is running. For instance we could change the value of the
60+
while the workflow is running. For instance we could change the value of the
6161
``WORD`` environment variable using the command::
6262

6363
cylc broadcast tutorial-broadcast -n announce -s "[environment]WORD=it"

src/tutorial/furthertopics/message-triggers.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Usage
2020
-----
2121

2222
:term:`Message triggers <message trigger>` are particularly useful if we have
23-
a long running task and we want to produce multiple tailored outputs whilst
23+
a long running task and we want to produce multiple tailored outputs while
2424
this task is running, rather than having to wait for the task to
2525
complete.
2626

src/user-guide/cheat-sheet.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ First, make your required changes to the files in the workflow's
131131
# validate, reinstall and reload the workflow
132132
cylc vr <id>
133133

134-
If you want to quickly edit a task's configuration, e.g. whilst developing a
134+
If you want to quickly edit a task's configuration, e.g. while developing a
135135
workflow or testing changes, the
136136
:ref:`"Edit Runtime" feature <interventions.edit-a-tasks-configuration>`
137137
in the GUI can be convenient.

src/user-guide/interventions/index.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Interventions
55

66
Sometimes things don't go to plan!
77

8-
So Cylc allows you to take manual control of your workflow whilst it's running
8+
So Cylc allows you to take manual control of your workflow while it's running
99
allowing you to do things like edit a task's configuration, re-run a section
1010
of your graph or override task outputs.
1111

@@ -445,7 +445,7 @@ Hold The Workflow And Trigger Tasks One By One
445445
----------------------------------------------
446446

447447
:Example:
448-
I want to hold back the workflow whilst I manually run one or more tasks
448+
I want to hold back the workflow while I manually run one or more tasks
449449
to fix a problem or test a task.
450450

451451
:Solution:

src/user-guide/task-implementation/job-submission.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -220,7 +220,7 @@ Any tasks recorded in the *submitted* or *running* states at workflow
220220
restart are automatically polled to determine what happened to them while the
221221
workflow was down.
222222

223-
By default, regular polling also takes place every 15 minutes whilst a job is
223+
By default, regular polling also takes place every 15 minutes while a job is
224224
submitted or running. The default polling intervals can be overridden in the
225225
global configuration:
226226

0 commit comments

Comments
 (0)