diff options
| author | David Bryant <davidbryant@gvtc.com> | 2022-09-28 11:26:36 -0500 |
|---|---|---|
| committer | David Bryant <davidbryant@gvtc.com> | 2022-09-28 11:26:36 -0500 |
| commit | dd7f9df19f7614fefdb91d7c0ff824aa0fc553c9 (patch) | |
| tree | 839d78d76d579b8eac6da23a684e9e4dacb4fc8b /part3intro/introduction.xml | |
| parent | ef93b660064eed234161eb75619ebb36618d86ee (diff) | |
Cleaned up verbiage in unnumbered intro to part 3 (chapters 5 et seq).
Diffstat (limited to 'part3intro/introduction.xml')
| -rw-r--r-- | part3intro/introduction.xml | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/part3intro/introduction.xml b/part3intro/introduction.xml index 6d30ffe49..03ac66a87 100644 --- a/part3intro/introduction.xml +++ b/part3intro/introduction.xml @@ -10,25 +10,25 @@ <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> </sect1> |