diff --git a/index.html b/index.html
index 01671b8fc..216cb3f76 100644
--- a/index.html
+++ b/index.html
@@ -3,7 +3,7 @@
 <head>
 <meta http-equiv="Content-Language" content="en-us">
 <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
+<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
 <meta name="ProgId" content="FrontPage.Editor.Document">
 <title>Building Boost Libraries</title>
 </head>
@@ -17,17 +17,17 @@ Boost Libraries</h1>
 <table border="1" cellpadding="5" width="656">
   <tr>
     <td width="638"><font size="5" color="#FF0000"><b>Read This
-      First!</b></font> <p>Boost.Build is not mature yet.&nbsp; Some features
+      First!</b></font> <p>Boost.Build is fairly new as yet.&nbsp; Some features
       are missing or incomplete. Instructions for accomplishing basic tasks
       (this page) are rudimentary.&nbsp; But enough functionality is working
       well to make using Boost.Build worthwhile.&nbsp; The important
       bits-and-pieces are all there - what's left is some of the relatively
-      minor glue to make the system smooth and easy to use.</p> <p>Don't expect
-      building a full Boost object library for any random compiler to work
-      yet.&nbsp; If there isn't a jam configuration file for your favorite
-      compiler, consider contributing one. Secondary tasks like copying
-      libraries to installation specific directories are also weak.</p> <p>Note
-      that the underlying Jam build engine is mature software, and has been
+      minor glue to make the system smooth and easy to use. Secondary tasks like 
+    copying libraries to installation specific directories are weak.</p> <p>If 
+    there isn't a configuration file (see <a href="#Tools">Tools</a>) available 
+    for your favorite compiler, consider contributing one. </p> <p>Note
+      that the underlying Boost.Jam build engine is mature software, and the 
+    original Jam build engine has been
       widely used for many years.&nbsp; The Boost specific extensions are well
       on their way to becoming stable, and have begun to attract interest and
       use outside of Boost.</td>
@@ -38,10 +38,14 @@ Boost Libraries</h1>
 <a href="#Preliminaries">Preliminaries</a><br>
 <a href="#Building">Building Boost Libraries</a><br>
 <a href="#Moretools">More on using the tools</a><br>
-<a href="#Tools">Tools available</a></p>
+<a href="#Tools">Tools available</a><br>
+<a href="#Jam">Boost.Jam executable</a></p>
 <h2><a name="Introduction">Introduction</a></h2>
 <p>These instructions explain how to accomplish common tasks using <b>Boost.Build</b>,
-the Boost Build System.</p>
+the Boost Build System.&nbsp; The build system uses <a href="build_system.htm">
+Boost.Jam</a>, an extension of the
+<a href="http://www.perforce.com/jam/jam.html">Perforce Jam</a> portable <i>make</i> 
+replacement.</p>
 <p>For tasks not covered here, see the full <a href="build_system.htm">build
 system documentation</a>.</p>
 <p>Note that many Boost libraries are implemented entirely within their headers,
@@ -50,41 +54,11 @@ require building object libraries first include the Boost Python, Regular
 Expression, and Thread libraries.</p>
 <h2><a name="Preliminaries">Preliminaries</a></h2>
 <ul>
-  <li><a href="../../more/download.html">Download Boost</a>, and unpack the full
+  <li><a href="../../more/download.html">Download Boost</a>, and unpack the full 
     directory structure into some root directory.</li>
-
-    <p>
-    
-  <li>install the Boost Jam binary executable where it will be found when
-    invoked from the command line.</li><br>
-    
-  <ul>
-
-    <li>A Win32 pre-built executable is available <a href="jam.exe">here</a> (168K).
-
-    <li>For most Unix variants, you can build Boost Jam by simply invoking
-        <tt>make</tt> in the <tt>tools/build/jam_src</tt> subdirectory of your
-        boost installation.
-
-        <li><a href="http://public.perforce.com/public/jam/src/README">Build
-        Instructions</a> are the same as for &quot;<a
-        href="http://www.perforce.com/jam/jam.html">Classic Jam</a>&quot;, if
-        you need them.
-
-        <li>Your new Jam executable will be located in a newly-created
-        <tt>tools/build/jam_src/bin.</tt><i>platform</i> subdirectory.
-
-        <li>If you build Jam for a new platform using the same boost
-        installation, be sure to first remove all object files, executables, and
-        libraries created by the inital make in the <tt>jam_src</tt> directory.
-  </ul>
-
-  <p>
-
-</ul>
-<blockquote>
-</blockquote>
-<ul>
+  <li>Install the <a href="#Jam">Boost.Jam executable</a> if needed. <a href="#Jam">
+  Pre-builts</a> are available. Make sure it's in your path. (Note: Boost 
+  requires an enhanced version of Jam; the basic version won't work.)</li>
   <li>Set any environment variables required to run your compiler and related
     tools from the command line. (It might be a good idea to verify your command
     line compiler is working if you don't use it regularly.) If you don't want
@@ -96,22 +70,18 @@ Expression, and Thread libraries.</p>
 steps.&nbsp; The sample commands given will work for both UNIX and Windows.</p>
 <ul>
   <li>Change to the Boost root directory.&nbsp; (The directory you unpacked the
-    distribution into.&nbsp; Among others, it contain the file c++boost.gif,
-    subdirectories boost, libs, more, etc.)</li>
+    distribution into.&nbsp; Among others, it contains the file c++boost.gif,
+    and subdirectories boost, libs, more, etc.)</li>
   <blockquote>
     <p><code>chdir my_boost</code></p>
   </blockquote>
 
-  <p>
-
   <li>Build the Boost libraries for your <a href="#Tools">tools</a>. The example
     is for the GNU and Metrowerks compilers.</li>
   <blockquote>
     <p><code>jam&nbsp;-sBOOST_ROOT=.&nbsp;-sTOOLS=&quot;gcc&nbsp;metrowerks&quot;</code></p>
   </blockquote>
 
-  <p>
-
   <li>If you don't want to specify <code>BOOST_ROOT</code> on the command-line,
   you can instead set the <code>BOOST_ROOT</code> environment variable (an
   absolute path is recommended).
@@ -146,7 +116,7 @@ steps.&nbsp; The sample commands given will work for both UNIX and Windows.</p>
     <td>Borland command line compiler tools</td>
   </tr>
   <tr>
-    <td>como</td>
+    <td><code>como</code></td>
     <td>Comeau command line compiler tools</td>
   </tr>
   <tr>
@@ -158,7 +128,7 @@ steps.&nbsp; The sample commands given will work for both UNIX and Windows.</p>
     <td>GNU GCC command line compiler tools, using the STLport library</td>
   </tr>
   <tr>
-    <td>intel-win32</td>
+    <td><code>intel-win32</code></td>
     <td>Intel command line compiler tools, in the Win32 environment using the
       Microsoft library</td>
   </tr>
@@ -179,7 +149,7 @@ steps.&nbsp; The sample commands given will work for both UNIX and Windows.</p>
     <td>Microsoft Visual C++ command line compiler tools, using the STLport library</td>
   </tr>
   <tr>
-    <td>vacpp</td>
+    <td><code>vacpp</code></td>
     <td>IBM Visual Age C++ command line compiler tools</td>
   </tr>
 </table>
@@ -189,12 +159,67 @@ the compiler.</p>
 to the tools/build subdirectory, where xxxx is the name of the tool being
 added.&nbsp; If you write an additional toolset file, please submit it to Boost
 so others may benefit from your work.</p>
+<h2>Boost.<a name="Jam">Jam</a> executable</h2>
+<p>Pre-built Boost.Jam executables are available for the following platforms:</p>
+    
+  <ul>
+    <li><a href="http://boost.sourceforge.net/jam-executables/bin.aix/jam.gz">
+    IBM Aix</a> </li>
+    <li>
+    <a href="http://boost.sourceforge.net/jam-executables/bin.linuxx86/jam.gz">
+    Linux-x86</a> </li>
+    <li>
+    <a href="http://boost.sourceforge.net/jam-executables/boost-build.win.zip">
+    Microsoft Windows</a> (includes Boost.Build files and boost-build helper 
+    program).</li>
+    <li><a href="http://boost.sourceforge.net/jam-executables/bin.irix/jam.gz">
+    SGI Irix</a> </li>
+    <li>
+    <a href="http://boost.sourceforge.net/jam-executables/bin.solaris/jam.gz">
+    SUN Solaris</a> </li>
+</ul>
+<p>RedHat Linux RPM packages are available:</p>
+<ul>
+  <li>
+  <a href="http://boost.sourceforge.net/jam-executables/boost-jam-3.0-1.i386.rpm">
+  Boost.Jam rpm</a> </li>
+  <li>
+  <a href="http://boost.sourceforge.net/jam-executables/boost-build-1.0-1.i386.rpm">
+  Boost.Build rpm</a> </li>
+  <li>
+  <a href="http://boost.sourceforge.net/jam-executables/boost-jam-3.0-1.src.rpm">
+  Boost.Jam source rpm </a></li>
+  <li>
+  <a href="http://boost.sourceforge.net/jam-executables/boost-build-1.0-1.src.rpm">
+  Boost.Build source rpm</a></li>
+</ul>
+<p>The Boost.Jam source files are included in the Boost distribution, so you can build 
+the Boost.Jam executable yourself:</p>
+    
+  <ul>
+
+    <li>For most Unix variants, you can build Boost.Jam by simply invoking
+        <tt>make</tt> in the <tt>tools/build/jam_src</tt> subdirectory of your
+        boost installation.
+
+        <li><a href="http://public.perforce.com/public/jam/src/README">Build
+        Instructions</a> are the same as for &quot;<a
+        href="http://www.perforce.com/jam/jam.html">Classic Jam</a>&quot;, if
+        you need them.
+
+        <li>Your new Boost.Jam executable will be located in a newly-created
+        <tt>tools/build/jam_src/bin.</tt><i>platform</i> subdirectory.
+
+        <li>If you build Boost.Jam for a new platform using the same boost
+        installation, be sure to first remove all object files, executables, and
+        libraries created by the initial make in the <tt>jam_src</tt> directory.
+  </ul>
 <hr>
-<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->08 November, 2001<!--webbot bot="Timestamp" endspan i-checksum="39353" -->
+<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->28 November, 2001<!--webbot bot="Timestamp" i-checksum="39367" endspan -->
 </p>
 <p>© Copyright 2001 Beman Dawes</p>
 <p>&nbsp;</p>
 
 </body>
 
-</html>
+</html>
\ No newline at end of file
diff --git a/v1/index.html b/v1/index.html
index 01671b8fc..216cb3f76 100644
--- a/v1/index.html
+++ b/v1/index.html
@@ -3,7 +3,7 @@
 <head>
 <meta http-equiv="Content-Language" content="en-us">
 <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
+<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
 <meta name="ProgId" content="FrontPage.Editor.Document">
 <title>Building Boost Libraries</title>
 </head>
@@ -17,17 +17,17 @@ Boost Libraries</h1>
 <table border="1" cellpadding="5" width="656">
   <tr>
     <td width="638"><font size="5" color="#FF0000"><b>Read This
-      First!</b></font> <p>Boost.Build is not mature yet.&nbsp; Some features
+      First!</b></font> <p>Boost.Build is fairly new as yet.&nbsp; Some features
       are missing or incomplete. Instructions for accomplishing basic tasks
       (this page) are rudimentary.&nbsp; But enough functionality is working
       well to make using Boost.Build worthwhile.&nbsp; The important
       bits-and-pieces are all there - what's left is some of the relatively
-      minor glue to make the system smooth and easy to use.</p> <p>Don't expect
-      building a full Boost object library for any random compiler to work
-      yet.&nbsp; If there isn't a jam configuration file for your favorite
-      compiler, consider contributing one. Secondary tasks like copying
-      libraries to installation specific directories are also weak.</p> <p>Note
-      that the underlying Jam build engine is mature software, and has been
+      minor glue to make the system smooth and easy to use. Secondary tasks like 
+    copying libraries to installation specific directories are weak.</p> <p>If 
+    there isn't a configuration file (see <a href="#Tools">Tools</a>) available 
+    for your favorite compiler, consider contributing one. </p> <p>Note
+      that the underlying Boost.Jam build engine is mature software, and the 
+    original Jam build engine has been
       widely used for many years.&nbsp; The Boost specific extensions are well
       on their way to becoming stable, and have begun to attract interest and
       use outside of Boost.</td>
@@ -38,10 +38,14 @@ Boost Libraries</h1>
 <a href="#Preliminaries">Preliminaries</a><br>
 <a href="#Building">Building Boost Libraries</a><br>
 <a href="#Moretools">More on using the tools</a><br>
-<a href="#Tools">Tools available</a></p>
+<a href="#Tools">Tools available</a><br>
+<a href="#Jam">Boost.Jam executable</a></p>
 <h2><a name="Introduction">Introduction</a></h2>
 <p>These instructions explain how to accomplish common tasks using <b>Boost.Build</b>,
-the Boost Build System.</p>
+the Boost Build System.&nbsp; The build system uses <a href="build_system.htm">
+Boost.Jam</a>, an extension of the
+<a href="http://www.perforce.com/jam/jam.html">Perforce Jam</a> portable <i>make</i> 
+replacement.</p>
 <p>For tasks not covered here, see the full <a href="build_system.htm">build
 system documentation</a>.</p>
 <p>Note that many Boost libraries are implemented entirely within their headers,
@@ -50,41 +54,11 @@ require building object libraries first include the Boost Python, Regular
 Expression, and Thread libraries.</p>
 <h2><a name="Preliminaries">Preliminaries</a></h2>
 <ul>
-  <li><a href="../../more/download.html">Download Boost</a>, and unpack the full
+  <li><a href="../../more/download.html">Download Boost</a>, and unpack the full 
     directory structure into some root directory.</li>
-
-    <p>
-    
-  <li>install the Boost Jam binary executable where it will be found when
-    invoked from the command line.</li><br>
-    
-  <ul>
-
-    <li>A Win32 pre-built executable is available <a href="jam.exe">here</a> (168K).
-
-    <li>For most Unix variants, you can build Boost Jam by simply invoking
-        <tt>make</tt> in the <tt>tools/build/jam_src</tt> subdirectory of your
-        boost installation.
-
-        <li><a href="http://public.perforce.com/public/jam/src/README">Build
-        Instructions</a> are the same as for &quot;<a
-        href="http://www.perforce.com/jam/jam.html">Classic Jam</a>&quot;, if
-        you need them.
-
-        <li>Your new Jam executable will be located in a newly-created
-        <tt>tools/build/jam_src/bin.</tt><i>platform</i> subdirectory.
-
-        <li>If you build Jam for a new platform using the same boost
-        installation, be sure to first remove all object files, executables, and
-        libraries created by the inital make in the <tt>jam_src</tt> directory.
-  </ul>
-
-  <p>
-
-</ul>
-<blockquote>
-</blockquote>
-<ul>
+  <li>Install the <a href="#Jam">Boost.Jam executable</a> if needed. <a href="#Jam">
+  Pre-builts</a> are available. Make sure it's in your path. (Note: Boost 
+  requires an enhanced version of Jam; the basic version won't work.)</li>
   <li>Set any environment variables required to run your compiler and related
     tools from the command line. (It might be a good idea to verify your command
     line compiler is working if you don't use it regularly.) If you don't want
@@ -96,22 +70,18 @@ Expression, and Thread libraries.</p>
 steps.&nbsp; The sample commands given will work for both UNIX and Windows.</p>
 <ul>
   <li>Change to the Boost root directory.&nbsp; (The directory you unpacked the
-    distribution into.&nbsp; Among others, it contain the file c++boost.gif,
-    subdirectories boost, libs, more, etc.)</li>
+    distribution into.&nbsp; Among others, it contains the file c++boost.gif,
+    and subdirectories boost, libs, more, etc.)</li>
   <blockquote>
     <p><code>chdir my_boost</code></p>
   </blockquote>
 
-  <p>
-
   <li>Build the Boost libraries for your <a href="#Tools">tools</a>. The example
     is for the GNU and Metrowerks compilers.</li>
   <blockquote>
     <p><code>jam&nbsp;-sBOOST_ROOT=.&nbsp;-sTOOLS=&quot;gcc&nbsp;metrowerks&quot;</code></p>
   </blockquote>
 
-  <p>
-
   <li>If you don't want to specify <code>BOOST_ROOT</code> on the command-line,
   you can instead set the <code>BOOST_ROOT</code> environment variable (an
   absolute path is recommended).
@@ -146,7 +116,7 @@ steps.&nbsp; The sample commands given will work for both UNIX and Windows.</p>
     <td>Borland command line compiler tools</td>
   </tr>
   <tr>
-    <td>como</td>
+    <td><code>como</code></td>
     <td>Comeau command line compiler tools</td>
   </tr>
   <tr>
@@ -158,7 +128,7 @@ steps.&nbsp; The sample commands given will work for both UNIX and Windows.</p>
     <td>GNU GCC command line compiler tools, using the STLport library</td>
   </tr>
   <tr>
-    <td>intel-win32</td>
+    <td><code>intel-win32</code></td>
     <td>Intel command line compiler tools, in the Win32 environment using the
       Microsoft library</td>
   </tr>
@@ -179,7 +149,7 @@ steps.&nbsp; The sample commands given will work for both UNIX and Windows.</p>
     <td>Microsoft Visual C++ command line compiler tools, using the STLport library</td>
   </tr>
   <tr>
-    <td>vacpp</td>
+    <td><code>vacpp</code></td>
     <td>IBM Visual Age C++ command line compiler tools</td>
   </tr>
 </table>
@@ -189,12 +159,67 @@ the compiler.</p>
 to the tools/build subdirectory, where xxxx is the name of the tool being
 added.&nbsp; If you write an additional toolset file, please submit it to Boost
 so others may benefit from your work.</p>
+<h2>Boost.<a name="Jam">Jam</a> executable</h2>
+<p>Pre-built Boost.Jam executables are available for the following platforms:</p>
+    
+  <ul>
+    <li><a href="http://boost.sourceforge.net/jam-executables/bin.aix/jam.gz">
+    IBM Aix</a> </li>
+    <li>
+    <a href="http://boost.sourceforge.net/jam-executables/bin.linuxx86/jam.gz">
+    Linux-x86</a> </li>
+    <li>
+    <a href="http://boost.sourceforge.net/jam-executables/boost-build.win.zip">
+    Microsoft Windows</a> (includes Boost.Build files and boost-build helper 
+    program).</li>
+    <li><a href="http://boost.sourceforge.net/jam-executables/bin.irix/jam.gz">
+    SGI Irix</a> </li>
+    <li>
+    <a href="http://boost.sourceforge.net/jam-executables/bin.solaris/jam.gz">
+    SUN Solaris</a> </li>
+</ul>
+<p>RedHat Linux RPM packages are available:</p>
+<ul>
+  <li>
+  <a href="http://boost.sourceforge.net/jam-executables/boost-jam-3.0-1.i386.rpm">
+  Boost.Jam rpm</a> </li>
+  <li>
+  <a href="http://boost.sourceforge.net/jam-executables/boost-build-1.0-1.i386.rpm">
+  Boost.Build rpm</a> </li>
+  <li>
+  <a href="http://boost.sourceforge.net/jam-executables/boost-jam-3.0-1.src.rpm">
+  Boost.Jam source rpm </a></li>
+  <li>
+  <a href="http://boost.sourceforge.net/jam-executables/boost-build-1.0-1.src.rpm">
+  Boost.Build source rpm</a></li>
+</ul>
+<p>The Boost.Jam source files are included in the Boost distribution, so you can build 
+the Boost.Jam executable yourself:</p>
+    
+  <ul>
+
+    <li>For most Unix variants, you can build Boost.Jam by simply invoking
+        <tt>make</tt> in the <tt>tools/build/jam_src</tt> subdirectory of your
+        boost installation.
+
+        <li><a href="http://public.perforce.com/public/jam/src/README">Build
+        Instructions</a> are the same as for &quot;<a
+        href="http://www.perforce.com/jam/jam.html">Classic Jam</a>&quot;, if
+        you need them.
+
+        <li>Your new Boost.Jam executable will be located in a newly-created
+        <tt>tools/build/jam_src/bin.</tt><i>platform</i> subdirectory.
+
+        <li>If you build Boost.Jam for a new platform using the same boost
+        installation, be sure to first remove all object files, executables, and
+        libraries created by the initial make in the <tt>jam_src</tt> directory.
+  </ul>
 <hr>
-<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->08 November, 2001<!--webbot bot="Timestamp" endspan i-checksum="39353" -->
+<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->28 November, 2001<!--webbot bot="Timestamp" i-checksum="39367" endspan -->
 </p>
 <p>© Copyright 2001 Beman Dawes</p>
 <p>&nbsp;</p>
 
 </body>
 
-</html>
+</html>
\ No newline at end of file

Read This - First! Boost.Build is not mature yet. Some features + First! Boost.Build is fairly new as yet. Some features are missing or incomplete. Instructions for accomplishing basic tasks (this page) are rudimentary. But enough functionality is working well to make using Boost.Build worthwhile. The important bits-and-pieces are all there - what's left is some of the relatively - minor glue to make the system smooth and easy to use. Don't expect - building a full Boost object library for any random compiler to work - yet. If there isn't a jam configuration file for your favorite - compiler, consider contributing one. Secondary tasks like copying - libraries to installation specific directories are also weak. Note - that the underlying Jam build engine is mature software, and has been + minor glue to make the system smooth and easy to use. Secondary tasks like + copying libraries to installation specific directories are weak. If + there isn't a configuration file (see Tools) available + for your favorite compiler, consider contributing one. Note + that the underlying Boost.Jam build engine is mature software, and the + original Jam build engine has been widely used for many years. The Boost specific extensions are well on their way to becoming stable, and have begun to attract interest and use outside of Boost.	Borland command line compiler tools
como	`como`	Comeau command line compiler tools
GNU GCC command line compiler tools, using the STLport library
intel-win32	`intel-win32`	Intel command line compiler tools, in the Win32 environment using the Microsoft library
Microsoft Visual C++ command line compiler tools, using the STLport library
vacpp	`vacpp`	IBM Visual Age C++ command line compiler tools