update FAQ

doc/source/Reference/FAQ.rst

@@ -14,15 +14,15 @@ My tasks went DEAD. Why might this be?
 ========================================
 
 The most common reason for the first few tasks to go DEAD is an improper path in the ``land_analysis.yaml`` configuration file. 
-In particular, ``EXP_BASEDIR`` must be set to the directory above ``land-DA_workflow``. For example, if ``land-DA_workflow`` resides at ``Users/Jane.Doe/landda/land-DA_workflow``, then ``EXP_BASEDIR`` must be set to ``Users/Jane.Doe/landda``. After modifying ``land_analysis.yaml``, users will need to regenerate the workflow XML by running: 
+In particular, ``EXP_BASEDIR`` must be set to the directory above ``land-DA_workflow``. For example, if ``land-DA_workflow`` resides at ``Users/Jane.Doe/landda/land-DA_workflow``, then ``EXP_BASEDIR`` must be set to ``Users/Jane.Doe/landda``. After correcting ``land_analysis.yaml``, users will need to regenerate the workflow XML by running: 
 
 .. code-block:: console
 
    uw rocoto realize --input-file land_analysis.yaml --output-file land_analysis.xml
 
-Then, rewind the DEAD tasks as described :ref:`below <RestartTask>` using ``rocotorewind``, and use ``rocotorun``/``rocotostat`` to advance/check on the workflow. 
+Then, rewind the DEAD tasks as described :ref:`below <RestartTask>` using ``rocotorewind``, and use ``rocotorun``/``rocotostat`` to advance/check on the workflow (see :numref:`Section %s <run-w-rocoto>` for how to do this). 
 
-If the first few tasks run successfully, but future tasks go DEAD, users will need to check the experiment log files, located at ``$EXP_BASEDIR/ptmp/test/com/output/logs``. It may also be useful to check that the JEDI directory and other paths are correct in ``land_analysis.yaml``. 
+If the first few tasks run successfully, but future tasks go DEAD, users will need to check the experiment log files, located at ``$EXP_BASEDIR/ptmp/test/com/output/logs``. It may also be useful to check that the JEDI directory and other paths and values are correct in ``land_analysis.yaml``. 
 
 
 .. _RestartTask:
@@ -44,6 +44,7 @@ On platforms that utilize Rocoto workflow software (including Hera and Orion), i
    200001030000    post_anal  61746109    SUCCEEDED             0       1        4.0
    200001030000   plot_stats  61746110    SUCCEEDED             0       1       70.0
    200001030000     forecast  61746128         DEAD           256       1          -
+   200001030000   plot_stats         -            -             -       -          -
 
 
 This means that the DEAD task has not completed successfully, so the workflow has stopped. Once the issue has been identified and fixed (e.g., by referencing the log files in ``$LANDDAROOT/ptmp/test/com/output/logs``), users can rewind, or "undo," the failed task using the ``rocotorewind`` command: