principles - P2 modularity

Minor wording improvements; reduction by 10 words.

1 files changed, 6 insertions, 6 deletions

diff --git a/paper.tex b/paper.tex
index aeb7404..d43aa8c 100644
--- a/paper.tex
+++ b/paper.tex
@@ -236,15 +236,15 @@ A detailed list of principles shows how Maneage is unique compared to these othe
   A plain-text project, besides being extremely low volume ($\sim100$ kilobytes), is human-readable and parsable by any machine, even if it can't be executed.
 
 \item \label{principle:modularity}\textbf{Modularity:}
-A project should be compartmentalized or partitioned into independent modules or components with well-defined inputs/outputs having no side-effects.
-In a modular project, communication between the independent modules is explicit, providing optimizations on multiple levels:
-1) Execution: independent modules can run in parallel, or modules that do not need to be run (because their dependencies have not changed) will not be re-done.
+A project should be compartmentalized into independent modules with well-defined inputs/outputs having no side effects.
+Communication between the independent modules should be explicit, providing several optimizations:
+1) Execution: independent modules can run in parallel. Modules that do not need to be run (because their dependencies have not changed) will not be re-run.
 2) Data provenance extraction (recording any dataset's origins).
-3) Citation: allowing others to credit specific parts of a project.
+3) Citation: others can credit specific parts of a project.
 4) Usage in other projects.
 
-\emph{Comparison with existing:} Visual workflow tools like Apache Taverna, GenePattern, Kepler or VisTrails do encourage this, but the more recent tools leave such design choices to the experience of project authors.
-However, designing a modular project needs to be encouraged and facilitated, otherwise scientists (who are not usually trained in data management) will not design their projects to be modular, leading to great inefficiencies in terms of project cost and/or scientific accuracy.
+\emph{Comparison with existing:} Visual workflow tools like Apache Taverna, GenePattern, Kepler or VisTrails encourage this, but the more recent tools leave this design choice as the responsibility of project authors.
+However, designing a modular project needs to be encouraged and facilitated. Otherwise, scientists, who are not usually trained in data management, will rarely design their projects to be modular, leading to great inefficiencies in terms of project cost and/or scientific accuracy.
 
 \item \label{principle:complexity}\textbf{Minimal complexity:}
   This principle is essentially Ockham's razor: ``\emph{Never posit pluralities without necessity}'' \citep{schaffer15}, but extrapolated to project management: