Minor copyedits - 4.2.1 source verification

Minor rewording; a reduction of about 12 words.

1 files changed, 8 insertions, 8 deletions

diff --git a/paper.tex b/paper.tex
index f9712bf..8bc4205 100644
--- a/paper.tex
+++ b/paper.tex
@@ -415,16 +415,16 @@ However, such binary blobs are optional. They are not Maneage's primary storage/
 \subsubsection{Verifying and building necessary software from source}
 \label{sec:buildsoftware}
 
-To compile the necessary software from source Maneage currently needs the host to have a C and C++ compiler (available on any POSIX-compliant OS).
-They will be used by Maneage to build and install (in the build directory) all necessary software and their dependencies with fixed versions.
-The dependency tree goes all the way down to core operating system components like GNU Bash, GNU AWK, GNU Coreutils on all supported operating systems (including macOS, not just GNU/Linux).
+To compile the necessary software from source, Maneage currently needs the host to have a C and C++ compiler (available on any POSIX-compliant OS).
+These will be used by Maneage to build and install (in the build directory) all necessary software and their dependencies, all with fixed version identities.
+The dependency tree continues down to core operating system components including GNU Bash, GNU AWK, GNU Coreutils on all supported operating systems (including macOS, not just GNU/Linux).
 On GNU/Linux OSs, a fixed version of the GNU Binutils and GNU C Compiler (GCC) is also built from source, and a fixed version of the GNU C Library will soon be added to be fully independent of the host on such systems (task 15390).
-In effect, except for the Kernel, Maneage builds all other necessary components of the OS.
-For example, see this paper's Acknowledgments section for all the software that were built for this paper.
+Except for the Kernel, Maneage builds all other necessary components of the OS.
+For example, see the Acknowledgments section for all the software that were built for this paper.
 
-Before building the software, their source codes will be validated by their SHA-512 checksum (which is already stored in the project).
-Maneage includes a large collection of scientific software (and their dependencies) that are usually not necessary in all projects.
-Therefore, each project has to identify its high-level software in the \inlinecode{TARGETS.conf} file under \inlinecode{re\-produce\-/soft\-ware\-/config} directory, see Figure \ref{fig:files}.
+Before building the software, their source codes are validated by their SHA-512 checksum (stored in the project).
+Maneage includes a large collection of scientific software (and its dependencies), much of which is superfluous.
+Therefore, each project has to identify its high-level software in the \inlinecode{TARGETS.conf} file under \inlinecode{re\-produce\-/soft\-ware\-/config} directory (Fig.~\ref{fig:files}).
 
 \subsubsection{Software citation}
 \label{sec:softwarecitation}