A bit more wordsmithing on the COPY CSV NULL business.

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 79ed7c204e3e0710729dcfe02afee73a41506b2c..b0e05188381dfe8f5e5b51859fc2019d78e22ec7 100644 (file)
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -1,5 +1,5 @@
 
 
@@ -183,8 +183,8 @@ COPY { tablename [ ( 
     
      
       The string that represents a null value. The default is
-      \N (backslash-N) in text mode, and a empty
-      value with no quotes in CSV mode. You might prefer an
+      \N (backslash-N) in text mode, and an unquoted empty
+      string in CSV mode. You might prefer an
       empty string even in text mode for cases where you don't want to
       distinguish nulls from empty strings.
      
@@ -249,8 +249,7 @@ COPY { tablename [ ( 
       In CSV COPY TO mode, forces quoting to be
       used for all non-NULL values in each specified column.
       NULL output is never quoted. If * is specified,
-      non-NULL values for all columns of the table will be
-      quoted.
+      non-NULL values will be quoted in all columns.
      
     
    
@@ -550,11 +549,11 @@ COPY count
    
     The CSV format has no standard way to distinguish a
     NULL value from an empty string.
-    PostgreSQL's COPY handles this by
-    quoting. A NULL is output as the NULL
-    parameter and is not quoted, while a non-NULL value matching the
-    the NULL parameter string is quoted. Therefore, using the default
-    settings, a NULL is written as an unquoted empty
+    PostgreSQL's COPY handles this by quoting.
+    A NULL is output as the NULL parameter string
+    and is not quoted, while a non-NULL value matching the
+    NULL parameter string is quoted.  For example, with the
+    default settings, a NULL is written as an unquoted empty
     string, while an empty string data value is written with double quotes
     (""). Reading values follows similar rules. You can
     use FORCE NOT NULL to prevent NULL input