Fix link and update tags to fit to example

_episodes/21-1st-workflow.md

@@ -11,8 +11,7 @@ keypoints:
 - "Top level inputs and outputs of the workflow are described in the `inputs`
 and `outputs` fields respectively."
 - "The steps are specified under `steps`."
-- "Execution order is determined by the flow of inputs and outputs between
-steps."
+- "Execution order is determined by the connections between steps."
 ---
 This workflow extracts a java source file from a tar file and then
 compiles it.
@@ -100,7 +99,7 @@ steps:
     in:
       tarfile: inp
       extractfile: ex
-    outputs: [example_out]
+    out: [example_out]
 ~~~
 {: .source}
 
@@ -116,20 +115,20 @@ The first step, `untar` runs `tar-param.cwl` (described previously in
 [Parameter references][params]).  This tool has two input parameters, `tarfile`
 and `extractfile` and one output parameter `example_out`.
 
-The `inputs` section of the workflow step connects these two input parameters to
+The ``in`` section of the workflow step connects these two input parameters to
 the inputs of the workflow, `inp` and `ex` using `source`.  This means that when
 the workflow step is executed, the values assigned to `inp` and `ex` will be
 used for the parameters `tarfile` and `extractfile` in order to run the tool.
 
-The `outputs` section of the workflow step lists the output parameters that are
+The `out` section of the workflow step lists the output parameters that are
 expected from the tool.
 
 ~~~
   compile:
     run: arguments.cwl
     in:
       src: untar/example_out
-    outputs: [classfile]
+    out: [classfile]
 ~~~
 {: .source}
 
@@ -138,4 +137,4 @@ connecting the input parameter `src` to the output parameter of `untar` using
 `untar/example_out`.  The output of this step `classfile` is connected to the
 `outputs` section for the Workflow, described above.
 
-[params]: _episodes/06-params/
+[params]: 06-params/