diff --git a/en_US.ISO8859-1/articles/releng/article.sgml b/en_US.ISO8859-1/articles/releng/article.sgml
index 3000fe4dc2..6b99bc650e 100644
--- a/en_US.ISO8859-1/articles/releng/article.sgml
+++ b/en_US.ISO8859-1/articles/releng/article.sgml
@@ -147,7 +147,7 @@
     process begins to ramp up 45 days before the anticipated release
     date when the release engineer sends an email to the development
     mailing lists to remind developers that they only have 15 days to
-    intergrate new changes before the code freeze.  During this time,
+    integrate new changes before the code freeze.  During this time,
     many developers perform what have become know as <quote>MFC
     sweeps</quote>.  <acronym>MFC</acronym> stands for <quote>Merge
     From CURRENT</quote> and it describes the process of merging a
@@ -157,7 +157,7 @@
   <sect2>
     <title>Code Review</title>
 
-    <para>Thiry days before the anticipated release, the source
+    <para>Thirty days before the anticipated release, the source
       repository enters a <quote>code slush</quote>.  During this
       time, all commits to the -STABLE branch must be approved by the
       release engineer (re@FreeBSD.org).  The kinds of changes that
@@ -260,7 +260,6 @@
         </textobject>
       </mediaobject>
 
-
     </sect3>
     
     <sect3>
@@ -337,11 +336,10 @@
         </listitem>
       </itemizedlist>
 
-      <para>Sysinstall should be updated to note the number of
-        available ports and the amount of disk space required for the
-        Ports Collection.  This information is currently kept in
-        <filename>src/release/sysinstall/dist.c</filename>.</para>
-
+      <para><application>Sysinstall</application> should be updated to note 
+        the number of available ports and the amount of disk space required
+	for the Ports Collection.  This information is currently kept in 
+	<filename>src/release/sysinstall/dist.c</filename>.</para>
     </sect3>
     
     <sect3>
@@ -404,7 +402,7 @@
       <quote><command>make
       <literal>buildworld</literal></command></quote>. The release
       target requires several variables be set properly to build a
-      release :</para>
+      release:</para>
     
     <itemizedlist>
       <listitem>
@@ -459,7 +457,8 @@
       
       <listitem>
         <para>Population of <filename>/etc</filename> and 
-        <filename>/dev</filename> in the chrooted environment.</para>
+        <filename>/dev</filename> in the chroot<emphasis>ed</emphasis> 
+        environment.</para>
       </listitem>
       
       <listitem>
@@ -615,11 +614,11 @@
       contents, and a <filename>filename.txt</filename> file that
       provides a manifest for the disc. This
       <emphasis>manifest</emphasis> can be created with a simple
-      command :</para>
+      command:</para>
     
     <screen>/stage/cdrom&prompt.root; <userinput>find . -type f | sed -e 's/\^.\///' | sort > filename.txt</userinput></screen>
     
-    <para>The specific requirements of each CD is outlined below.</para>
+    <para>The specific requirements of each CD are outlined below.</para>
     
     <sect3>
       <title>Disc 1</title>
@@ -662,7 +661,7 @@
     <sect3>
       <title>Discs 3 and 4</title>
 
-      <para>The remaining two discs contains additional software
+      <para>The remaining two discs contain additional software
         packages for FreeBSD. The packages should be clustered so that
         a package and all of its <emphasis>dependencies</emphasis> are
         included on the same disc.
@@ -695,7 +694,7 @@
       additional kernel modules or userland tools be added to the
       installation floppies.  The <quote>quick and dirty</quote> way
       to accomplish this would be to modify the staging directory of
-      an existing <quote>make release</quote> build hierarchy :</para>
+      an existing <quote>make release</quote> build hierarchy:</para>
     
     <itemizedlist>
       <listitem>
@@ -705,7 +704,7 @@
       
       <listitem>
         <para><command>rm 
-        <literal>${CHROOTDIR}/usr/obj/usr/src/\release/release.[48]</literal>
+        <literal>${CHROOTDIR}/usr/obj/usr/src/release/release.[48]</literal>
         </command></para>
       </listitem>
       
@@ -726,7 +725,7 @@
     </itemizedlist>
     
     <para>New release floppies will be located in
-      <filename>${CHROOTDIR}/R/ stage/floppies</filename>.</para>
+      <filename>${CHROOTDIR}/R/stage/floppies</filename>.</para>
     
     <para>Alternatively, the
       <quote><filename>boot.flp</filename></quote> make
@@ -792,14 +791,14 @@
   <itemizedlist>
     <listitem>
       <para><emphasis>Parallelism</emphasis> - Certain portions of the
-        release build are actually <quote>embarrasingly
+        release build are actually <quote>embarrassingly
         parallel</quote>.  Most of the tasks are very I/O intensive,
         so multiple high-speed disk drives is actually important that
         multiple processors in speeding up the <quote>make
-        release</quote> process.  if multiple disks are used for
+        release</quote> process.  If multiple disks are used for
         different hierarchies in the <emphasis>chroot</emphasis>
         environment, then the CVS checkout of the ports and doc trees
-        can be happening simulatneously to the <quote>make
+        can be happening simultaneously to the <quote>make
         <literal>world</literal></quote> on another disk.  Using a
         <acronym>RAID</acronym> solution (hardware and software) can
         significantly decrease overall build time.</para>