From a3d6cf7de41495fbf7c8dd5b34377a8d3136d7eb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Herv=C3=A9=20M=C3=A9nager?= Date: Fri, 22 Dec 2017 21:37:07 +0100 Subject: [PATCH] suggestion for correction in introduction text --- _episodes/01-introduction.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_episodes/01-introduction.md b/_episodes/01-introduction.md index 35f9c2ae..5306031b 100644 --- a/_episodes/01-introduction.md +++ b/_episodes/01-introduction.md @@ -24,7 +24,7 @@ execution based on dependencies between tasks. However unlike "make", CWL tasks are isolated and you must be explicit about your inputs and outputs. The benefit of explicitness and isolation are flexibility, portability, and scalability: tools and workflows described with CWL can transparently leverage -technologies such as Docker, be used with CWL implementations from different -vendors, and is well suited for describing large-scale workflows in cluster, +technologies such as Docker and be used with CWL implementations from different +vendors. CWL is well suited for describing large-scale workflows in cluster, cloud and high performance computing environments where tasks are scheduled in parallel across many nodes.