Whitespace fix up, no content changes. Translators can ignore this.

1 files changed, 42 insertions, 41 deletions

diff --git a/release/doc/en_US.ISO8859-1/hardware/i386/proc-i386.sgml b/release/doc/en_US.ISO8859-1/hardware/i386/proc-i386.sgml
index fc48966..cc91c12 100644
--- a/release/doc/en_US.ISO8859-1/hardware/i386/proc-i386.sgml
+++ b/release/doc/en_US.ISO8859-1/hardware/i386/proc-i386.sgml
@@ -4,56 +4,57 @@
 <sect1 id="proc">
   <title>Supported Processors and Motherboards</title>
 
-  <para>&os;/i386 runs on a wide variety of
-  <quote>IBM PC compatible</quote> machines.  Due to the wide range of
-  hardware available for this architecture, it is impossible to
-  exhaustively list all combinations of equipment supported by &os;.
-  Nevertheless, some general guidelines are presented here.</para>
+  <para>&os;/i386 runs on a wide variety of <quote>IBM PC
+    compatible</quote> machines.  Due to the wide range of hardware
+    available for this architecture, it is impossible to exhaustively
+    list all combinations of equipment supported by &os;.
+    Nevertheless, some general guidelines are presented here.</para>
 
   <para>Almost all i386-compatible processors are supported.  All
-  Intel processors beginning with the 80386 are supported, including
-  the 80386, 80486, Pentium, Pentium Pro, Pentium II, Pentium III,
-  Pentium 4, and variants thereof, such as the Xeon and Celeron
-  processors.  (While technically supported, the use of the 80386SX is
-  specifically not recommended.)  All i386-compatible AMD processors
-  are also supported, including the Am486, Am5x86, K5, K6 (and variants),
-  Athlon (including Athlon-MP, Athlon-XP, Athlon-4, and Athlon Thunderbird), and Duron processors.  
-  The AMD &Eacute;lan SC520 embedded processor is supported.
-  The Transmeta Crusoe is recognized
-  and supported, as are i386-compatible processors from Cyrix and
-  NexGen.</para>
+    Intel processors beginning with the 80386 are supported, including
+    the 80386, 80486, Pentium, Pentium Pro, Pentium II, Pentium III,
+    Pentium 4, and variants thereof, such as the Xeon and Celeron
+    processors.  (While technically supported, the use of the 80386SX
+    is specifically not recommended.)  All i386-compatible AMD
+    processors are also supported, including the Am486, Am5x86, K5, K6
+    (and variants), Athlon (including Athlon-MP, Athlon-XP, Athlon-4,
+    and Athlon Thunderbird), and Duron processors.  The AMD
+    &Eacute;lan SC520 embedded processor is supported.  The Transmeta
+    Crusoe is recognized and supported, as are i386-compatible
+    processors from Cyrix and NexGen.</para>
 
   <para>There is a wide variety of motherboards available for this
-  architecture.  Motherboards using the ISA, VLB, EISA, AGP, and PCI
-  expansion busses are well-supported.  There is some limited support
-  for the MCA (<quote>MicroChannel</quote>) expansion bus used in the
-  IBM PS/2 line of PCs.</para>
+    architecture.  Motherboards using the ISA, VLB, EISA, AGP, and PCI
+    expansion busses are well-supported.  There is some limited
+    support for the MCA (<quote>MicroChannel</quote>) expansion bus
+    used in the IBM PS/2 line of PCs.</para>
 
   <para>Symmetric multi-processor (SMP) systems are generally
-  supported by &os;, although in some cases, BIOS or motherboard bugs
-  may generate some problems.  Perusal of the archives of the &a.smp;
-  may yield some clues.</para>
+    supported by &os;, although in some cases, BIOS or motherboard
+    bugs may generate some problems.  Perusal of the archives of the
+    &a.smp; may yield some clues.</para>
 
   <para>&os; will take advantage of HyperThreading (HTT) support on
     Intel CPUs that support this feature.  A kernel with the
-    <literal>options&nbsp;SMP</literal> feature enabled will automatically detect the
-    additional logical processors.  The default &os; scheduler treats
-    the logical processors the same as additional physical
-    processors; in other words, no attempt is made to optimize
-    scheduling decisions given the shared resources between logical
-    processors within the same CPU.  Because this naive scheduling can
-    result in suboptimal performance, the logical CPUs are halted by
-    default at startup.  They can be enabled
-    with the <varname>machdep.hlt_logical_cpus</varname> sysctl
-    variable.  It is also possible to halt any CPU in the idle
-    loop with the <varname>machdep.hlt_cpus</varname> sysctl
-    variable.  The &man.smp.4; manual page has more details.</para>
+    <literal>options&nbsp;SMP</literal> feature enabled will
+    automatically detect the additional logical processors.  The
+    default &os; scheduler treats the logical processors the same as
+    additional physical processors; in other words, no attempt is made
+    to optimize scheduling decisions given the shared resources
+    between logical processors within the same CPU.  Because this
+    naive scheduling can result in suboptimal performance, the logical
+    CPUs are halted by default at startup.  They can be enabled with
+    the <varname>machdep.hlt_logical_cpus</varname> sysctl variable.
+    It is also possible to halt any CPU in the idle loop with the
+    <varname>machdep.hlt_cpus</varname> sysctl variable.  The
+    &man.smp.4; manual page has more details.</para>
 
   <para>&os; will generally run on i386-based laptops, albeit with
-  varying levels of support for certain hardware features such as
-  sound, graphics, power management, and PCCARD expansion slots.
-  These features tend to vary in idiosyncratic ways between machines,
-  and frequently require special-case support in &os; to work around
-  hardware bugs or other oddities.  When in doubt, a search of the
-  archives of the &a.mobile; may be useful.</para>
+    varying levels of support for certain hardware features such as
+    sound, graphics, power management, and PCCARD expansion slots.
+    These features tend to vary in idiosyncratic ways between
+    machines, and frequently require special-case support in &os; to
+    work around hardware bugs or other oddities.  When in doubt, a
+    search of the archives of the &a.mobile; may be useful.</para>
+
 </sect1>