build fixes

Author: hjoliver

src/7-to-8/major-changes/compatibility-mode.rst

@@ -36,7 +36,7 @@ The ``suite.rc`` filename triggers a backward compatibility mode in which:
 - ``succeeded`` task outputs are :ref:`*required* <User Guide Required Outputs>`,
   so in the absence of suicide triggers the scheduler will retain other
   :term:`final status` tasks in the :term:`n=0 window <n-window>` to stall the
-   workflow.
+  workflow.
 
   - (in Cylc 8, **all** outputs are *required* unless marked as
     :ref:`*optional* <User Guide Optional Outputs>` by the new ``?`` syntax)

src/glossary.rst

@@ -76,7 +76,8 @@ Glossary
 
       Active tasks are:
 
-      - Tasks which have some, but not all of their prerequisites satisfied.
+      - Tasks which have some, but not all of their
+        :term:`prerequisites <prerequisite>` satisfied.
       - ``waiting`` tasks, that are actively waiting on:
 
         - :term:`xtriggers <xtrigger>`.
@@ -567,7 +568,7 @@ Glossary
       if the :term:`wallclock time` exceeds some offset from the cycle point.
 
       Expired is a :term:`final status` - an expired task will not run
-      even if its prerequisites get satisfied.
+      even if its :term:`prerequisites <prerequisite>` get satisfied.
 
       The associated ``:expire`` :term:`output <task output>` can be used to
       trigger other tasks. It must be marked as an :term:`optional output`,
@@ -1384,7 +1385,7 @@ Glossary
 
    prerequisite
    task prerequisite
-      A task's prerequisites are the :term:`outputs <task outputs>` of
+      A task's prerequisites are the :term:`outputs <task output>` of
       parent tasks upstream in the graph that must be completed before
       it can run. Tasks are said to "depend on" their prerequisites, hence
       the term :term:`dependency graph <graph>`.
@@ -1769,6 +1770,7 @@ Glossary
 
       If no active tasks remain and all external constraints are satisfied,
       but the n=0 window contains tasks waiting with partially satisfied
-      :term:`prerequisites`, or tasks with :term:`final status` and
-        :term:`incomplete outputs <output completion>`, then the workflow is
+      :term:`prerequisites <prerequisite>`, or tasks with :term:`final status` and
+      :term:`incomplete outputs <output completion>`, then the workflow is
       not complete and the scheduler will :term:`stall` pending manual intervention.
+

src/user-guide/running-workflows/workflow-completion.rst

@@ -13,8 +13,8 @@ Workflow Completion
 
    If no active tasks remain and all external constraints are satisfied,
    but the n=0 window contains tasks waiting with partially satisfied
-   :term:`prerequisites`, or tasks with :term:`final status` and
-     :term:`incomplete outputs <output completion>`, then the workflow is
+   :term:`prerequisites <prerequisite>`, or tasks with :term:`final status` and
+   :term:`incomplete outputs <output completion>`, then the workflow is
    not complete and the scheduler will :term:`stall` pending manual intervention.
 
 
@@ -32,8 +32,8 @@ or otherwise) it will remain in the stalled state on restart.
 
 Stalls are often caused by unexpected task failures, either directly (tasks
 with :term:`final status` and :term:`incomplete outputs <output completion>`)
-or indirectly (tasks with partially satisfed prerequisites, downstream of an
-unexpected failure).
+or indirectly (tasks with partially satisfied :term:`prerequisites <prerequisite>`,
+downstream of an unexpected failure).
 
 .. warning::
 

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

@@ -185,7 +185,7 @@ configured).
 Task messages are validated by:
 
 .. autoclass:: cylc.flow.unicode_rules.TaskMessageValidator
-   :no-index:
+   :noindex:
 
 .. _job-scripts.aborting-on-error:
 

src/user-guide/writing-workflows/external-triggers.rst

@@ -402,6 +402,7 @@ success. The function signature is:
 .. automodule:: cylc.flow.xtriggers.xrandom
    :members: xrandom, validate
    :member-order: bysource
+   :noindex:
 
 An example xrandom trigger workflow: