Apply suggestions from code review

Co-authored-by: Hilary James Oliver <[email protected]>

Author: oliver-sanders

src/tutorial/furthertopics/broadcast.rst

@@ -143,6 +143,6 @@ Further Reading
 The :ref:`cylc-broadcast` section in the user guide contains more detail
 on broadcasts.
 
-The GUI contains an "Edit Runtime" utility which loads the tasks configuration
+The GUI contains an "Edit Runtime" utility which loads the task's configuration
 into a form. Any changes you make are then broadcasted to the task.
 See :ref:`interventions.edit-a-tasks-configuration`.

src/user-guide/running-workflows/cylc-broadcast.rst

@@ -12,15 +12,15 @@ Broadcasts can be helpful for:
 
 * Quickly developing tasks without having to
   :ref:`edit and reload the workflow configuration <interventions.edit-the-workflow-configuration>`.
-* Sending small amounts of data from task to another (e.g. file paths).
+* Sending small amounts of data from a running task to other upcoming tasks (e.g. file paths).
 * Orchestrating production workflows from an external system.
 
-Once issued, broadcasts last for the life of the workflow and will persist if
-the workflow is shutdown and restarted (unless manually "cleared").
-
-However, broadcasts which target specific cycles will eventually be
+Broadcasts which target specific cycles will eventually be
 :ref:`expired <user_guide.broadcast.expiry>` when no longer needed.
 
+Otherwise, broadcasts last for the life of the workflow and will persist if
+the workflow is shutdown and restarted (unless manually "cleared").
+
 .. seealso::
 
    :ref:`broadcast-tutorial`