From a5417f6b100363eeed6ad3300a873ca066bcc506 Mon Sep 17 00:00:00 2001
From: Mohammad Akhlaghi <mohammad@akhlaghi.org>
Date: Tue, 9 Jun 2020 18:51:03 +0100
Subject: Two minor typos corrected

Two words were corrected in the text that made the sentences grammatically
wrong (they were actually typos! historically they were correct, but we
later changed the later part of the sentence without fixing the first
part).
---
 paper.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'paper.tex')

diff --git a/paper.tex b/paper.tex
index ccca868..e788b06 100644
--- a/paper.tex
+++ b/paper.tex
@@ -335,7 +335,7 @@ Project authors add their modular subMakefiles in between.
 Except for \inlinecode{paper.mk} (which builds the ultimate target: \inlinecode{paper.pdf}), all subMakefiles build a macro file with the same base-name (the \inlinecode{.tex} file in each subMakefile of Figure \ref{fig:datalineage}).
 Other built files (intermediate analysis steps) cascade down in the lineage to one of these macro files, possibly through other files.
 
-Just before reaching the ultimate target (\inlinecode{paper.pdf}), the lineage reaches a bottleneck in \inlinecode{verify.mk}, to satisfy the verification criteria (this step was yet not available in \cite{akhlaghi19, infante20}).
+Just before reaching the ultimate target (\inlinecode{paper.pdf}), the lineage reaches a bottleneck in \inlinecode{verify.mk}, to satisfy the verification criteria (this step was not yet available in \cite{akhlaghi19, infante20}).
 All project deliverables (macro files, plot or table data and other datasets) are verified at this stage, with their checksums, to automatically ensure exact reproducibility.
 Where exact reproducibility is not possible, values can be verified by any statistical means, specified by the project authors.
 
@@ -366,7 +366,7 @@ This fast and cheap testing encourages experimentation (without necessarily know
 
 Finally, to satisfy the recorded history criterion, version control (currently implemented in Git) is another component of Maneage (see Figure \ref{fig:branching}).
 Maneage is a Git branch that contains the shared components (infrastructure) of all projects (e.g., software tarball URLs, build recipes, common subMakefiles and interface script).
-Derived project start by branching off, and customizing it (e.g., adding a title, data links, narrative, and subMakefiles for its particular analysis, see Listing \ref{code:branching}, there is customization checklist in \inlinecode{README-hacking.md}).
+Derived projects start by branching off, and customizing it (e.g., adding a title, data links, narrative, and subMakefiles for its particular analysis, see Listing \ref{code:branching}, there is customization checklist in \inlinecode{README-hacking.md}).
 
 \begin{lstlisting}[
     label=code:branching,
-- 
cgit v1.2.1

