Put spaces after "RFC".

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 20eb31fbfc3238568179dd8a8075c6d045bf5424..e5f56e55d94c95e1fc5c512e5278c20fea224b51 100644 (file)
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Client Authentication
@@ -666,10 +666,10 @@ local   db1,db2,@demodbs  all                         md5
 
    
     GSSAPI is an industry-standard protocol
-    for secure authentication defined in RFC2743. 
+    for secure authentication defined in RFC 2743. 
     PostgreSQL supports
     GSSAPI with Kerberos
-    authentication according to RFC1964. GSSAPI
+    authentication according to RFC 1964. GSSAPI
     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
 
    
     The Identification Protocol is described in
-    RFC 1413. 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 What user initiated the

diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml
index f7fe07c525c53bb55896713740031f8b3fbafade..892dfdca2b6a56c56a2e5726293233cfeadb6f65 100644 (file)
--- a/doc/src/sgml/pgcrypto.sgml
+++ b/doc/src/sgml/pgcrypto.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  pgcrypto
@@ -390,7 +390,7 @@
   PGP encryption functions
 
   
-   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.
   
 
@@ -689,7 +689,7 @@
    
     Whether to convert \n into \r\n when
     encrypting and \r\n to \n when
-    decrypting.  RFC2440 specifies that text data should be stored using
+    decrypting.  RFC 2440 specifies that text data should be stored using
     \r\n line-feeds.  Use this to get fully RFC-compliant
     behavior.
    
@@ -706,7 +706,7 @@
    
     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.
    
    
@@ -1179,7 +1179,7 @@
      
       
      
-     New version of RFC2440.
+     New version of RFC 2440.