o Reword a bit in a couple of places, to avoid using 'necessary' and

'need' twice in the same sentence.

o   Replace <literal> tags with <emphasis> for `tag', `port' and
    `package' (they are really used as FreeBSD-specific terms, not as
    <literal> text here).

o   Expand a paragraph with inline URIs, which result in pretty awkward
    line breaks in PDF/PS output, to a <variablelist>.  This separates
    the URIs from the running text, and looks slightly prettier in print
    output.

en_US.ISO8859-1/articles/version-guide/article.sgml

@@ -65,24 +65,24 @@
       <itemizedlist>
 	<listitem>
 	  <para>The goal of a major release is to introduce a set of new
-	    features.  Where necessary, it may be necessary to break
-	    compatibility with previous major releases in order to advance
-	    the state of &os;, or, occasionally, to drop features that
-	    it is no longer feasible to support.</para>
+	    features.  Inevitably, as new features are added to &os;, or as
+	    older features are no longer useful or are dropped, it is
+	    sometimes necessary to break compatibility with previous major
+	    releases.</para>
 	</listitem>
 
 	<listitem>
 	  <para>The goal of a minor release is primarily to fix bugs and
-	    improve performance and stability.  Keeping compatibility
+	    improve performance and stability.  Keeping both source-level and binary compatibility
 	    from one minor release to another is a priority.  On occasion,
 	    new features may be added to a minor release when it is
 	    believed that these other goals will not be compromised.</para>
 	</listitem>
       </itemizedlist>
 
-      <para>However, keep in mind that a <literal>release version</literal>
+      <para>However, keep in mind that a <quote>release version</quote>
 	is merely a snapshot of the source tree at a particular point in
-	time which is given a particular name (or <literal>tag</literal>).
+	time which is given a particular name (or <emphasis>tag</emphasis>).
 	(For instance, the tag that Release Engineering assigned for the
 	5.4 release was <literal>RELENG_5_4_0_RELEASE</literal>.) Development
 	always continues on what is known as the <literal>HEAD</literal>
@@ -138,9 +138,9 @@
 	programs to be installed (termed the <firstterm>Ports
 	Collection</firstterm>).  Applications may be installed
 	either from source, if its licensing terms allow such
-	redistribution (these are termed <literal>ports</literal>),
-	or as compiled binaries if allowed (these are termed
-	<literal>packages</literal>).</para>
+	redistribution (these are called <emphasis>ports</emphasis>),
+	or as compiled binaries if allowed (these are called
+	<emphasis>packages</emphasis>).</para>
     </sect2>
   </sect1>
 
@@ -303,13 +303,27 @@
       resources but primarily due to the amount of volunteer effort
       that is available.</para>
 
-    <para>Interested readers should also see the current
-      <ulink url="&url.base;/releng/index.html#schedule">Release
-      Engineering Schedule</ulink> and
-      <ulink url="&url.base;/security/security.html#supported-branches">Security
-      Branch Schedule</ulink>.  Both documents also go into much
-      greater depth about the background and rationale behind
-      these decisions.</para>
+    <para>Interested readers should also see:</para>
+
+    <variablelist>
+      <varlistentry>
+        <term><ulink url="&url.base;/releng/index.html#schedule"></ulink></term>
+        <listitem>
+	  <para>The Release Engineering Schedule</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term><ulink url="&url.base;/security/security.html#supported-branches"></ulink></term>
+	<listitem>
+	  <para>The Security Branch Schedule</para>
+	</listitem>
+      </varlistentry>
+    </variablelist>
+
+    <para>These documents go into much greater depth about the background and
+      rationale behind the decisions regarding the supported branches and the
+      lifetime of each branch.</para>
   </sect1>
 
   <sect1 id="decision-points">
@@ -350,7 +364,7 @@
 
     <itemizedlist>
       <listitem>
-	<para>If you have a short-term need, need the highest degree of
+	<para>If you have a short-term need, would benefit from the highest degree of
 	  stability currently available, and are not able to devote many
 	  resources to upgrading, then you will probably want to install
 	  the latest <literal>STABLE</literal> minor release and remain