Fix some minor build error and clean up whitespace

1 files changed, 17 insertions, 29 deletions

diff --git a/en/boot-installer/arm.xml b/en/boot-installer/arm.xml
index d891ecbbb..6addc36de 100644
--- a/en/boot-installer/arm.xml
+++ b/en/boot-installer/arm.xml
@@ -5,24 +5,25 @@
 
 &boot-installer-intro-net.xml;
 
-  <sect3 arch="arm"><title>Booting from TFTP on Netwinder</title>
-
+   <sect3 arch="arm"><title>Booting from TFTP on Netwinder</title>
 <para>
 
 Netwinders have two network interfaces: A 10Mbps NE2000-compatible
-card (which is generally referred to as </literal>eth0</literal>) and
+card (which is generally referred to as <literal>eth0</literal>) and
 a 100Mbps Tulip card.  There may be problems loading the image via TFTP
 using the 100Mbps card so it is recommended that you use the 10Mbps
 interfaced (the one labeled with <literal>10 Base-T</literal>).
 
-</para><note><para>
+</para>
+<note><para>
 
 You need NeTTrom 2.2.1 or later to boot the installation system, and
 version 2.3.3 is recommended.  Unfortunately, firmware files are currently
 not available for download because of license issues.  If this situation
 changes, you may find new images at <ulink url="http//www.netwinder.org/"></ulink>.
 
-</para></note><para>
+</para></note>
+<para>
 
 When you boot your Netwinder you have to interrupt the boot process during the
 countdown.  This allows you to set a number of firmware settings needed in
@@ -47,8 +48,7 @@ where 24 is the number of set bits in the netmask, or a dynamic address:
 </screen></informalexample>
 
 You may also need to configure the <userinput>route1</userinput>
-settings if the TFTP
-server is not on the local subnet.
+settings if the TFTP server is not on the local subnet.
 
 Following these settings, you have to specify the TFTP server and the
 location of the image.  You can then store your settings to flash.
@@ -93,10 +93,9 @@ url="http://www.netwinder.org/howto/Firmware-HOWTO.html"></ulink> is
 available.
 
 </para>
-  </sect3>
-
-  <sect3 arch="arm"><title>Booting from TFTP on CATS</title>
+   </sect3>
 
+   <sect3 arch="arm"><title>Booting from TFTP on CATS</title>
 <para>
 
 On CATS machines, use <command>boot de0:</command> or similar at the
@@ -107,7 +106,6 @@ Cyclone prompt.
   </sect2>
 
 
-
   <sect2 arch="arm"><title>Booting from CD-ROM</title>
 
 &boot-installer-intro-cd.xml;
@@ -125,14 +123,14 @@ To boot a CD-ROM from the Cyclone console prompt, use the command
 
 &boot-installer-intro-firmware.xml;
 
-  <sect3 arch="arm" id="boot-firmware-nslu2"><title>Booting the NSLU2</title>
-
+   <sect3 arch="arm" id="boot-firmware-nslu2"><title>Booting the NSLU2</title>
 <para>
 
 There are three ways how to put the installer firmware into flash:
 
-  <sect4 arch="arm"><title>Using the NSLU2 web interface</title>
+</para>
 
+    <sect4 arch="arm"><title>Using the NSLU2 web interface</title>
 <para>
 
 Go to the administration section and choose the menu item
@@ -142,11 +140,9 @@ installer image you have previously downloaded.  Then press the
 and confirm again.  The system will then boot straight into the installer.
 
 </para>
+    </sect4>
 
-   </sect4>
-
-  <sect4 arch="arm"><title>Via the network using Linux/Unix</title>
-
+    <sect4 arch="arm"><title>Via the network using Linux/Unix</title>
 <para>
 
 You can use <command>upslug2</command> from any Linux or Unix machine to
@@ -208,11 +204,9 @@ connect your USB disk again now, otherwise the installer won't be able to
 find it.
 
 </para>
+    </sect4>
 
-   </sect4>
-
-  <sect4 arch="arm"><title>Via the network using Windows</title>
-
+    <sect4 arch="arm"><title>Via the network using Windows</title>
 <para>
 
 There is <ulink url =
@@ -220,12 +214,6 @@ There is <ulink url =
 tool</ulink> for Windows to upgrade the firmware via the network.
 
 </para>
-
-   </sect4>
-
-</para>
-
+    </sect4>
    </sect3>
-
   </sect2>
-