From 3411bba9a4df6b7517ebfef4202253c2004977b2 Mon Sep 17 00:00:00 2001
From: Travis Byrne <travis.p.byrne@gmail.com>
Date: Tue, 29 Oct 2024 10:47:20 -0600
Subject: [PATCH] dependency typo fix

---
 docs/sections/user_guide/yaml/rocoto.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/sections/user_guide/yaml/rocoto.rst b/docs/sections/user_guide/yaml/rocoto.rst
index a655b7e11..4c4844d4c 100644
--- a/docs/sections/user_guide/yaml/rocoto.rst
+++ b/docs/sections/user_guide/yaml/rocoto.rst
@@ -131,7 +131,7 @@ Let's dissect the following task example:
      walltime: 00:01:00
      envars:
        person: siri
-     dependencies:
+     dependency:
 
 Each task is named by its UW YAML key. Blocks under ``tasks:`` prefixed with ``task_`` will be named with what follows the prefix. In the example above the task will be named ``hello`` and will appear in the XML like this:
 
@@ -157,7 +157,7 @@ The name of the task can be any string accepted by Rocoto as a task name (includ
      <value>siri</value>
    </envar>
 
-``dependencies:`` -- [Optional] Any number of dependencies accepted by Rocoto. This section is described in more detail below.
+``dependency:`` -- [Optional] Any number of dependencies accepted by Rocoto. This section is described in more detail below.
 
 The other keys not specifically mentioned here follow the same conventions as described in the :rocoto:`Rocoto<>` documentation.
 
@@ -180,7 +180,7 @@ Each of the dependencies that requires attributes (the ``key="value"`` parts ins
      ...
    task_goodbye:
      command: "goodbye"
-     dependencies:
+     dependency:
         taskdep:
           attrs:
             task: hello
@@ -209,7 +209,7 @@ Because UW YAML represents a hash table (a dictionary in Python), each key at th
    task_hello:
      command: "hello world"
      ...
-     dependencies:
+     dependency:
        and:
          datadep_foo:
            value: "foo.txt"