diff --git a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
index bb2f641176..e9748478a8 100644
--- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.76 2001/07/17 23:33:26 chern Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.77 2001/07/19 23:18:06 chern Exp $
 -->
 
 <chapter id="cutting-edge">
@@ -264,26 +264,31 @@ subscribe cvs-all</programlisting>
 	<title>What is &os.stable;?</title>
 	<indexterm><primary>-STABLE</primary></indexterm>
 
-	<para>&os.stable; is our development branch for a more low-key
-	  and conservative set of changes intended for our next mainstream
-	  release.  Any changes to this branch will have debuted in
-	  &os.current; first, helping to reduce (but not eliminate) the chance
-	  that the changes will cause problems.</para>
+	<para>&os.stable; is our development branch from which major releases
+	  are made.  Changes go into this branch at a different pace, and
+	  with the general assumption that they've first gone into
+	  &os.current; first for testing.  This is <emphasis>still</emphasis>
+	  a development branch, however, and this means that at any given time,
+	  the sources for &os.stable; may or may not be suitable for any
+	  particular purpose.  It is simply another engineering development
+	  track, not a resource for end-users.</para>
       </sect3>
 
       <sect3>
 	<title>Who needs &os.stable;?</title>
 
-	<para>If you are interested in tracking the FreeBSD development
-	  process, and you want early access to the features that will appear
-	  in the next <quote>point</quote> release of FreeBSD then you should
+	<para>If you are interested in tracking or contributing to the
+          FreeBSD development process, especially as it relates to the
+	  next <quote>point</quote> release of FreeBSD, then you should
 	  consider following &os.stable;.</para>
 
-	<para>Tracking &os.stable; also gives you easy access to security
-	  fixes for FreeBSD as they are released.  However, you do not
-	  <emphasis>need</emphasis> to track &os.stable; to do this, as every
-	  security advisory for FreeBSD explains how to fix the problem for
-	  the releases it affects.</para>
+	<para>While it is true that security fixes also go into the
+	  &os.stable; branch, you do not <emphasis>need</emphasis> to
+	  track &os.stable; to do this. Every security advisory for
+	  FreeBSD explains how to fix the problem for the releases it
+	  affects, and tracking an entire development branch just
+	  for security reasons is likely to bring in a lot of unwanted
+	  changes as well.</para>
 
 	<para>Although we endeavor to ensure that the &os.stable; branch
 	  compiles and runs at all times, this cannot be guaranteed.  In