- make it resemble html.

6 files changed, 24 insertions, 24 deletions

diff --git a/docs/busybox.net/about.html b/docs/busybox.net/about.html
index 305dabf9d..080f8a9dd 100644
--- a/docs/busybox.net/about.html
+++ b/docs/busybox.net/about.html
@@ -24,9 +24,9 @@ nodes in /dev, a few configuration files in /etc, and a Linux kernel.
 
 <p>
 
-BusyBox is maintained by <a href=http://www.landley.net>Rob Landley</a>, and
+BusyBox is maintained by <a href="http://www.landley.net/">Rob Landley</a>, and
 licensed under the
-<a href= "http://www.gnu.org/copyleft/gpl.html">GNU GENERAL PUBLIC LICENSE</a>
+<a href="http://www.gnu.org/copyleft/gpl.html">GNU GENERAL PUBLIC LICENSE</a>
 
 <p>
 <p>
@@ -56,7 +56,7 @@ consider these fine companies!
 </ul>
 
 If you wish to be a sponsor, or if you have already contributed and would like
-your name added here, email <a href= "mailto:andersen@codepoet.org">Erik</a>.
+your name added here, email <a href="mailto:andersen@codepoet.org">Erik</a>.
 
 
 <!--#include file="footer.html" -->
diff --git a/docs/busybox.net/news.html b/docs/busybox.net/news.html
index 91e756f49..f70c0e3a3 100644
--- a/docs/busybox.net/news.html
+++ b/docs/busybox.net/news.html
@@ -7,7 +7,7 @@
     maintainership to Rob Landley was license enforcement.  BusyBox and
     uClibc's existing license enforcement efforts (pro-bono representation
     by Erik's father's law firm, and the
-    <a href=http://www.busybox.net/shame.html>Hall of Shame</a>), haven't
+    <a href="http://www.busybox.net/shame.html">Hall of Shame</a>), haven't
     scaled to match the popularity of the projects.  So we put our heads
     together and did the obvious thing: ask Pamela Jones of
     <a href="http://www.groklaw.net">Groklaw</a> for suggestions.  She
@@ -17,9 +17,9 @@
     <a href="http://www.softwarefreedom.org">Software Freedom Law Center</a>
     has agreed to represent BusyBox and uClibc.  We join a number of other
     free and open source software projects (such as
-    <a href=http://lwn.net/Articles/141806/>X.org</a>,
+    <a href="http://lwn.net/Articles/141806/">X.org</a>,
     <a href="http://lwn.net/Articles/135413/">Wine</a>, and
-    <a href=http://plone.org/foundation/newsitems/software-freedom-law-center-support/>Plone</a>
+    <a href="http://plone.org/foundation/newsitems/software-freedom-law-center-support/>Plone"</a>
     in being represented by a fairly cool bunch of lawyers, which is not a
     phrase you get to use every day.</p>
 
@@ -35,7 +35,7 @@
     <p>The new stable release is
     <a href="http://www.busybox.net/downloads/busybox-1.1.0.tar.bz2">BusyBox
     1.1.0</a>.  It has a number of improvements, including several new applets.
-    (It also has <a href=http://www.busybox.net/lists/busybox/2006-January/017733.html>a few rough spots</a>,
+    (It also has <a href="http://www.busybox.net/lists/busybox/2006-January/017733.html">a few rough spots</a>,
     but we're trying out a "release early, release often" strategy to see how
     that works.  Expect 1.1.1 sometime in March.)</p>
 
diff --git a/docs/busybox.net/programming.html b/docs/busybox.net/programming.html
index f54f018ed..f5433f519 100644
--- a/docs/busybox.net/programming.html
+++ b/docs/busybox.net/programming.html
@@ -22,7 +22,7 @@
   <li><a href="#who">Who are the BusyBox developers?</a></li>
 </ul>
 
-<h2><b><a name="goals" />What are the goals of busybox?</b></h2>
+<h2><b><a name="goals">What are the goals of busybox?</a></b></h2>
 
 <p>Busybox aims to be the smallest and simplest correct implementation of the
 standard Linux command line tools.  First and foremost, this means the
@@ -31,7 +31,7 @@ and cleanest implementation we can manage, be <a href="#standards">standards
 compliant</a>, minimize run-time memory usage (heap and stack), run fast, and
 take over the world.</p>
 
-<h2><b><a name="design" />What is the design of busybox?</b></h2>
+<h2><b><a name="design">What is the design of busybox?</a></b></h2>
 
 <p>Busybox is like a swiss army knife: one thing with many functions.
 The busybox executable can act like many different programs depending on
@@ -53,9 +53,9 @@ binaries for each applet, and a "libbb.so" to make the busybox common code
 available as a shared library.  Neither is ready yet at the time of this
 writing.</p>
 
-<a name="source" />
+<a name="source"></a>
 
-<h2><a name="source_applets" /><b>The applet directories</b></h2>
+<h2><a name="source_applets"><b>The applet directories</b></a></h2>
 
 <p>The directory "applets" contains the busybox startup code (applets.c and
 busybox.c), and several subdirectories containing the code for the individual
@@ -95,7 +95,7 @@ html, txt, and man page formats) in the docs directory.  See
 <a href="#adding">adding an applet to busybox</a> for more
 information.</p>
 
-<h2><a name="source_libbb" /><b>libbb</b></h2>
+<h2><a name="source_libbb"><b>libbb</b></a></h2>
 
 <p>Most non-setup code shared between busybox applets lives in the libbb
 directory.  It's a mess that evolved over the years without much auditing
@@ -110,7 +110,7 @@ of open(), close(), read(), and write() that test for their own failures
 and/or retry automatically, linked list management functions (llist.c),
 command line argument parsing (getopt_ulflags.c), and a whole lot more.</p>
 
-<h2><a name="adding" /><b>Adding an applet to busybox</b></h2>
+<h2><a name="adding"><b>Adding an applet to busybox</b></a></h2>
 
 <p>To add a new applet to busybox, first pick a name for the applet and
 a corresponding CONFIG_NAME.  Then do this:</p>
@@ -151,10 +151,10 @@ bugs.  Be sure to try both "allyesconfig" and "allnoconfig" (and
 
 </ul>
 
-<h2><a name="standards" />What standards does busybox adhere to?</a></h2>
+<h2><a name="standards">What standards does busybox adhere to?</a></h2>
 
 <p>The standard we're paying attention to is the "Shell and Utilities"
-portion of the <a href=http://www.opengroup.org/onlinepubs/009695399/>Open
+portion of the <a href="http://www.opengroup.org/onlinepubs/009695399/">Open
 Group Base Standards</a> (also known as the Single Unix Specification version
 3 or SUSv3).  Note that paying attention isn't necessarily the same thing as
 following it.</p>
@@ -330,7 +330,7 @@ return 0 unless it has hit the end of input, and an attempt to write 0
 bytes should be ignored by the OS.)</p>
 
 <p>As for short writes, play around with two processes piping data to each
-other on the command line (cat bigfile | gzip > out.gz) and suspend and
+other on the command line (cat bigfile | gzip &gt; out.gz) and suspend and
 resume a few times (ctrl-z to suspend, "fg" to resume).  The writer can
 experience short writes, which are especially dangerous because if you don't
 notice them you'll discard data.  They can also happen when a system is under
@@ -340,7 +340,7 @@ text console scrolling...)</p>
 
 <p>So will data always be read from the far end of a pipe at the
 same chunk sizes it was written in?  Nope.  Don't rely on that.  For one
-counterexample, see <a href="http://www.faqs.org/rfcs/rfc896.html">rfc 896</p>
+counterexample, see <a href="http://www.faqs.org/rfcs/rfc896.html">rfc 896 
 for Nagle's algorithm</a>, which waits a fraction of a second or so before
 sending out small amounts of data through a TCP/IP connection in case more
 data comes in that can be merged into the same packet.  (In case you were
diff --git a/docs/busybox.net/shame.html b/docs/busybox.net/shame.html
index 2c800c85f..5cd868aa0 100644
--- a/docs/busybox.net/shame.html
+++ b/docs/busybox.net/shame.html
@@ -68,7 +68,7 @@ the busybox license by releasing the source code with your product.
   </li><li><a href="http://www.a-link.com/RR64AP.html">Avaks alink Roadrunner 64</a>
   <br> Partial source available, based on source distributed under NDA from <a href="http://www.lsilogic.com/products/dsl_platform_solutions/hb_linuxr2_2.html"> LSILogic</a>. Why the NDA LSILogic, what are you hiding ?
   <br>To verify the Avaks infrigment see my slashdot <a href="http://slashdot.org/~bug1/journal/">journal</a>. 
-  <br>The ZipIt wireless IM device appears to be using Busybox-1.00-pre1 in the ramdisk, however no source has been made available.</br>
+  <br>The ZipIt wireless IM device appears to be using Busybox-1.00-pre1 in the ramdisk, however no source has been made available.
   </li><li>Undoubtedly there are others...  Please report them so we can shame them (or if necessary sue them) into compliance.
 
 </ul>
diff --git a/docs/busybox.net/subversion.html b/docs/busybox.net/subversion.html
index 3743b4da1..65be61c73 100644
--- a/docs/busybox.net/subversion.html
+++ b/docs/busybox.net/subversion.html
@@ -1,13 +1,13 @@
 <!--#include file="header.html" -->
 
-<h3>Browse Source</h2>
+<h3>Accessing Source</h3>
 
 
 
-<h3>Patches</h3>
+<h2>Patches</h2>
 
 <p>If you don't want to mess with subversion, you can download
-<a href="/downloads/patches">all BusyBox patches</a> or check the
+<a href="/downloads/patches/">all BusyBox patches</a> or check the
 <a href="/downloads/patches/last10.html">ten most recent</a>.
 
 <h3>Anonymous Subversion Access</h3>
diff --git a/docs/busybox.net/tinyutils.html b/docs/busybox.net/tinyutils.html
index 7ed795f5d..ef76d33d8 100644
--- a/docs/busybox.net/tinyutils.html
+++ b/docs/busybox.net/tinyutils.html
@@ -28,9 +28,9 @@ dev mailing list.
 </table>
 
 <p>In a gui environment, you'll probably want a web browser.
-<a href=http://www.konqueror.org/embedded/>Konqueror Embedded</a> requires QT
-(or QT Embedded), but not KDE.  The <a href=http://www.dillo.org/>Dillo</a>
-requires GTK+, but not Gnome.  Or you can try the <a href=http://links.twibright.com/>graphical
+<a href="http://www.konqueror.org/embedded/">Konqueror Embedded</a> requires QT
+(or QT Embedded), but not KDE.  The <a href="http://www.dillo.org/">Dillo</a>
+requires GTK+, but not Gnome.  Or you can try the <a href="http://links.twibright.com/">graphical
 version of links</a>.</p>
 
 <!--#include file="footer.html" -->