A horde of whitespace fixes.

12 files changed, 88 insertions, 88 deletions

diff --git a/www/bu_303b.html b/www/bu_303b.html
index 7cd475ef..84c874b9 100644
--- a/www/bu_303b.html
+++ b/www/bu_303b.html
@@ -50,7 +50,7 @@ BU-303 GPS Receiver
 
 <div id="Content">
 
-<p>(Found on a Korean electronics dealer's website, edited to fix the 
+<p>(Found on a Korean electronics dealer's website, edited to fix the
 English and remove promotional crap.)</p>
 
 <div style='align:center'>
@@ -68,7 +68,7 @@ English and remove promotional crap.)</p>
           1.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:top;width:94%;background-color:#d7f2ff">"SiRF Star 
+      <td class="T-1" style="vertical-align:top;width:94%;background-color:#d7f2ff">"SiRF Star
         II/LP" high performance and low power consumption chipset.</td>
     </tr>
     <tr>
@@ -77,7 +77,7 @@ English and remove promotional crap.)</p>
           2.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%">All-in-view 12-channel parallel 
+      <td class="T-1" style="vertical-align:width:94%">All-in-view 12-channel parallel
         processing.</td>
     </tr>
     <tr>
@@ -86,7 +86,7 @@ English and remove promotional crap.)</p>
           3.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">Built-in active 
+      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">Built-in active
         antenna.</td>
     </tr>
     <tr>
@@ -95,7 +95,7 @@ English and remove promotional crap.)</p>
           4.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%">High sensitivity to satellite 
+      <td class="T-1" style="vertical-align:width:94%">High sensitivity to satellite
         signal.</td>
     </tr>
     <tr>
@@ -104,7 +104,7 @@ English and remove promotional crap.)</p>
           5.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">Cold start 
+      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">Cold start
         under 45 seconds, average.</td>
     </tr>
     <tr>
@@ -113,7 +113,7 @@ English and remove promotional crap.)</p>
           6.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%">Superior urban canyon 
+      <td class="T-1" style="vertical-align:width:94%">Superior urban canyon
         performance.</td>
     </tr>
     <tr>
@@ -122,7 +122,7 @@ English and remove promotional crap.)</p>
           7.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">FoliageLock for 
+      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">FoliageLock for
         weak signal tracking.</td>
     </tr>
     <tr>
@@ -131,7 +131,7 @@ English and remove promotional crap.)</p>
           8.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%">Build-in SuperCap to reserve 
+      <td class="T-1" style="vertical-align:width:94%">Build-in SuperCap to reserve
         system data for rapid satellite acquisition.</td>
     </tr>
     <tr>
@@ -140,7 +140,7 @@ English and remove promotional crap.)</p>
           9.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">Supported NMEA 
+      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">Supported NMEA
         0183 command: GGA, GSA, GSV, RMC, GLL, VTG</td>
     </tr>
     <tr>
@@ -149,7 +149,7 @@ English and remove promotional crap.)</p>
           10.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%">Magnetic base for 
+      <td class="T-1" style="vertical-align:width:94%">Magnetic base for
         mounting on a car.</td>
     </tr>
     <tr>
@@ -158,7 +158,7 @@ English and remove promotional crap.)</p>
           11.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">LED indicator 
+      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">LED indicator
         for GPS fix or not fix.<br>
         LED OFF: Receiver is off<br>
         LED ON : No fix, searching<br>
@@ -178,7 +178,7 @@ English and remove promotional crap.)</p>
           13.
         </div>
       </td>
-      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">USB interface 
+      <td class="T-1" style="vertical-align:width:94%;background-color:#d7f2ff">USB interface
         connection port</td>
     </tr>
   </tbody>
@@ -197,7 +197,7 @@ English and remove promotional crap.)</p>
     </tr>
     <tr>
       <td class="ffg" style="vertical-align:width:33%">Output Messages</td>
-      <td class="T-1" style="vertical-align:width:67%">NMEA0183 V2.2 protocol, and 
+      <td class="T-1" style="vertical-align:width:67%">NMEA0183 V2.2 protocol, and
         supports commands:<br>
         GGA, GSA, GSV, RMC, GLL, VTG</td>
     </tr>
@@ -219,7 +219,7 @@ English and remove promotional crap.)</p>
     </tr>
     <tr>
       <td class="ffg" style='vertical-align:width:33%;background-color:#d7f2ff'>Altitude Limit</td>
-      <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>18,000m(60,000 
+      <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>18,000m(60,000
         feet)Max.</td>
     </tr>
     <tr>
@@ -228,7 +228,7 @@ English and remove promotional crap.)</p>
     </tr>
     <tr>
       <td class="ffg" style='vertical-align:width:33%;background-color:#d7f2ff'>Velocity Limit</td>
-      <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>515 
+      <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>515
         meters/sec(1000knots)Max</td>
     </tr>
     <tr>
@@ -236,9 +236,9 @@ English and remove promotional crap.)</p>
       <td class="T-1" style="vertical-align:width:67%">20 m/sec**3</td>
     </tr>
     <tr>
-      <td class="ffg" style='vertical-align:width:33%;background-color:#d7f2ff'>Horizontal 
+      <td class="ffg" style='vertical-align:width:33%;background-color:#d7f2ff'>Horizontal
         Accuracy</td>
-      <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>15m 2d RMS 
+      <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>15m 2d RMS
         without SA<br>
         10m 2d RMS WAAS enabled<br>
         1-5m DGPS corrected .</td>
@@ -248,7 +248,7 @@ English and remove promotional crap.)</p>
       <td class="T-1" style="vertical-align:width:67%">40m 95%</td>
     </tr>
     <tr>
-      <td class="ffg" style='vertical-align:width:33%;background-color:#d7f2ff'>Velocity 
+      <td class="ffg" style='vertical-align:width:33%;background-color:#d7f2ff'>Velocity
         Accuracy</td>
       <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>0.1m/sec 95%</td>
     </tr>
@@ -265,7 +265,7 @@ English and remove promotional crap.)</p>
       <td class="T-1" style="vertical-align:width:67%">90 mA(include Antenna)</td>
     </tr>
     <tr>
-      <td class="ffg" style='vertical-align:width:33%;background-color:#d7f2ff'>Storage 
+      <td class="ffg" style='vertical-align:width:33%;background-color:#d7f2ff'>Storage
         Temperature</td>
       <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>-40C ~ 85C</td>
     </tr>
@@ -275,7 +275,7 @@ English and remove promotional crap.)</p>
     </tr>
     <tr>
       <td class="ffg" style='vertical-align:width:33%;background-color:#d7f2ff'>Humidity</td>
-      <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>Up to 95% non - 
+      <td class="T-1" style='vertical-align:width:33%;background-color:#d7f2ff'>Up to 95% non -
         Condensing</td>
     </tr>
   </tbody>
@@ -283,7 +283,7 @@ English and remove promotional crap.)</p>
 
 <div>&nbsp;</div>
 
-<p>And this is from the spec sheet for the RoyalTek Sapphire, another 
+<p>And this is from the spec sheet for the RoyalTek Sapphire, another
 SiRF-II-based GPS:</p>
 
 <pre>
@@ -305,20 +305,20 @@ solder on its leads.</p>
 to fall on the floor) could stress and eventually break the solder bond.
 If you start hearing a rattling noise from inside the BU-303 case,
 this has probably happened.  The least-bad effect this can have is
-that the unit will start taking longer to acquire a first fix, because 
+that the unit will start taking longer to acquire a first fix, because
 every time you plug it in will effectively be a cold start.  If the loose
 SuperCap's contacts land in the right places, they can destroy or
 subtly derange the unit.  At worst, this actually presented an
 explosion hazard.</p>
 
-<p>After the battery has been loose for a while, the USB transciever 
+<p>After the battery has been loose for a while, the USB transciever
 in the device may go catatonic.  You will know this has happened if
 the indicator LED still lights when the BU-303 is plugged in but the
 USB system on your laptop no longer sees the device.  Check this by
 running lsusb(1); you should see a line that looks like this:</p>
 
 <pre>
-Bus XXX: Device YYY: ID 067b:2302 Prolific Technology Inc. PL2303 Serial Port 
+Bus XXX: Device YYY: ID 067b:2302 Prolific Technology Inc. PL2303 Serial Port
 </pre>
 
 <p>If you don't see this line, do not despair &mdash; it is actually
@@ -326,7 +326,7 @@ possible to repair the unit.  Here is how:</p>
 
 <ol>
 <li>Collect the right tools.  You will need one (1) Philips-blade
-jewelers' screwdriver, one (1) tube of epoxy superglue, and one (1) 
+jewelers' screwdriver, one (1) tube of epoxy superglue, and one (1)
 clean well-lighted suface on which tiny parts won't disappear.  If
 your fingers are clumsy, get a pair of tweezers or a really small pair
 of needlenose pliers.</li>
@@ -353,7 +353,7 @@ parallel to the board-edge towards the middle of one side, that match
 two metal fingers on the loose battery.</li>
 
 <li>Place the battery within the white circle so that its figers sit on
-the pads.  There will be only one way it fits.  Once you know how to 
+the pads.  There will be only one way it fits.  Once you know how to
 put it in that position with your fingers or a pair of tweezers, get
 out a tube of epoxy superglue.  Put some on the metal rectangle on the
 bottom face of the battery and put the battery into position.  Hold it
diff --git a/www/excellence.html b/www/excellence.html
index 5130ce84..ca532a9b 100644
--- a/www/excellence.html
+++ b/www/excellence.html
@@ -67,8 +67,8 @@ GPSD and Code Excellence
 
 <div id="Content">
 
-<p>There's a wonderfully tongue-in-cheek project called the 
-<a href="http://codeoffsets.com/">The Alliance for Code Excellence</a> 
+<p>There's a wonderfully tongue-in-cheek project called the
+<a href="http://codeoffsets.com/">The Alliance for Code Excellence</a>
 ("Building a better tomorrow &mdash; one line of code at a time.") that
 sells Bad Code Offset certificates. They fund open source projects to
 produce good code that will, in theory, offset all the bad code out
diff --git a/www/for-vendors.html b/www/for-vendors.html
index 9f185fae..705eb5ea 100644
--- a/www/for-vendors.html
+++ b/www/for-vendors.html
@@ -93,8 +93,8 @@ GPS and NMEA-based technologies. That expertise can be yours for
 free.</p>
 
 <p>We maintain a <a href="hardware.html">Hardware</a> page that
-is the open-source community reference for GPS shoppers.  A good 
-rating on that page means additional sales for your product.  We 
+is the open-source community reference for GPS shoppers.  A good
+rating on that page means additional sales for your product.  We
 also maintain a <a href='hall-of-shame.html'>GPS Hall Of Shame</a>,
 and that is a place you <em>don't</em> want to end up.</p>
 
@@ -129,7 +129,7 @@ top 5% of their profession in ability and experience.</p>
 
 <p>Red Hat and other distribution vendors select and integrate the
 work of literally thousands of open-source projects like GPSD to
-produce entire running operating systems of unprecedentedly high 
+produce entire running operating systems of unprecedentedly high
 quality.</p>
 
 <p>The main disadvantage of open-source development is that, except
diff --git a/www/hall-of-shame.html b/www/hall-of-shame.html
index 7b2adb55..049bab28 100644
--- a/www/hall-of-shame.html
+++ b/www/hall-of-shame.html
@@ -150,7 +150,7 @@ so...</p>
 <li><p>SiRF binary mode delivers HDOP but not PDOP or VDOP.  SiRFs in
 NMEA mode deliver all three.</p></li>
 
-<li><p>EverMore NMEA delivers UTC time.  EverMore binary protocol delivers 
+<li><p>EverMore NMEA delivers UTC time.  EverMore binary protocol delivers
 only GPS time, which has a time-varying offset from UTC &mdash; and no
 way to query the offset.</p></li>
 </ul>
diff --git a/www/hardware-tail.html b/www/hardware-tail.html
index b937d2a8..b19673f0 100644
--- a/www/hardware-tail.html
+++ b/www/hardware-tail.html
@@ -4,7 +4,7 @@
 
 <p>Some GPS receivers offer a 1PPS (one pulse per second) output that
 GPSD is capable of passing along to <code>ntpd</code> for use as an
-extremely accurate clock source.  These are marked as having PPS 
+extremely accurate clock source.  These are marked as having PPS
 in the table above. The "Claimed Accuracy" figures are taken
 from manufacturers' data sheets, and have not been independently
 verified.</p>
diff --git a/www/history.html b/www/history.html
index 6fce5afa..479ad7ff 100644
--- a/www/history.html
+++ b/www/history.html
@@ -132,12 +132,12 @@ gpsd's protocol or how to unpack its data into a C structure).</p>
 <p>Eric's work became the prototype for gpsd-2.0.  In mid-August of
 2004, Eric moved the project to Berlios with the approval and
 cooperation of all three of the 1.x maintainers.  (The main reason
-for that choice of hosting site was that it was among the first to 
-offer Subversion, which was new technology at the time and which 
+for that choice of hosting site was that it was among the first to
+offer Subversion, which was new technology at the time and which
 Eric and the 1.x developers were all interested in experimenting with.)</p>
 
 <p>In early 2005 the project took another significant turn as Eric
-implemented packet-sniffing and autobauding, threw out all the 
+implemented packet-sniffing and autobauding, threw out all the
 old configuration options. and factored the daemon into a thin
 multiplexer layer sitting on top of a set of device drivers. Support
 for non-NMEA devices dates from this redesign; SiRF was the first.</p>
diff --git a/www/references.html b/www/references.html
index 5af87b35..09069d04 100644
--- a/www/references.html
+++ b/www/references.html
@@ -97,15 +97,15 @@ read it and/or studied the behavior of GPSes claiming to conform to
 it.  This is the result.</dd>
 
 <dt><a href="http://www.gpsinformation.org/dale/nmea.htm">NMEA data</a></dt>
-<dd>This is one of the sources for the above. Includes some 
+<dd>This is one of the sources for the above. Includes some
 information on vendor-specific quirks that we don't.</dd>
 
 <dt><a href='http://www.navcen.uscg.gov/pdf/gps/IS_GPS_200H.pdf'>Navstar
  Global Positioning Interface Specification IS-GPS-200H (2013)</a></dt>
 <dd>This is the official specification for interpreting radio
-transmission from GPS satellites. You do not need to read this 
-unless you are trying to make sense of the raw 50BPS subframe 
-data.  Be warned: though this specification is not evil, it 
+transmission from GPS satellites. You do not need to read this
+unless you are trying to make sense of the raw 50BPS subframe
+data.  Be warned: though this specification is not evil, it
 is complex and nasty.</dd>
 
 <dt><a href='http://www.navcen.uscg.gov/pdf/gps/geninfo/2008SPSPerformanceStandardFINAL.pdf'>Standard Positioning Service
@@ -122,7 +122,7 @@ available to civil users through the GPS Standard Positioning Service
 Augmentation System.</dd>
 
 <dt><a href='https://ssl29.pair.com/dmarkle/puborder.php?show=3'>RTCM
-Recommended Standards for Differential GNSS</a></dt> 
+Recommended Standards for Differential GNSS</a></dt>
 <dd>This is the ordering page for the official RTCM SC-104 standards,
 both the obsolescent 2.x and current 3.x versions. The distribution
 terms are evil. At least one of the GPSD project members has purchased
@@ -134,13 +134,13 @@ href='https://www.google.com/search?q=RTCM+10402.3'>"RTCM
 10403.1"</a>.</dd>
 
 <dt><a
-href='http://www.itu.int/rec/recommendation.asp?type=items&amp;lang=e&amp;parent=r-rec-m.823-2-199710-i'>ITU-R M.823-2</a></dt> 
+href='http://www.itu.int/rec/recommendation.asp?type=items&amp;lang=e&amp;parent=r-rec-m.823-2-199710-i'>ITU-R M.823-2</a></dt>
 <dd>This specification documents some of the murky depths of
-rtcm-104, the specification used for broadcasting differential-gps 
+rtcm-104, the specification used for broadcasting differential-gps
 corrections. Unfortunately, its distribution terms are also evil.</dd>
 
 <dt><a href='http://ec.europa.eu/enterprise/policies/satnav/galileo/files/galileo-os-sis-icd-issue1-revision1_en.pdf'>Galileo Open Service SIS
-ICD (2010)</a></dt> 
+ICD (2010)</a></dt>
 <dd>This is issue 1 revision 1 0 of the Galileo Open Service Signal In Space
 Interface Control Document. The latest version of the official
 standard found <a
@@ -170,7 +170,7 @@ documents.</dd>
 using time-division multiple access in the VHF maritime mobile band</a></dt>
 <dd>The official standard descrcribing AIS.</dd>
 
-<dt><a href='http://www.topografix.com/gpx.asp'>GPX Exchange Format</a></dt> 
+<dt><a href='http://www.topografix.com/gpx.asp'>GPX Exchange Format</a></dt>
 <dd>GPX (the GPS Exchange Format) is a light-weight
 XML data format for the interchange of GPS data (waypoints, routes,
 and tracks) between applications and Web services on the Internet. The
@@ -234,10 +234,10 @@ for having been so stupid as to demand this.</p>
 
 <dl>
 <dt><a href='http://usglobalsat.com/downloads/SiRF_Binary_Protocol.pdf'>SiRF
-Binary Protocol Reference Manual</a> (2.4, November 2008) </dt> 
+Binary Protocol Reference Manual</a> (2.4, November 2008) </dt>
 <dd>The
 binary protocol for the chip used by over 80% of consumer-grade GPS
-mice.  For comparsion we also have older versions: 
+mice.  For comparsion we also have older versions:
 <a href="http://gpsd.googlecode.com/files/SiRF-SiRF-v2_3.pdf">2.2</a>
 (December 2007),
 <a href='http://gpsd.googlecode.com/files/SiRF-SiRF-v1_7.pdf'>1.7</a>
@@ -246,9 +246,9 @@ href='http://gpsd.googlecode.com/files/SiRF-SiRF-v1_6.pdf'>1.6</a>
 (April 2005) .</dd>
 
 <dt><a href='http://www.element14.com/community/servlet/JiveServlet/downloadBody/13410-102-1-42402/40.Sirf%20nmea%20ref%20manual.pdf'>SiRF
-NMEA Protocol Reference Manual</a> (2.2, November 2008) </dt> 
+NMEA Protocol Reference Manual</a> (2.2, November 2008) </dt>
 <dd><a href='https://www.sparkfun.com/datasheets/GPS/NMEA%20Reference%20Manual-Rev2.1-Dec07.pdf'>SiRF
-NMEA Protocol Reference Manual</a> (2.1, December 2007) </dd> 
+NMEA Protocol Reference Manual</a> (2.1, December 2007) </dd>
 
 
 <dt><a href='http://gpsd.googlecode.com/files/SiRF-Sectron.pdf'>SiRF GPS Protocol
@@ -282,7 +282,7 @@ and 3 chips.</dd>
 <dl>
 <dt><a href='https://gpsd.googlecode.com/files/itrax02-NMEA-1.31.pdf'>NMEA Protocol
 Specification for iTrax02 Evaluation Kit</a> (Rev 1.11, June
-2003)</dt> 
+2003)</dt>
 <dd>Describes the NMEA extensions for the iTrax chipset
 used by Fastrax GPSes. Supported by <code>gpsd</code>.</dd>
 
@@ -317,7 +317,7 @@ this very simple textual report format.</dd>
 
 <dl>
 <dt><a
-href='http://www.novatel.com/assets/Documents/Manuals/om-20000077.pdf'>Novatel Superstar II User Manual (2005)</a></dt> 
+href='http://www.novatel.com/assets/Documents/Manuals/om-20000077.pdf'>Novatel Superstar II User Manual (2005)</a></dt>
 <dd>Describes the OEM board, include some good general overview
 material on GPS technology. Doesn't describe control or reporting
 commands.</dd>
@@ -345,12 +345,12 @@ Guide</a> (May 2003)</dt>
 generic NMEA GPS.   Supported by <code>gpsd</code>.</dd>
 
 <dt><a href='https://gpsd.googlecode.com/files/Emt_GPS_User_Protocol_Rev_D.pdf'
->GM-X205 GPS Receiver Module User's Guide</a> (Issue D, August 2003)</dt> 
+>GM-X205 GPS Receiver Module User's Guide</a> (Issue D, August 2003)</dt>
 <dd>Describes the binary protocol emitted
 by EverMore GM-X205 GPS chipset. Supported by <code>gpsd</code>.</dd>
 
 <dt><a href='http://gpsd.googlecode.com/files/crescent-sdx-3.pdf'>Crescent Integrator's Manual</a> (November 2005)</dt>
-<dd>Reference for the Hemisphere GPS from CSI Wireless.  Has both an NMEA mode 
+<dd>Reference for the Hemisphere GPS from CSI Wireless.  Has both an NMEA mode
 and a binary protocol. We have not been able to test with one of these, but the
 manual suggests <code>gpsd</code> should handle the NMEA mode just fine.</dd>
 
@@ -361,7 +361,7 @@ of NMEA they call the <q>standard Ashtech command set</q>.  We
 have not been able to test with one of these, but the manual suggests
 <code>gpsd</code> should handle the NMEA mode just fine.</dd>
 
-<dt><a href='http://gpsd.googlecode.com/files/truenorth-reference.pdf'>True North Revolution Compass Technical 
+<dt><a href='http://gpsd.googlecode.com/files/truenorth-reference.pdf'>True North Revolution Compass Technical
 Reference</a> (Revision B, August 2003)</dt>
 <dd>Interface spec for a digital magnetic compass that reports in NMEA.  <code>gpsd</code> had support for this in versions up to 2.33; whether it keeps
 that status in later releases will depend on whether we can get test hardware.</dd>
@@ -394,7 +394,7 @@ with LocSense based receivers.</dd>
 <dd>Describes the binary protocol used by Rockwell/Conexant Zodiac chipsets.
 Supported by <code>gpsd</code>.  Now obsolete; SiRF ate their lunch.</dd>
 
-<dt><a href='http://code.google.com/p/gpsd/downloads/detail?name=SiRF-Axiom.pdf&amp;can=2&amp;q='>Axiom Sandpiper II Documentation</a> [broken link] (August 2000)</dt> 
+<dt><a href='http://code.google.com/p/gpsd/downloads/detail?name=SiRF-Axiom.pdf&amp;can=2&amp;q='>Axiom Sandpiper II Documentation</a> [broken link] (August 2000)</dt>
 
 <dd>We have archived the most complete available documentation on the Axiom
 Sandpiper II OEM module (discontinued, vendor has gone out of
@@ -409,7 +409,7 @@ business). Supported by <code>gpsd</code>.</dd>
 coordinates reported by many vendor binary protocols to ordinary
 geodetic coordinates.</dd>
 
-<dt><a href="http://williams.best.vwh.net/avform.htm">Aviation 
+<dt><a href="http://williams.best.vwh.net/avform.htm">Aviation
 Formulary</a></dt>
 <dd>Compendium of formulas related to geodetic navigation, with examples.</dd>
 </dl>
diff --git a/www/reliability.html b/www/reliability.html
index 6349dbe3..638e3bc9 100644
--- a/www/reliability.html
+++ b/www/reliability.html
@@ -119,7 +119,7 @@ We've as yet been unable to eliminate all scan-build warnings, but we
 require the code to audit clean under all the other tools on each
 release. </p>
 
-<p>We used to use <a href='http://www.splint.org'>splint</a>, until 
+<p>We used to use <a href='http://www.splint.org'>splint</a>, until
 we found that we couldn't replicate the results of splint runs
 reliably in different Linux distributions. Also, far and away the biggest
 pain in the ass to use. You have to drop cryptic, cluttery magic
diff --git a/www/replacing-nmea.xml b/www/replacing-nmea.xml
index 4af8c8f2..3092b8a2 100644
--- a/www/replacing-nmea.xml
+++ b/www/replacing-nmea.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE article PUBLIC 
+<!DOCTYPE article PUBLIC
    "-//OASIS//DTD DocBook XML V4.1.2//EN"
    "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
 <!ENTITY howto         "http://en.tldp.org/HOWTO/">
@@ -17,7 +17,7 @@
   <surname>Raymond</surname>
   <affiliation>
     <orgname><ulink url="&homepage;">
-    Thyrsus Enterprises</ulink></orgname> 
+    Thyrsus Enterprises</ulink></orgname>
     <address>
     <email>esr@thyrsus.com</email>
     </address>
@@ -25,7 +25,7 @@
 </author>
 <copyright>
   <year>2004</year>
-  <holder role="mailto:esr@thyrsus.com">Eric S. Raymond</holder> 
+  <holder role="mailto:esr@thyrsus.com">Eric S. Raymond</holder>
 </copyright>
 <!-- legalnotice>
   <title>Copyright</title>
@@ -73,7 +73,7 @@
       <date>21 November 2006</date>
       <authorinitials>esr</authorinitials>
       <revremark>
-         Fixed timestamp to Zulu time.  Specified signed latitude.  
+         Fixed timestamp to Zulu time.  Specified signed latitude.
       </revremark>
    </revision>
    <revision>
@@ -114,7 +114,7 @@ identifying text tag, followed by multiple comma-separated textual
 fields, ended by an asterisk, a checksum, and LF/CR.  This is a
 simple, clean format with good extensibility, easy to parse and
 generate.  It is well adapted to its job, which is to pass
-small amounts of numeric and status information.  The textual 
+small amounts of numeric and status information.  The textual
 format makes it easy to log NMEA sessions, edit them, and play them
 back &mdash; a substantial advantage in developing talker and
 parser software.</para>
@@ -134,7 +134,7 @@ precision.  </para></listitem>
 
 <listitem><para>
 It is not possible to get a time/position/velocity report in a single
-sentence.  Some sentences (GPRMC) report time and 2D position and velocity, 
+sentence.  Some sentences (GPRMC) report time and 2D position and velocity,
 some (GPGGA) report time and 3D position, some (GPVTG) report velocity
 only.  As a result, the API for a protocol client is complicated by
 the necessity of maintaining separate age indications for 2D position,
@@ -171,7 +171,7 @@ complexity in the receiver by not requiring a stateful parser.
 
 <listitem><para>
 Position accuracy estimates are not easy to compute from
-NMEA reports.  Reporting a measurement without giving its 95% 
+NMEA reports.  Reporting a measurement without giving its 95%
 confidence interval is bad practice.
 </para></listitem>
 
@@ -185,7 +185,7 @@ is more powerful and flexible at these things; thus, the GPS only
 needs to be a time/position/velocity oracle.
 </para></listitem>
 
-<listitem><para> 
+<listitem><para>
 NMEA 0183 is in general very loosely specified and
 poorly documented. Its problems are compounded by the fact that it is
 a proprietary specification, jealously guarded by IP lawyers.
@@ -213,14 +213,14 @@ a protocol for GPS reports;</para>
 Keep the low-level syntax, because it's not broken.  It has all the
 advantages of textual protocols.  Going to a more tightly-packed
 binary format might look attractive at first glance, but the gain in
-information would be marginal at best. Textual formats already use 
-7 out of 8 bits per byte and encode variable-length numeric fields more 
+information would be marginal at best. Textual formats already use
+7 out of 8 bits per byte and encode variable-length numeric fields more
 efficiently than binary; also they avoid endianness issues.
 </para></listitem>
 
-<listitem><para> 
+<listitem><para>
 Add to the syntax standard ways of indicating that either (a) the
-GPS cannot now ship valid data for the field, or (b) the GPS will 
+GPS cannot now ship valid data for the field, or (b) the GPS will
 <emphasis>never</emphasis> ship data for this field.
 </para></listitem>
 
@@ -230,7 +230,7 @@ every sentence.  Every timestamp should be in the same standard form
 and should include a full date with century.</para>
 </listitem>
 
-<listitem><para> 
+<listitem><para>
 Report the uncertainty corresponding to a 95% confidence interval on a
 standard normal distribution for each measurement field.
 </para></listitem>
@@ -241,7 +241,7 @@ time/position/velocity and the uncertainties in same.
 </para></listitem>
 
 <listitem><para>
-Make it an objective of the design for an informal specification to fit 
+Make it an objective of the design for an informal specification to fit
 on a single page.
 </para></listitem>
 </itemizedlist>
@@ -274,7 +274,7 @@ url='http://www.w3.org/TR/NOTE-datetime'>W3C profile of ISO
 
 <orderedlist>
 <listitem><para>
-The sentence tag is GPTPV, standing for Time/Position/Velocity.  
+The sentence tag is GPTPV, standing for Time/Position/Velocity.
 </para></listitem>
 
 <listitem><para>
@@ -320,7 +320,7 @@ The tenth field is course over ground in degrees from true north.
 </para></listitem>
 
 <listitem><para>
-The eleventh field is uncertainty of course over ground in degrees  (95% 
+The eleventh field is uncertainty of course over ground in degrees  (95%
 confidence).
 </para></listitem>
 
@@ -347,7 +347,7 @@ mode field is added to satisfy a U.S. regulator's requirement.</para>
 <programlisting>
 $GPTPV,2005-02-11T04:40:51.231Z,?,49.45,-123.12,2.3,70.1,52.0,01.0,02.1,23.1,0.6,,,8,A*31
 
-     2005-02-11T04:40:51.231Z,  Time (Feb 11 04:40:51 EST 2005) 
+     2005-02-11T04:40:51.231Z,  Time (Feb 11 04:40:51 EST 2005)
      ?,                         Timestamp uncertainty will never be reported
      49.45,                     Latitude (- sign indicates latitude south)
      -123.12,                   Longitude (- sign indicates longitude west)
@@ -371,7 +371,7 @@ $GPTPV,2005-02-11T04:40:51.231Z,?,49.45,-123.12,2.3,70.1,52.0,01.0,02.1,23.1,0.6
 
 <orderedlist>
 <listitem><para>
-The sentence tag is GPSVU, standing for Satellite View Update.  
+The sentence tag is GPSVU, standing for Satellite View Update.
 </para></listitem>
 
 <listitem><para>
@@ -419,7 +419,7 @@ ID, and the fields are as follows:</para>
 
 <orderedlist>
 <listitem><para>
-The sentence tag is GPVID, standing for Vendor ID.  
+The sentence tag is GPVID, standing for Vendor ID.
 </para></listitem>
 
 <listitem><para>
@@ -427,19 +427,19 @@ The first field is the required timestamp.
 </para></listitem>
 
 <listitem><para>
-The second field is the SGPS revision level.  
+The second field is the SGPS revision level.
 </para></listitem>
 
 <listitem><para>
-The third field is the vendor name.  
+The third field is the vendor name.
 </para></listitem>
 
 <listitem><para>
-The fourth field is the device name or model number.  
+The fourth field is the device name or model number.
 </para></listitem>
 
 <listitem><para>
-The fifth field is a chipset designation.  
+The fifth field is a chipset designation.
 </para></listitem>
 
 <listitem><para>
@@ -461,7 +461,7 @@ $GPVID,2006-11-17T12:29:37Z,1.0,Haicom,H204S,SiRF-II,231.00.00*5C
 </sect2>
 <sect2><title>GPGSP</title>
 
-<para>With the addition of a fourth sentence, $GPSGP, transition to the 
+<para>With the addition of a fourth sentence, $GPSGP, transition to the
 new protocol would be easy.  It would have two forms:</para>
 
 <para>$GPSGP,1: directs the receiver to emit GPPVT and GPSVU
@@ -478,7 +478,7 @@ $GPGSP,1*4E
 
 
 <para>An SGPS-conformant receiver is required to respond with
-$GPSGP,timestamp,x,y where x is 1 or 0 reflecting the command, and y is 1 or 0 
+$GPSGP,timestamp,x,y where x is 1 or 0 reflecting the command, and y is 1 or 0
 reporting its new mode.</para>
 
 <para>Other listeners can distinguish GPGSP responses from requests
@@ -498,7 +498,7 @@ corresponding report based on most recent available data.</para>
 
 <para>Astute readers will already have noted that the SGPS sentences
 might be sold as a minor extension to NMEA 0183. first supplementing
-and eventually obsolescing the half-dozen or so sentences emitted by 
+and eventually obsolescing the half-dozen or so sentences emitted by
 most modern GPSes.</para>
 
 <para>The only fields reported in the SGPS set that cannot be
diff --git a/www/troubleshooting.html b/www/troubleshooting.html
index 5a265533..dbd3baf9 100644
--- a/www/troubleshooting.html
+++ b/www/troubleshooting.html
@@ -100,7 +100,7 @@ Troubleshooting</a></p>
 <p>We do not yet have troubleshooting instructions for GPSes using
 CF (Compact Flash) interfaces. Please contribute some if you can.</p>
 
-<p>If your test client does not show data, keep reading.</p> 
+<p>If your test client does not show data, keep reading.</p>
 
 <h1 id='gpstroubleshooting'>GPS troubleshooting</h1>
 
diff --git a/www/upstream-bugs.html b/www/upstream-bugs.html
index 59c247eb..912900d2 100644
--- a/www/upstream-bugs.html
+++ b/www/upstream-bugs.html
@@ -51,7 +51,7 @@
 <script type="text/javascript"
  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
     </script>
-<hr> 
+<hr>
 <a href="http://validator.w3.org/check/referer"><img
  src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"
  height="31" width="88"></a>
@@ -66,7 +66,7 @@ maintainer, we've tried to kick these upstream.</p>
 <h1>Links to Open User-Visible Problems</h1>
 
 <ul>
-<li><a href="#osx-pl2303">Unknown osx-pl2303 driver issues on Mac OS X</a></li> 
+<li><a href="#osx-pl2303">Unknown osx-pl2303 driver issues on Mac OS X</a></li>
 <li><a href="#tiocmwait">PPS fails: ioctl(TIOCMIWAIT) hangs after tcsetattr()</a></li>
 <li><a href="#pps-gpio">The pps-gpio driver only reports on one edge</a></li>
 <li><a href="#bluetooth">Firmware problems in some Bluetooth and USB devices can hang them</a></li>
diff --git a/www/wishlist.html b/www/wishlist.html
index c1d60ecb..13824a03 100644
--- a/www/wishlist.html
+++ b/www/wishlist.html
@@ -53,7 +53,7 @@ src="http://www.catb.org/hacker-emblem/glider.png" alt="hacker emblem"></a><hr>
 <script type="text/javascript"
  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
     </script>
-<hr> 
+<hr>
 <a href="http://validator.w3.org/check/referer"><img
  src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"
  height="31" width="88"></a>