01/04: doc: review by Ricardo. WIP: Squash me

[Jan Nieuwenhuizen]

janneke pushed a commit to branch wip-bootstrap
in repository guix.

commit 1b9192af11e5a5d50a3cbfbd7d0384254185197d
Author: Jan Nieuwenhuizen <address@hidden>
Date:   Tue Sep 18 05:47:16 2018 +0200

    doc: review by Ricardo.  WIP: Squash me
---
 doc/guix.texi | 31 ++++++++++++++++---------------
 1 file changed, 16 insertions(+), 15 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 5a2cc81..58f6647 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -23609,21 +23609,21 @@ a simple and auditable assembler.  Your help is 
welcome!
 @section The Reduced Binary Seed Bootstrap
 
 Guix---like other GNU/Linux distributions---is traditionally bootstrapped from
-from a set of bootstrap binaries: Bourne shell, command-line tools provided by
-GNU Coreutils, Awk, Findutils, `sed', and `grep' and Guile, GCC, Binutils, and
-the GNU C Library (@pxref{Bootstrapping}).  Usually, these bootstrap-binaries
-are ``taken for granted.''
+a set of bootstrap binaries: Bourne shell, command-line tools provided by GNU
+Coreutils, Awk, Findutils, `sed', and `grep' and Guile, GCC, Binutils, and the
+GNU C Library (@pxref{Bootstrapping}).  Usually, these bootstrap binaries are
+``taken for granted.''
 
-What does this mean, really?  By taking these binaries for granted, trusting
-Guix depends on the trusting these binaries to be correct and clean.  Therein
-lies a problem: the current combined size of these bootstrap-binaries is about
-250MB (@pxref{Bootstrappable Builds,,, mes, Mes Reference Manual}).  Auditing
-or even inspecting these is next to impossible.
+Taking these binaries for granted means that we consider them to be a correct
+and trustworthy `seed' for building the complete system.  Therein lies a
+problem: the current combined size of these bootstrap binaries is about 250MB
+(@pxref{Bootstrappable Builds,,, mes, Mes Reference Manual}).  Auditing or
+even inspecting these is next to impossible.
 
 For @code{i686-linux}, Guix now features a ``Reduced Binary Seed'' bootstrap
 @footnote{We would like to say: ``Full Source Bootstrap'' and while we are
-working towards that it would be a hyperbole to use that term for what we do
-now.}.
+working towards that goal it would be hyperbole to use that term for what we
+do now.}.
 
 The Reduced Binary Seed bootstrap removes the most critical tools---from a
 trust perspective---from the bootstrap binaries: GCC, Binutils and the GNU C
@@ -23632,7 +23632,7 @@ Library are replaced by: @code{mescc-tools-seed} (a 
tiny assembler and linker)
 and @code{tinycc-seed} (the Mes C Library, built for TinyCC).  Using these new
 binary seeds and a new set of
 @c
-package address@hidden@c
address@hidden@c
 mescc-tools-boot,
 nyacc-boot,
 mes-boot,
@@ -23652,10 +23652,11 @@ gcc-mesboot1-wrapper,
 glibc-headers-mesboot,
 glibc-mesboot,
 gcc-mesboot,
+and
 gcc-mesboot-wrapper.
 }
 @c
-the ``missing'' Binutils, and the GNU C Library are built, from source.  From
+the ``missing'' Binutils, and the GNU C Library are built from source.  From
 here on the more traditional bootstrap process resumes.  This approach has
 reduced the bootstrap binaries in size to about 130MB.  Work is ongoing to
 reduce this further.  If you are interested, join us on @code{#boottrappable}
@@ -23664,8 +23665,8 @@ on the Freenode IRC network.
 @c ./pre-inst-env guix graph --type=bag -e '(begin (use-modules (guix 
packages)) (%current-system "i686-linux") (@@ (gnu packages commencement) 
gcc-mesboot))' > doc/images/gcc-mesboot-bag-graph.dot
 @c dot -T png doc/images/gcc-mesboot-bag-graph.dot > 
doc/images/gcc-mesboot-bag-graph.png
 
-Below is the generated dependency graph to for @code{gcc-mesboot} that builds
-the rest of GuixSD.
+Below is the generated dependency graph for @code{gcc-mesboot}, the bootstrap
+compiler used to build the rest of GuixSD.
 
 @image{images/gcc-mesboot-bag-graph,6in,,Dependency graph of the gcc-mesboot}