aboutsummaryrefslogtreecommitdiffstats
path: root/chapter02/aboutsbus.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter02/aboutsbus.xml')
-rw-r--r--chapter02/aboutsbus.xml7
1 files changed, 3 insertions, 4 deletions
diff --git a/chapter02/aboutsbus.xml b/chapter02/aboutsbus.xml
index f43859584..c6ad47071 100644
--- a/chapter02/aboutsbus.xml
+++ b/chapter02/aboutsbus.xml
@@ -6,7 +6,7 @@
of identifying how long a package takes to compile. Why don't we use normal
times like anybody else?</para>
-<para>The biggest problem is that times cannot be acurate, not even a
+<para>The biggest problem is that times cannot be accurate, not even a
little bit. So many people install LFS on so many different systems, the
times it takes to compile something varies too much. One package may take
20 minutes on one system, but that same package may take 3 days on another
@@ -22,9 +22,8 @@ fairly consistent among a lot of different systems. So multiply 9.5 by the
number of seconds it takes for Bash to install (the SBU value) and you get
a close approximation of how long GCC will take on your system.</para>
-<para>Note: SBUs don't work on SMP machines. We've seen that SBUs don't
-work well on SMP based machines. So all bets are off if you're lucky enough
-to have an SMP setup.</para>
+<para>Note: We've seen that SBUs don't work well on SMP based machines. So
+all bets are off if you're lucky enough to have an SMP setup.</para>
</sect1>