more spelling fixes

Author: wxtim

src/7-to-8/caveats.rst

@@ -107,6 +107,6 @@ Authorization
    the UI doesn't yet provide easy access to other users' UI Servers.
 
 CLI Via UIS
-   The ability to route Cylc commands via the UIS is planned for a future relase
+   The ability to route Cylc commands via the UIS is planned for a future release
 
    * https://github.com/cylc/cylc-flow/issues/3528

src/glossary.rst

@@ -620,7 +620,7 @@ Glossary
       Implicit tasks submit real jobs that just exit without doing anything
       useful. They may be useful placeholders during workflow development but
       are not allowed by default because they can be created accidentally by
-      smply misspelling a task name in the graph or under ``[runtime]``.
+      simply misspelling a task name in the graph or under ``[runtime]``.
 
       Here ``bar`` is implicit:
 

src/reference/config/file-format.rst

@@ -55,7 +55,7 @@ Boolean Values
 
 
 Sections and Sub-sections
-   Settings have a level-dependendent number of square brackets:
+   Settings have a level-dependent number of square brackets:
 
    .. code-block:: cylc
 
@@ -97,7 +97,7 @@ Duplicate Sections and Items
       [animals]
         dog = fido
         cat = dusty
- 
+
    is equivalent to this:
 
    .. code-block:: cylc

src/tutorial/scheduling/datetime-cycling.rst

@@ -53,7 +53,7 @@ ISO8601 Datetimes
    For brevity we may omit seconds (and minutes) from the time i.e:
    ``20000101T0000`` (``20000101T00``).
 
-   For reability we can add hyphens (``-``) between the date components
+   For readability we can add hyphens (``-``) between the date components
    and colons (``:``) between the time components.
    This is optional, but if you do this you must use both hyphens *and* colons.
 

src/tutorial/scheduling/further-scheduling.rst

@@ -59,7 +59,7 @@ Clock Triggers
 .. ifnotslides::
 
    In Cylc, :term:`cycle points <cycle point>` are just labels. Tasks are
-   triggered when their dependencies are met regardles of their cycle point.
+   triggered when their dependencies are met regardless of their cycle point.
    But we can use *clock triggers* to force tasks to wait for a particular time,
    relative to their cycle point time, before running.
    This is necessary for certain operational and monitoring systems, e.g. for

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

@@ -9,7 +9,7 @@ scheduler program when they are ready to run, and how to define new
 
 .. note::
 
-   For the requirements a command, script, or program, must fulfill in order to
+   For the requirements a command, script, or program, must fulfil in order to
    function as a Cylc task, see :ref:`TaskImplementation`.
 
 When a task is ready Cylc generates a :term:`job script` (see :ref:`JobScripts`).
@@ -156,7 +156,7 @@ Overriding The Job Submission Command
 -------------------------------------
 
 To change the form of the actual command used to submit a job you
-need to define a new 
+need to define a new
 :cylc:conf:`global.cylc[platforms][<platform name>]job runner command template`.
 
 .. code-block:: cylc

src/user-guide/writing-workflows/scheduling.rst

@@ -1334,7 +1334,7 @@ Tasks that depend on their own previous-cycle instance can be declared as
        [[graph]]
            T00,T12 = "foo => bar"
 
-However, this feature is deprecated in favor of explicit intercycle triggers
+However, this feature is deprecated in favour of explicit intercycle triggers
 which expose the associated scheduling behaviour in the graph:
 
 .. code-block:: cylc

src/workflow-design-guide/general-principles.rst

@@ -117,8 +117,8 @@ they can run directly on target platforms, and you can rerun them later without
 restarting the workflow.
 
 
-Confining Ouput To The Run Directory
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Confining Output To The Run Directory
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Output files should be confined to the run directory tree. Then all
 output is easy to find, multiple instances of the same workflow can run

src/workflow-design-guide/portable-workflows.rst

@@ -263,7 +263,7 @@ workflow config file to automatically set site-specific workflow inputs and ther
 avoid the need to make manual changes every time you check out and run a new
 version. The site switch itself has to be set of course, but there may be other
 settings too such as model parameters for a standard local test domain. Just
-put these settings in ``opt/rose-suite-niwa.conf`` (for site "niwa")
+put these settings in ``opt/rose-suite-niwa.conf`` (for site ``niwa``)
 and run the workflow with ``rose suite-run -O niwa``.