Changeset dd7f9df for part3intro/introduction.xml

Timestamp:

09/28/2022 04:26:36 PM (19 months ago)

Author:

David Bryant <davidbryant@…>

Branches:

11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

5620622

Parents:

ef93b66

Message:

Cleaned up verbiage in unnumbered intro to part 3 (chapters 5 et seq).

File:

• part3intro/introduction.xml (modified) (1 diff)

part3intro/introduction.xml

@@ -11 +11 @@
   <title>Introduction</title>
 
-  <para>This part is divided into three stages: first building a cross
-  compiler and its associated libraries; second, use this cross toolchain
+  <para>This part is divided into three stages: first, building a cross
+  compiler and its associated libraries; second, using this cross toolchain
   to build several utilities in a way that isolates them from the host
-  distribution; third, enter the chroot environment, which further improves
-  host isolation, and build the remaining tools needed to build the final
+  distribution; and third, entering the chroot environment (which further improves
+  host isolation) and constructing the remaining tools needed to build the final
   system.</para>
 
-  <important><para>With this part begins the real work of building a new
-  system. It requires much care in ensuring that the instructions are
-  followed exactly as the book shows them. You should try to understand
-  what they do, and whatever your eagerness to finish your build, you should
-  refrain from blindly type them as shown, but rather read documentation when
+  <important><para>This is where the real work of building a new system
+  begins. Be very careful to follow the instructions exactly as the book
+  shows them. You should try to understand what each command does,
+  and no matter how eager you are to finish your build, you should
+  refrain from blindly typing the commands as shown. Read the documentation when
   there is something you do not understand. Also, keep track of your typing
-  and of the output of commands, by sending them to a file, using the
-  <command>tee</command> utility. This allows for better diagnosing
-  if something gets wrong.</para></important>
+  and of the output of commands, by using the <command>tee</command> utility
+  to send the terminal output to a file. This makes debugging easier
+  if something goes wrong.</para></important>
 
-  <para>The next section gives a technical introduction to the build process,
-  while the following one contains <emphasis role="strong">very
+  <para>The next section is a technical introduction to the build process,
+  while the following one presents <emphasis role="strong">very
   important</emphasis> general instructions.</para>