Address review comments.

Author: hjoliver

src/glossary.rst

@@ -344,7 +344,6 @@ Glossary
          "1/bar" -> "2/bar" -> "3/bar"
 
 
-
       .. seealso::
 
          * :ref:`tutorial-integer-cycling`
@@ -362,14 +361,14 @@ Glossary
 
 
    cycle point
-      The unique label given to tasks that belong to a particular :term:`cycle`.
+      The label given to tasks that belong to a particular :term:`cycle`.
       For :term:`integer cycling` these will be integers, e.g. ``1``, ``2``,
       ``3``, etc.
       For :term:`datetime cycling` they will be :term:`ISO 8601` datetimes,
       e.g. ``2000-01-01T00:00Z``.
 
-      Cylc has no global cycle loop, so each task instance has its own cycle
-      point label.
+      Cylc can run multiple cycles at once, dependencies allowing, so each
+      task instance has its own cycle point label.
 
       .. seealso::
 

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

@@ -31,12 +31,12 @@ to allow you to intervene, e.g. by manually triggering an incomplete
 task after fixing the bug that caused it to fail.
 
 If a stalled workflow does eventually shut down, on the stall timeout
-or by stop command, it will immediately stall again on restart.
+or by stop command, it will immediately stall again on restart to await
+manual intervention.
 
 .. warning::
 
-   At present you have to look at the :term:`scheduler log` to see
-   which tasks caused a stall.
+   Look in the :term:`scheduler log` to see which tasks caused a stall.
 
 .. seealso::
 

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

@@ -843,7 +843,7 @@ Late Events
   The scheduler can only check for lateness once a task becomes
   :term:`active <active task>`. In Cylc 8 this usually means the task
   is ready, or nearly ready, to run, which limits the usefulness of late
-  events as currently implemented.
+  events.
 
 If a real time (clock-triggered) workflow performs fairly consistently from one
 cycle to the next, you may want to be notified when certain tasks are running

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

@@ -2233,7 +2233,7 @@ held back, and are displayed in the GUI/Tui with a small circle above them.
 
 .. note::
 
-   Tasks in the :term:`n=1 window <n-window>` are not displayed as runahead
+   Tasks in the :term:`n>=1 window <n-window>` are not displayed as runahead
    limited; they form the future graph and are not yet being actively limited.
 
 As the workflow advances and active cycles complete, the runahead limit moves