From bf506794dc293c8f4e7e8aac6dcd31e95426ecb2 Mon Sep 17 00:00:00 2001
From: Arun Isaac
Date: Mon, 21 Jun 2021 15:58:37 +0530
Subject: doc: Fill paragraph.

* doc/ccwl.skb (Tutorial)[Workflow with multiple steps]: Fill
paragraph.
---
 doc/ccwl.skb | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

(limited to 'doc/ccwl.skb')

diff --git a/doc/ccwl.skb b/doc/ccwl.skb
index cc1f3bf..2ffd8f6 100644
--- a/doc/ccwl.skb
+++ b/doc/ccwl.skb
@@ -161,14 +161,14 @@ it.])
         (scheme-source "doc/decompress-compile-run.scm")
 
         (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 ,(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 steps are
-general CWL inputs/outputs. They need not be the standard stdin and
-stdout streams.])
+,(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
+,(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
+steps are general CWL inputs/outputs. They need not be the standard
+stdin and stdout streams.])
 
         ;; TODO: Add workflow graph
 
-- 
cgit v1.2.3