fix small spelling errors (#396)

Author: wxtim

src/7-to-8/major-changes/play-pause-stop.rst

@@ -12,7 +12,7 @@ Play Pause Stop
 Overview
 --------
 
-Cylc 8 uses a simplfied model for controlling workflows based on the controls
+Cylc 8 uses a simplified model for controlling workflows based on the controls
 of a tape player.
 
 There are now three controls, play, pause and stop:

src/7-to-8/summary.rst

@@ -434,7 +434,7 @@ Security
 
 .. seealso::
 
-   Techincal reference:
+   Technical reference:
 
    * :ref:`CylcUIServer.architecture`
 

src/glossary.rst

@@ -497,7 +497,7 @@ Glossary
    intercycle dependency
    intercycle trigger
       In a :term:`cycling workflow <cycling>`, intercycle dependence refers to
-      a :term:`task` dependending on other tasks at different cycle points.
+      a :term:`task` depending on other tasks at different cycle points.
 
       For example, in the following workflow the task ``bar`` depends on
       its own previous instance:
@@ -552,7 +552,7 @@ Glossary
       A qualifier is what follows :term:`task` or family :term:`family` names
       after a colon ``:`` in :term:`triggers <trigger>`, in the :term:`graph`,
       to specify exactly which :term:`task outputs <task output>` must be
-      completed for the :term:`dependency` to be satisified.
+      completed for the :term:`dependency` to be satisfied.
 
       For example, in ``foo:start => bar``, the ``:start`` qualifier means that
       the ``started`` output of task ``foo`` must be completed to satisfy the
@@ -1270,7 +1270,7 @@ Glossary
 
    task output
       Task outputs mark the progression of a :term:`task` from waiting (for
-      prerequisites to be satisified) through to success or failure at run
+      prerequisites to be satisfied) through to success or failure at run
       time. Downstream tasks can trigger off of the outputs of other tasks, as
       determined by the :term:`graph`.
 

src/reference/environments/conda.rst

@@ -27,7 +27,7 @@ The simplest Cylc installation consists only of `Cylc Flow`_:
 .. tip::
 
    We suggest installing `Cylc Flow`_ at a "minor" version (e.g. ``8.1`` rather
-   than ``8.1.2``) to pick up the latest "maintainance" release.
+   than ``8.1.2``) to pick up the latest "maintenance" release.
 
 If you do not specify your Python version you will be provided with the most
 recent compatible one.
@@ -112,7 +112,7 @@ Working With Other Conda Channels
 ---------------------------------
 
 Cylc projects are published to Conda Forge and the above environments install
-all dependences from Conda Forge.
+all dependencies from Conda Forge.
 
 If you want to install other dependencies (e.g. Python), from other channels
 (e.g. Anaconda), list the dependency explicitly and place the channel *above*

src/user-guide/introduction/what-is-cylc.rst

@@ -4,7 +4,7 @@ What is Cylc?
 Cylc (pronounced silk) is a workflow engine, a system that automatically
 executes tasks according to schedules and dependencies.
 
-In a Cylc workflow each step is an application: an excecutable command, script,
+In a Cylc workflow each step is an application: an executable command, script,
 or program. Cylc runs each task as soon as it is appropriate to do so.
 
 

src/user-guide/sharing-access-to-workflows.rst

@@ -30,7 +30,7 @@ There are three methods of identifying a user to grant access to:
 
 
 Using glob (``*``) to pattern match usernames and group names is not currently
-supported. 
+supported.
 
 Permissions are additive. If the user appears elsewhere in configuration, for
 example as a member of a system group, the permission level is taken as the
@@ -51,7 +51,7 @@ Assigning permissions can be done in two ways:
 Using both methods is supported, e.g ["READ", "stop", "pause"]
 
 Individual Operations
-^^^^^^^^^^^^^^^^^^^^^ 
+^^^^^^^^^^^^^^^^^^^^^
 To assign users permissions, you can list the operations you wish to grant
 
 .. code-block:: python
@@ -117,7 +117,7 @@ to operations in these groups, use ``!READ``, ``!CONTROL``, ``!ALL``.
 .. note::
 
    The ``READ`` access group is shorthand for all read-only operations. At present,
-   this is soley the ``read`` operation, which grants access to GraphQL queries and
+   this is solely the ``read`` operation, which grants access to GraphQL queries and
    subscriptions, and enables users to see the workflows in the UI. In future
    the ``READ`` access group may be extended.
 
@@ -164,7 +164,7 @@ In this scenario:
   workflows, even if ``user1`` is a member of the system ``groupA``. This is due
   to negations taking precedence over additions.
 
-- ``"user2"`` is not permitted to view workflows, or perform any operations. 
+- ``"user2"`` is not permitted to view workflows, or perform any operations.
 
 .. _site_configuration:
 
@@ -190,7 +190,7 @@ Defaults and Limits
 ^^^^^^^^^^^^^^^^^^^
 Sites set both limits and defaults for users.
 
-- ``limit`` determines the maximum access users can grant to their workflows. 
+- ``limit`` determines the maximum access users can grant to their workflows.
 
 - ``default`` sets a default access level, which applies if the user does
   not appear in the user-authorization configuration (via explicit user name or group).
@@ -295,7 +295,7 @@ If authorization is not performing as expected, check
 - you have provided ``read`` permissions, which enables the user to see your
   workflows.
 
-- check the spelling in your configuration. The correct spelling is 
+- check the spelling in your configuration. The correct spelling is
   ``c.CylcUIServer.user_authorization``
 
 - the server has been started by the user of the workflows you are trying to

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

@@ -41,7 +41,7 @@ A Cylc :term:`source directory` contains:
 
    Task jobs can also run scripting defined in the ``flow.cylc`` file,
    executables installed to user-defined locations of the workflow run
-   directory, and external excutables.
+   directory, and external executables.
 
 ``lib/python/`` (optional)
    A directory for Python modules. It is added to ``$PYTHONPATH`` in

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

@@ -6,7 +6,7 @@ Scheduling Configuration
 .. tutorial:: Scheduling Tutorial <tutorial-scheduling>
 
 The :cylc:conf:`[scheduling]` section of the :cylc:conf:`flow.cylc` file
-defines what tasks exist in the worklow, in a :term:`dependency graph <graph>`,
+defines what tasks exist in the workflow, in a :term:`dependency graph <graph>`,
 and when they should run, relative to each other and to constraints such as
 :term:`clock triggers <clock trigger>`, :term:`external triggers <external
 trigger>`, and :term:`internal queues <internal queue>`