diff --git a/en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml b/en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml
index 88c84c0749..751ba6484a 100644
--- a/en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml
@@ -966,7 +966,7 @@ no adaptors present</screen>
     <title>Simple Directmedia Layer</title>
 
     <para>The Simple Directmedia Layer, SDL, was intended to be a
-      porting layers between Microsoft Windows, BeOS, and Unix,
+      porting layer between Microsoft Windows, BeOS, and Unix,
       allowing cross-platform applications to be developed which made
       efficient use of sound and graphics.  The SDL layer provides a
       low-level abstraction to the hardware which can sometimes be
@@ -1006,17 +1006,11 @@ no adaptors present</screen>
       and the capabilities of various applications are bound to
       diverge somewhat from the descriptions given here.</para>
 
-    <para>Firstly, it is important to know that most of the video
+    <para>Firstly, it is important to know that many of the video
       applications which run on FreeBSD were developed as Linux
-      applications, originating in the past year.  For this reason,
-      they are both very experimental and riddled with
-      Linux-isms which might prevent them from working at full
-      efficiency on FreeBSD.</para>
-
-    <para>By <quote>experimental</quote>, I mean that you should expect
-      re-encoders, players, and DVD decrypters to have some major
-      bugs, or interoperability problems with other programs.  Here is
-      a short list of the sort of things I mean:</para>
+      applications.  Many of these applications are still
+      beta-quality.  Some of the problems that you may encounter with
+      video packages on FreeBSD include :</para>
 
       <orderedlist>
 
@@ -1043,25 +1037,24 @@ no adaptors present</screen>
       </listitem>
 
       <listitem>
-        <para>An application always dumping core.</para>
+        <para>An application frequently dumps core.</para>
       </listitem>
 
       <listitem>
         <para>Documentation is not installed with the port and can be
-          found either on the web or under
-          <filename><replaceable>PORTPATH</replaceable>/work/
-          </filename>.</para>
+          found either on the web or under the port's 'work'
+          directory.</para>
       </listitem>
 
       </orderedlist>
 
-    <para>By <quote>Linux-isms</quote>, I mean that there are some
+    <para>Many of these applications may also exhibit
+      <quote>Linux-isms</quote>.  That is, there may be
       issues resulting from the way some standard libraries are
       implemented in the Linux distributions, or some features of the
       Linux kernel which have been assumed by the authors of the
-      applications, because that is where the authors are primarily
-      developing.  These issues may not be noticed and worked around
-      by the port maintainers which can lead to some problems like
+      applications.  These issues are not always noticed and worked around
+      by the port maintainers, which can lead to problems like
       these:</para>
        
       <orderedlist>
@@ -1095,7 +1088,8 @@ no adaptors present</screen>
         flexibility on Linux and other Unices.  The project was
         started when the team founder got fed up with bad playback
         performance on then available players.  Some would say that
-        interface has been sacrificed for streamlined design, but once
+        the graphical interface has been sacrificed for a streamlined
+        design.  However, once
         you get used to the command line options and the key-stroke
         controls, it works very well.</para>
 
@@ -1112,7 +1106,7 @@ no adaptors present</screen>
 	  another.  Therefore, it is important to build it from
 	  ports and not to use a binary package.  Additionally, a
 	  number of options can be specified in the <command>make</command>
-	  which echo at the start of the build.</para>
+	  command line, as described at the start of the build.</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/multimedia/mplayer</userinput>
 &prompt.root; <userinput>make</userinput>
@@ -1145,13 +1139,13 @@ You can enable XAnim DLL support by defining WITH_XANIM.
           <filename>Makefile</filename> can enable it.  It may be
           enabled by default in subsequent versions of the port.</para>
 
-        <para>The HTML documentation to <application>MPlayer</application> is very informative.
+        <para>The HTML documentation for <application>MPlayer</application> is very informative.
           If the reader finds the information on video hardware and
-          interfaces in the chapter lacking, the <application>MPlayer</application> documentation
-          is a very thorough alternative.  You should definitely take
-          the time to read the documentation of
-          <application>MPlayer</application>, if you are looking for
-          information about video support in Unix.</para>
+          interfaces in this chapter lacking, the <application>MPlayer</application> documentation
+          is a very thorough supplement.  You should definitely take
+          the time to read the <application>MPlayer</application>
+          documentation if you are looking for information about video
+          support in Unix.</para>
 
       </sect4>
 
@@ -1161,9 +1155,9 @@ You can enable XAnim DLL support by defining WITH_XANIM.
 	           <secondary>use</secondary></indexterm>
 
         <para>Any user of <application>MPlayer</application> must set up a
-          <filename>.mplayer</filename> subdirectory directory of her
+          <filename>.mplayer</filename> subdirectory of her
           home directory.  To create this necessary subdirectory,
-	  you can do the following:</para>
+	  you can type the following:</para>
 
 <screen>&prompt.user; <userinput>cd /usr/ports/multimedia/mplayer</userinput>
 &prompt.user; <userinput>make install-user</userinput></screen>