aboutsummaryrefslogtreecommitdiffstats
path: root/chapter02/abouttestsuites.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter02/abouttestsuites.xml')
-rw-r--r--chapter02/abouttestsuites.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter02/abouttestsuites.xml b/chapter02/abouttestsuites.xml
index 4652ff0d5..0d74fbf6a 100644
--- a/chapter02/abouttestsuites.xml
+++ b/chapter02/abouttestsuites.xml
@@ -4,14 +4,14 @@
<para>Most packages provide a test suite. Running the test suite for a newly
built package is generally a good idea as it can provide a nice sanity check
-that everything compiled correctly. A test suite that passes it's set of
+that everything compiled correctly. A test suite that passes its set of
checks usually proves that the package is functioning mostly as the developer
intended. It does not, however, guarantee that the package is totally bug
free.</para>
<para>Some test suites are more important than others. For example, the test
-suites for the core toolchain packages, GCC and Binutils, and the C library,
-Glibc, are of the utmost importance due to their central positioning in a
+suites for the core toolchain packages -- GCC, Binutils, and Glibc (the C
+library) -- are of the utmost importance due to their central positioning in a
properly functioning system. But be warned, the test suites for GCC and Glibc
can take a very long period of time to complete, especially on slower
hardware.</para>