--- article.sgml	Wed Jul 24 12:33:57 2002
+++ article.sgml	Wed Jul 24 13:33:05 2002
@@ -134,7 +134,7 @@ 
     <para>First, all embedded FreeBSD systems that use flash memory as system
       disk will be interested in memory disks and memory filesystems.  Because
       of the limited number of writes that can be done to flash memory, the
-      disk and the filesystems no the disk will most likely be mounted
+      disk and the filesystems on the disk will most likely be mounted
       read-only.  In this environment, filesystems such as
       <filename>/tmp</filename> and <filename>/var</filename> are mounted as
       memory filesystems to allow the system to create logs and update
@@ -204,7 +204,7 @@ 
       read-only.  Remember that in <xref linkend="intro"> we detailed the
       limitations of flash memory - specifically the limited write capability.
       The importance of not mounting filesystems on flash media read-write,
-      and the importance of not using a swap file cannot be overstated.  A
+      and the importance of not using a swap file, cannot be overstated.  A
       swap file on a busy system can burn through a piece of flash media in
       less than one year. Heavy logging or temporary file creation and
       destruction can do the same.  Therefore, in addition to removing the
@@ -290,7 +290,7 @@ 
 	  by pressing the <keycap>w</keycap> key (this is a hidden option on
 	  this screen).  When presented with a menu to choose a boot manager,
 	  take care to select <literal>None</literal> if you are using an
-	  M-Systems Disk-On-Chip.  If you are using a ATA compatible compact
+	  M-Systems Disk-On-Chip.  If you are using an ATA compatible compact
 	  flash card, you should choose the FreeBSD Boot Manager.  Now press
 	  the <keycap>q</keycap> key to quit the partition menu.  You will be
 	  shown the boot manager menu once more - repeat the choice you made
@@ -333,8 +333,8 @@ 
 	  of the file from <literal>ESDI</literal> to
 	  <literal>DOC2K</literal>.  Next, regardless of whether you are using
 	  Disk-On-Chip or ATA compatible compact flash media, you need to add
-	  an a: line at the end of the file.  This <literal>a:</literal> line
-	  should look like:</para>
+	  an <literal>a:</literal> line at the end of the file.  This
+	  <literal>a:</literal> line should look like:</para>
 
 	<programlisting>a:      <replaceable>123456</replaceable>  0       4.2BSD  0       0</programlisting>
 
@@ -455,7 +455,7 @@ 
 
     <procedure>
       <step>
-	<para>Obtain an existing kern.flp image file</para>
+	<para>Obtain an existing <filename>kern.flp</filename> image file</para>
       </step>
 
       <step>
@@ -553,7 +553,7 @@ 
 
       <para>To make it possible to enter a ports directory and successfully
 	run <command>make install</command>, it is necessary for the file
-	<filename>/var/db/port.mkversion</filename> to exist, and that it have
+	<filename>/var/db/port.mkversion</filename> to exist, and that it has
 	a correct date in it.  Further, we must create a packages directory on
 	a non-memory filesystem that will keep track of our packages across
 	reboots. Because it is necessary to mount your filesystems as
@@ -599,8 +599,8 @@ 
 
       <para>Apache keeps pid files and logs in
 	<filename><replaceable>apache_install</replaceable>/logs</filename>.
-	Since this directory no doubt exists on a read-only filesystem, this
-	will not work.  It is necessary to add a new directory to the
+	Since this directory, without a doubt, exists on a read-only filesystem,
+	this will not work.  It is necessary to add a new directory to the
 	<filename>/etc/rc.diskless2</filename> list of directories to create
 	in <filename>/var</filename>, to link
 	<filename><replaceable>apache_install</replaceable>/logs</filename> to