Put spaces after "RFC".

doc/src/sgml/client-auth.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.105 2007/12/29 04:15:38 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.106 2008/01/05 13:17:00 petere Exp $ -->
 
 <chapter id="client-authentication">
  <title>Client Authentication</title>
@@ -666,10 +666,10 @@ local   db1,db2,@demodbs  all                         md5
 
    <para>
     <productname>GSSAPI</productname> is an industry-standard protocol
-    for secure authentication defined in RFC2743. 
+    for secure authentication defined in RFC 2743. 
     <productname>PostgreSQL</productname> supports
     <productname>GSSAPI</productname> with <productname>Kerberos</productname>
-    authentication according to RFC1964. <productname>GSSAPI</productname>
+    authentication according to RFC 1964. <productname>GSSAPI</productname>
     provides automatic authentication (single sign-on) for systems
     that support it. The authentication itself is secure, but the
     data sent over the connection will be in clear unless
@@ -851,7 +851,7 @@ local   db1,db2,@demodbs  all                         md5
 
    <para>
     The <quote>Identification Protocol</quote> is described in
-    <citetitle>RFC 1413</citetitle>. Virtually every Unix-like
+    RFC 1413. Virtually every Unix-like
     operating system ships with an ident server that listens on TCP
     port 113 by default. The basic functionality of an ident server
     is to answer questions like <quote>What user initiated the

doc/src/sgml/pgcrypto.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/pgcrypto.sgml,v 1.3 2007/12/16 23:00:42 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/pgcrypto.sgml,v 1.4 2008/01/05 13:17:00 petere Exp $ -->
 
 <sect1 id="pgcrypto">
  <title>pgcrypto</title>
@@ -390,7 +390,7 @@
   <title>PGP encryption functions</title>
 
   <para>
-   The functions here implement the encryption part of the OpenPGP (RFC2440)
+   The functions here implement the encryption part of the OpenPGP (RFC 2440)
    standard.  Supported are both symmetric-key and public-key encryption.
   </para>
 
@@ -689,7 +689,7 @@
    <para>
     Whether to convert <literal>\n</literal> into <literal>\r\n</literal> when
     encrypting and <literal>\r\n</literal> to <literal>\n</literal> when
-    decrypting.  RFC2440 specifies that text data should be stored using
+    decrypting.  RFC 2440 specifies that text data should be stored using
     <literal>\r\n</literal> line-feeds.  Use this to get fully RFC-compliant
     behavior.
    </para>
@@ -706,7 +706,7 @@
    <para>
     Do not protect data with SHA-1.  The only good reason to use this
     option is to achieve compatibility with ancient PGP products, predating
-    the addition of SHA-1 protected packets to RFC2440.
+    the addition of SHA-1 protected packets to RFC 2440.
     Recent gnupg.org and pgp.com software supports it fine.
    </para>
    <programlisting>
@@ -1179,7 +1179,7 @@
      <para>
       <ulink url="http://www.imc.org/draft-ietf-openpgp-rfc2440bis"></ulink>
      </para>
-     <para>New version of RFC2440.</para>
+     <para>New version of RFC 2440.</para>
     </listitem>
     <listitem>
      <para><ulink url="http://www.ietf.org/rfc/rfc1321.txt"></ulink></para>