again more changes

docs/exercise5.rst

@@ -7,17 +7,17 @@ It is implemented as a python script
 
     1. All parameters are loaded at the beginning from a JSON document 
        **parameters.json**.
-    2. The steps candidates_apply() and screen_candidates() are applied as long 
+    2. The steps candidates_apply() and screen_candidates() are repeated as long 
        as the size of the canditate list is smaller than ``number_to_invite``.
 
 
-The anatomy of a Firetask
--------------------------
+Anatomy of Firetasks
+--------------------
 
 All firetasks are classes derived from the ``FiretaskBase`` class. Many built-in 
 Firetasks are available in the upstream FireWorks, such as the ``ScriptTask``, 
-``PyTask``, FileTransferTask. Additional firetasks can be written for generic or 
-specific purposes.
+``PyTask``, FileTransferTask. Additional firetasks can be written for both 
+generic and specific purposes.
 
 The skeleton of a Firetask looks like this::
 
@@ -79,8 +79,8 @@ The resulting workflow, which is given in **dataloader.json**, must be successfu
 running with no further modifications.
 
 **Hint**: You can use the ``load()`` method from the ``json`` package to load 
-JSON documents as list or dictionaries and then return the structure via 
-``FWAction`` (see example). 
+JSON documents as list or dictionaries and then return a ``FWAction`` object 
+with ``update_spec`` and the structure (see above example). 
 
 
 Problem 5.2: Conditional Repeater Task
@@ -95,4 +95,4 @@ to insert a workflow section (sub-workflow) dynamically::
 
     workflow_obj = load_object(workflow_dict)
     actions = ['detours': workflow_obj]
-
+    return FWAction(*actions)