Update iconv wording, per Peter.

doc/src/sgml/release.sgml

@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.406 2005/12/06 20:25:42 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.407 2005/12/06 21:00:53 momjian Exp $
 
 Typical markup:
 
@@ -528,16 +528,16 @@ psql -t -f fixseq.sql db1 | psql -e db1
 
      <listitem>
       <para>
-       Some users are having problems loading <literal>UTF8</> data into
+       Some users are having problems loading UTF-8 data into
-       8.1.X.  This is because previous versions allowed invalid <literal>UTF8</>
+       8.1.X.  This is because previous versions allowed invalid UTF-8 byte
        sequences to be entered into the database, and this release
-       properly accepts only valid <literal>UTF8</> sequences.  One
+       properly accepts only valid UTF-8 sequences.  One
-       way to correct a dumpfile is to use <command>iconv -c -f UTF-8 -t UTF-8
+       way to correct a dumpfile is to run the command <command>iconv -c -f UTF-8 -t UTF-8
        -o cleanfile.sql dumpfile.sql</>.  The <literal>-c</> option removes
        invalid character sequences.  A diff of the two files will show the
-       sequences that are invalid.  <command>iconv</> reads the entire input 
+       sequences that are invalid.  <command>iconv</> reads the entire input
-       file into memory so it might be necessary to <command>split</> the dump 
+       file into memory so it might be necessary to use <command>split</>
-       into multiple smaller files for processing.
+       to break up the dump into multiple smaller files for processing.
       </para>
      </listitem>