Minor edits in the text

While looking over the PDF, a few small edits were made to be more clear.

1 files changed, 4 insertions, 4 deletions

diff --git a/paper.tex b/paper.tex
index aeb4434..db93e32 100644
--- a/paper.tex
+++ b/paper.tex
@@ -144,13 +144,13 @@ Section \ref{sec:maneage} describes the internal structure of Maneage and Sectio
 \section{Definitions}
 \label{sec:definitions}
 
-The concepts and terminologies of reproducibility and project/workflow management and design are commonly used differently by different research communities or different solution providers.
-As a consequence, before starting with the technical details it is important to clearly define the specific terms used here.
+The concepts and terminologies of reproducibility and project/workflow management and design are used differently by different research communities or different solution providers.
+It is therefore important to clarify some specific terms used in this paper.
 
 \begin{enumerate}[label={\bf D\arabic*}]
 \item \label{definition:input}\textbf{Input:}
   A project's input is any file that may be usable in other projects.
-  The inputs of a project include data or software source code \citep[see][on the fundamental similarity of data and source code.]{hinsen16}.
+  The inputs of a project include data or software source code \citep[see][on the fundamental similarity of data and source code]{hinsen16}.
   Inputs may have initially been created/written (e.g., software source code) or collected (e.g., data) for one specific project. However, they can, and most often will, be used in later projects as well.
 
 \item \label{definition:output}\textbf{Output:}
@@ -224,7 +224,7 @@ To help in the comparison, the founding principles of Maneage are listed below.
   (P1.5) can be run locally (without internet connection),
   (P1.6) contains the full project's analysis, visualization \emph{and} narrative, from access to raw inputs to producing final published format (e.g., PDF or HTML),
   (P1.7) requires no manual/human interaction and can run automatically \citep[according to][``\emph{a clerk can do it}'']{claerbout1992}.
-  A consequence of P1.1 is that the project itself must be stored in plain-text, and not need any specialized software to open, parse or execute.
+  A consequence of P1.1 is that the project itself must be stored in plain-text: not needing any specialized software to open, parse or execute.
 
   \emph{Comparison with existing:} with many dependencies beyond POSIX, except for IPOL, none of the tools above are complete.
   For example, most recent solutions need Python (for the workflow, not the analysis), or rely on Jupyter notebooks.