diff --git a/en_US.ISO8859-1/articles/pxe/article.sgml b/en_US.ISO8859-1/articles/pxe/article.sgml
index 154cb16188..f469c46af9 100644
--- a/en_US.ISO8859-1/articles/pxe/article.sgml
+++ b/en_US.ISO8859-1/articles/pxe/article.sgml
@@ -10,27 +10,27 @@
 <article>
   <articleinfo>
     <title>FreeBSD Jumpstart Guide</title>
-    
+
     <authorgroup>
       <author>
         <firstname>Alfred</firstname>
         <surname>Perlstein</surname>
-        
+
         <affiliation>
           <address><email>alfred@FreeBSD.org</email></address>
         </affiliation>
       </author>
     </authorgroup>
-    
+
     <pubdate>$FreeBSD$</pubdate>
-    
+
     <abstract>
       <para>This article details the method used to allow machines to install
         FreeBSD using the Intel PXE method of booting a machine over a network.
         </para>
     </abstract>
   </articleinfo>
-  
+
   <sect1 id="introduction">
     <title>Introduction</title>
 
@@ -41,16 +41,16 @@
     </warning>
 
     <para>Terminology:</para>
-    
+
     <informaltable frame="none">
       <tgroup cols="2">
-      
+
         <tbody>
           <row>
             <entry>Server</entry>
             <entry>The machine offering netboot and install options.</entry>
           </row>
-          
+
           <row>
             <entry>Client</entry>
             <entry>The machine that will have FreeBSD installed on it.</entry>
@@ -62,8 +62,8 @@
     <para>Requires:
       Clients supporting the Intel PXE netboot option, an Ethernet connection.
       </para>
-    
-    <para>Please let me know if you come across anything you have problems with 
+
+    <para>Please let me know if you come across anything you have problems with
       or suggestions for additional documentation.</para>
 
     <para>If you would like someone to train/implement a specific netinstall system
@@ -79,11 +79,11 @@
 
     <procedure>
       <step>
-        <para>Install DHCP: Install <filename role="package">net/isc-dhcp3</filename> you can use this config file 
+        <para>Install DHCP: Install <filename role="package">net/isc-dhcp3</filename> you can use this config file
           <ulink url="dhcpd.conf">
           <filename>dhcpd.conf</filename></ulink>, stick it in /usr/local/etc/</para>
       </step>
-      
+
       <step>
         <para>Enable tftp:</para>
 	
@@ -91,17 +91,17 @@
           <step>
             <para>Make a directory <filename>/usr/tftpboot</filename></para>
           </step>
-            
+
           <step>
-            <para>Add this line to your 
+            <para>Add this line to your
               <filename>/etc/inetd.conf</filename>:</para>
-	    
+	
 <programlisting>tftp    dgram   udp     wait    nobody  /usr/libexec/tftpd    tftpd /usr/tftpboot</programlisting>
           </step>
         </procedure>
-          
+
       </step>
-        
+
       <step>
         <para>Enable NFS:</para>
 	
@@ -111,7 +111,7 @@
 
 	    <programlisting>nfs_server_enable="YES"</programlisting>
           </step>
-            
+
           <step>
             <para>Add this to <filename>/etc/exports</filename>:</para>
 
@@ -119,44 +119,44 @@
           </step>
         </procedure>
       </step>
-        
+
       <step>
-        <para>Reboot to enable the new services or start them 
+        <para>Reboot to enable the new services or start them
           manually.</para>
       </step>
     </procedure>
   </sect1>
-  
+
   <sect1 id="bootstrap-config">
     <title>Bootstrap Setup</title>
 
     <procedure>
       <step>
-        <para>Download bootfiles: Download the 
+        <para>Download bootfiles: Download the
           <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/i386/kern.flp">
-          kern.flp</ulink> and 
-          <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/i386/mfsroot.flp"> 
+          kern.flp</ulink> and
+          <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/i386/mfsroot.flp">
           mfsroot.flp</ulink> floppy images.</para>
       </step>
-      
+
       <step>
         <para>Setup tftp/pxe-boot directory:</para>
 	
         <procedure>
           <step>
             <para>Put pxeboot in the boot directory:</para>
-	    
+	
 	    <screen>&prompt.root; <userinput>rm -rf /usr/obj/*</userinput>
 &prompt.root; <userinput>cd /usr/src/sys/boot</userinput>
 &prompt.root; <userinput>make</userinput>
 &prompt.root; <userinput>cp /usr/src/sys/boot/i386/pxeldr/pxeboot /usr/tftpboot</userinput></screen>
           </step>
-          
+
           <step>
             <para>Using the vndevice mount the <filename>kern.flp</filename>
 	      file and copy its contents to
 	      <filename>/usr/tftpboot</filename>:</para>
-            
+
 	    <screen>&prompt.root; <userinput>vnconfig vn0 kern.flp</userinput>    # associate a vndevice with the file
 &prompt.root; <userinput>mount /dev/vn0 /mnt</userinput>      # mount it
 &prompt.root; <userinput>cp -R /mnt /usr/tftpboot</userinput> # copy the contents to /usr/tftpboot
@@ -165,20 +165,20 @@
           </step>
         </procedure>
       </step>
-      
+
       <step>
-        <para>Compile a custom kernel for the clients (particularly to avoid 
-          the device config screen at boot) and stick it in 
+        <para>Compile a custom kernel for the clients (particularly to avoid
+          the device config screen at boot) and stick it in
           <filename>/usr/tftpboot</filename>.</para>
       </step>
-      
+
       <step>
-        <para>Make a special <filename>loader.rc</filename> to and install it 
-          in <filename>/usr/tftpboot/boot/loader.rc</filename> so that it 
-          does not prompt for the second disk, here is 
+        <para>Make a special <filename>loader.rc</filename> to and install it
+          in <filename>/usr/tftpboot/boot/loader.rc</filename> so that it
+          does not prompt for the second disk, here is
           <ulink url="loader.rc">mine</ulink>.</para>
       </step>
-      
+
       <step>
         <para>Extract the installer and helper utilities from the mfsroot disk
           and uncompress them, put them in <filename>/usr/tftpboot</filename>
@@ -192,18 +192,18 @@
 &prompt.root; <userinput>cd /usr/tftpboot</userinput>                 # get into the pxeboot directory
 &prompt.root; <userinput>gunzip mfsroot.gz</userinput>                # uncompress the mfsroot</screen>
       </step>
-      
+
       <step>
         <para>Make your sysinstall script <filename>install.cfg</filename>, you
-          can use 
+          can use
           <ulink url="install.cfg">mine</ulink>
           as a template, but you must edit it.</para>
       </step>
-      
-      <step> 
-        <para>Copy the sysinstall script into the extracted and uncompressed 
+
+      <step>
+        <para>Copy the sysinstall script into the extracted and uncompressed
           mfsroot image:</para>
-          
+
 	<screen>&prompt.root; <userinput>cd /usr/tftpboot</userinput>
 &prompt.root; <userinput>vnconfig vn0 mfsroot</userinput>
 &prompt.root; <userinput>mount /dev/vn0 /mnt</userinput>
@@ -213,10 +213,10 @@
       </step>
     </procedure>
   </sect1>
-  
+
   <sect1 id="install-setup">
     <title>Install Setup</title>
-     
+
     <procedure>
       <step>
         <para>Put the install files in an NFS accessible location on the
@@ -233,49 +233,49 @@ LAYOUT.TXT      catpages        crypto          manpages
 README.TXT      cdrom.inf       dict            mfsroot.flp
 RELNOTES.TXT    compat1x        doc             packages</screen>
       </step>
-      
+
       <step>
-        <para>Copy the compressed packages into the packages/All directory 
+        <para>Copy the compressed packages into the packages/All directory
           under <filename>nfs</filename>.</para>
       </step>
-      
+
       <step>
         <para>Make sure you have an <filename>INDEX</filename> file prepared
 	  in the packages directory. You can make your own
 	  <filename>INDEX</filename> entries like so:</para>
 
 	<programlisting>alfred-1.0||/|Alfred install bootstrap||alfred@FreeBSD.org||||</programlisting>
-      
+
         <para>Then you can install custom packages, particularly your own
 	  custom post-install package.</para>
       </step>
     </procedure>
   </sect1>
-  
+
   <sect1 id="custom-postinst-package">
     <title>Custom Post-Install Package</title>
 
     <para>You can use the script <ulink url="pkgmaker.sh"><filename>pkgmaker.sh
-      </filename></ulink> to create a 
-      custom package for post install, the idea is to have it install and 
-      configure any special things you may need done. 
-      <filename>pkgmaker</filename> is run in the directory above the package 
-      you wish to create with the single argument of the package (ie mypkg) 
-      which will then create a mypkg.tgz for you to include in your sysinstall 
+      </filename></ulink> to create a
+      custom package for post install, the idea is to have it install and
+      configure any special things you may need done.
+      <filename>pkgmaker</filename> is run in the directory above the package
+      you wish to create with the single argument of the package (ie mypkg)
+      which will then create a mypkg.tgz for you to include in your sysinstall
       package.</para>
 
-    <para>Inside your custom package dir you will want a file called 
-      <filename>PLIST</filename> which contains all the files that you wish to 
+    <para>Inside your custom package dir you will want a file called
+      <filename>PLIST</filename> which contains all the files that you wish to
       install and be incorporated into your package.</para>
-      
+
     <para>You will also want files called
-      <ulink url="pre"><filename>pre</filename></ulink> and 
+      <ulink url="pre"><filename>pre</filename></ulink> and
       <ulink url="post"><filename>post</filename></ulink>
-      in the directory, these are shell scripts 
-      that you want to execute before and after your package is 
+      in the directory, these are shell scripts
+      that you want to execute before and after your package is
       installed.</para>
-      
-    <para>Since this package is in your <filename>install.cfg</filename> file 
+
+    <para>Since this package is in your <filename>install.cfg</filename> file
       it should be run and do the final configuration for you.</para>
   </sect1>
 </article>