remove alternative spellings of paramete?ri[sz]e (#563)

Author: wxtim

src/dictionaries/words

@@ -29,6 +29,7 @@ env
 etc
 executables
 facade
+fallback
 filename
 filenames
 filesystem
@@ -82,10 +83,8 @@ obs
 offline
 onwards
 packjob
-parameterisation
-parameterise
-parameterised
 parameterization
+parameterize
 parameterized
 passX
 passphrase

src/glossary.rst

@@ -1219,8 +1219,8 @@ Glossary
 
 
    task parameters
-   parameterisation
-      Task parameterisation is one way of consolidating configuration in the
+   parameterization
+      Task parameterization is one way of consolidating configuration in the
       :cylc:conf:`flow.cylc` file. Cylc implicitly loops over ranges or lists
       of pre-defined parameters to automatically generate sets of similar
       tasks.
@@ -1247,7 +1247,7 @@ Glossary
       .. seealso::
 
          * :ref:`Cylc User Guide <User Guide Param>`
-         * :ref:`Cylc tutorial <tutorial-cylc-parameterisation>`
+         * :ref:`Cylc tutorial <tutorial-cylc-parameterization>`
 
 
    family

src/tutorial/runtime/configuration-consolidation/index.rst

@@ -100,7 +100,7 @@ The ``cylc config`` Command
 
       A primary use of ``cylc config`` is inspecting the
       ``[runtime]`` section of a workflow. However, the command does not
-      expand :term:`parameterisations <parameterisation>` and
+      expand :term:`parameterizations <parameterization>` and
       :term:`families <family>` in the workflow :term:`graph`. To see the
       expanded graph use the ``cylc graph`` command.
 
@@ -129,7 +129,7 @@ The ``cylc config`` Command
 
 .. ifslides::
 
-   Note that ``cylc config`` doesn't expand families or parameterisations
+   Note that ``cylc config`` doesn't expand families or parameterizations
    in the :term:`graph`. Use ``cylc graph`` to visualise these.
 
    .. TODO - Raise and issue for this, note cylc config and cylc view.
@@ -146,7 +146,7 @@ The Three Approaches
 
 * :ref:`families <tutorial-cylc-families>`
 * :ref:`jinja2 <tutorial-cylc-jinja2>`
-* :ref:`parameters <tutorial-cylc-parameterisation>`
+* :ref:`parameters <tutorial-cylc-parameterization>`
 
 
 .. _cylc-tutorial-consolidation-conclusion:
@@ -165,7 +165,7 @@ Which Approach To Use
    * `Jinja2`_ is good at configuring settings which apply to the entire workflow
      rather than just a single task, as we can define variables then use them
      throughout the workflow.
-   * :term:`Parameterisation <parameterisation>` works best for describing tasks
+   * :term:`Parameterization <parameterization>` works best for describing tasks
      which are very similar but which have subtly different configurations
      (e.g. different arguments or environment variables).
 
@@ -177,7 +177,7 @@ Which Approach To Use
       Collecting tasks into broad groups.
    Jinja2
       Configuration settings which apply to the entire workflow.
-   Parameterisation
+   Parameterization
       Tasks which are similar.
 
 .. nextslide::

src/tutorial/runtime/configuration-consolidation/jinja2.rst

@@ -169,7 +169,7 @@ This would result in:
    .. rubric:: This practical continues on from the
       :ref:`families practical <cylc-tutorial-families-practical>`.
 
-   Next section: :ref:`tutorial-cylc-parameterisation`
+   Next section: :ref:`tutorial-cylc-parameterization`
 
 
 .. _cylc-tutorial-jinja2-practical:

src/tutorial/runtime/configuration-consolidation/parameters.rst

@@ -1,11 +1,11 @@
-.. _tutorial-cylc-parameterisation:
+.. _tutorial-cylc-parameterization:
 
 
-Parameterised Tasks
+Parameterized Tasks
 ===================
 
 
-Parameterised tasks (see :term:`parameterisation`) provide a way of implicitly
+Parameterized tasks (see :term:`parameterization`) provide a way of implicitly
 looping over tasks without the need for Jinja2.
 
 
@@ -197,10 +197,10 @@ Parameters can be either strings or integers:
    .. rubric:: This practical continues on from the
       :ref:`Jinja2 practical <cylc-tutorial-jinja2-practical>`.
 
-   4. **Use Parameterisation To Consolidate The** ``get_observations``
+   4. **Use Parameterization To Consolidate The** ``get_observations``
       **Tasks**.
 
-      Next we will parameterise the ``get_observations`` tasks.
+      Next we will parameterize the ``get_observations`` tasks.
 
       Add a parameter called ``station``:
 
@@ -273,7 +273,7 @@ Parameters can be either strings or integers:
 
          cylc config . -i "[runtime]"
 
-      Finally we can use this parameterisation to simplify the workflow's
+      Finally we can use this parameterization to simplify the workflow's
       graphing. Replace the ``get_observations`` lines in the graph with
       ``get_observations<station>``:
 
@@ -294,14 +294,14 @@ Parameters can be either strings or integers:
          in the graph so you must use ``cylc graph`` to inspect changes to the
          graphing.
 
-   #. **Use Parameterisation To Consolidate The** ``post_process`` **Tasks**.
+   #. **Use Parameterization To Consolidate The** ``post_process`` **Tasks**.
 
       At the moment we only have one ``post_process`` task
       (``post_process_exeter``), but suppose we wanted to add a second task for
       Edinburgh.
 
       Create a new parameter called ``site`` and set it to contain ``exeter``
-      and ``edinburgh``. Parameterise the ``post_process`` task using this
+      and ``edinburgh``. Parameterize the ``post_process`` task using this
       parameter.
 
       .. hint::
@@ -325,7 +325,7 @@ Parameters can be either strings or integers:
                  station = aldergrove, camborne, heathrow, shetland
             +        site = exeter, edinburgh
 
-         Next we parameterise the task in the graph:
+         Next we parameterize the task in the graph:
 
          .. code-block:: diff
 

src/user-guide/running-workflows/task-job-states.rst

@@ -9,7 +9,7 @@ icons like this: |task-running|.
 
 **Jobs** are less abstract; they represent real job scripts submitted to run
 on a :term:`job platform`, or the final status of those real jobs. In the Cylc
-UI, job states have colored icons like this: |job-running|.
+UI, job states have coloured icons like this: |job-running|.
 
 A single task can have multiple jobs, by automatic retry or manual triggering.
 

src/user-guide/writing-workflows/parameterized-tasks.rst

@@ -4,7 +4,7 @@ Task Parameters
 ===============
 
 Cylc can automatically generate related tasks and dependencies by expanding
-:term:`parameterized <parameterisation>` names over lists or ranges of
+:term:`parameterized <parameterization>` names over lists or ranges of
 values. Uses for this include:
 
 - Generating an ensemble of similar model runs