aboutsummaryrefslogtreecommitdiffstats
path: root/appendixa
diff options
context:
space:
mode:
authorGerard Beekmans <gerard@linuxfromscratch.org>2002-05-29 23:15:53 +0000
committerGerard Beekmans <gerard@linuxfromscratch.org>2002-05-29 23:15:53 +0000
commit4ceb3a1a3e03ced7b9512a5fb626827f8a79c7fa (patch)
treef11e7d8abe0b4de4b35e1d4cb8408bd0b55a942d /appendixa
parent159c2d2da34540e99d4aa985dc9e2c7e7a76ec4d (diff)
applied Alex's listed-items.patch
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1942 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'appendixa')
-rw-r--r--appendixa/glibc-desc.xml8
-rw-r--r--appendixa/introduction.xml32
2 files changed, 19 insertions, 21 deletions
diff --git a/appendixa/glibc-desc.xml b/appendixa/glibc-desc.xml
index 62b6efc1e..f3ee7c291 100644
--- a/appendixa/glibc-desc.xml
+++ b/appendixa/glibc-desc.xml
@@ -185,10 +185,10 @@ libnss_hesiod, libnss_nis, libnss_nisplus</title>
offered to access the databases in separate modules. This has some
advantages:</para>
<itemizedlist>
-<listitem><para>Contributors can add new services without adding them to
-GNU C Library.</para></listitem>
-<listitem><para>The modules can be updated separately.</para></listitem>
-<listitem><para>The C library image is smaller.</para></listitem>
+<listitem><para>contributors can add new services without adding them to
+GNU C library,</para></listitem>
+<listitem><para>the modules can be updated separately,</para></listitem>
+<listitem><para>the C library image is smaller.</para></listitem>
</itemizedlist></sect4>
<sect4><title>libpcprofile</title>
diff --git a/appendixa/introduction.xml b/appendixa/introduction.xml
index 504699147..c5c231042 100644
--- a/appendixa/introduction.xml
+++ b/appendixa/introduction.xml
@@ -2,32 +2,31 @@
<title>Introduction</title>
<?dbhtml filename="introduction.html" dir="appendixa"?>
-<para>This appendix describes the following aspects of every package
-that is installed in this book:</para>
+<para>In this appendix the following aspects of every package
+installed in this book are described:</para>
<itemizedlist>
-<listitem><para>The official download location for the
-package.</para></listitem>
+<listitem><para>the official download location for the
+package,</para></listitem>
-<listitem><para>What the package contains.</para></listitem>
+<listitem><para>what the package contains,</para></listitem>
-<listitem><para>What each program from a package does.</para></listitem>
+<listitem><para>what each program from the package does,</para></listitem>
-<listitem><para>What each package needs to compile.</para></listitem>
+<listitem><para>what the package needs to be compiled.</para></listitem>
</itemizedlist>
<para>Most information about these packages (especially the descriptions of
-them) come from the man pages from those packages. We are not going to print
-the entire man page, just the core elements to make it possible to
-understand what a program does. To get knowledge of all details on a program,
-we suggest you start by reading the complete man page in addition to
-this appendix.</para>
+them) come from the man pages of those packages. We do not include
+the entire man page, but just some key elements to make it possible to
+understand what a program does. To get information on all details of a program,
+please refer to its man page or info page.</para>
<para>Certain packages are documented in more depth
than others, because we just happen to know more about certain
-packages than I know about others. If anything should be added to the
+packages than about others. If you think anything should be added to the
following descriptions, please don't hesitate to email the mailing
lists. We intend that the list should contain an in-depth description
of every package installed, but we can't do it without help.</para>
@@ -45,12 +44,11 @@ what programs are needed to use that packages programs. Just the ones
needed to compile it.</para>
<para>The dependency list can be, from time to time, outdated in regards
-to the current used package version. Checking dependencies takes quite a
+to the currently used package version. Checking dependencies takes quite a
bit of work, so they may lag behind a bit on the package update. But
often with minor package updates, the installation dependencies hardly
-change, so they'll be current in most cases. If we upgrade to a major
-new release, we'll make sure the dependencies are checked too at the
-same time.</para>
+change, so they'll be current in most cases. When we upgrade to a major
+new release, we'll make sure the dependencies are checked too.</para>
</sect1>