From 83802addde438eae2db409b89f570606e4e1ace6 Mon Sep 17 00:00:00 2001
From: Arun Isaac
Date: Mon, 18 Oct 2021 00:55:53 +0530
Subject: doc: Say that inputs, not workflow inputs, come into pipe and tee.

Workflow inputs are now global. It is misleading to say that they come
into the first expression, namely pipe and tee, in these examples.

* doc/ccwl.skb (Tutorial)[Workflow with multiple steps]: Say that
inputs, not workflow inputs, come into pipe and tee.
---
 doc/ccwl.skb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'doc')

diff --git a/doc/ccwl.skb b/doc/ccwl.skb
index c948b53..57fa225 100644
--- a/doc/ccwl.skb
+++ b/doc/ccwl.skb
@@ -202,7 +202,7 @@ it.])
         (p [Notice the
 ,(source-ref "ccwl/ccwl.scm" "\\(\\(pipe" (code "pipe")) form in the
 body of the workflow. The ,(code "pipe") form specifies a list of
-steps to be executed sequentially. The workflow inputs coming into
+steps to be executed sequentially. The inputs coming into
 ,(code "pipe") are passed into the first step. Thereafter, the outputs
 of each step are passed as inputs into the next. Note that this has
 nothing to do with the Unix pipe. The inputs/outputs passed between
@@ -231,7 +231,7 @@ three different checksums of a given input file.])
         (p [Notice the
 ,(source-ref "ccwl/ccwl.scm" "\\(\\(tee" (code "tee")) form in the
 body of the workflow. The ,(code "tee") form specifies a list of steps
-that are independent of each other. The workflow inputs coming into
+that are independent of each other. The inputs coming into
 ,(code "tee") are passed into every step contained in the body of the
 ,(code "tee"). The outputs of each step are collected together and
 unioned as the output of the ,(code "tee").])
-- 
cgit v1.2.3