From 74d1478c6e63f3ea5e4ec4ba37e1dd0ba3cdc733 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 18 Apr 2000 23:43:24 +0000
Subject: [PATCH] Rename binary object to binary format.

---
 doc/src/sgml/ref/copy.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index d8c48f6229..fac440bf9f 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.14 2000/04/18 23:21:04 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.15 2000/04/18 23:43:24 momjian Exp $
 Postgres documentation
 -->
 
@@ -48,7 +48,7 @@ COPY [ BINARY ] <replaceable class="parameter">table</replaceable> [ WITH OIDS ]
       <listitem>
        <para>
 	Changes the behavior of field formatting, forcing all data to be
-	stored or read as binary objects rather than as text.
+	stored or read in binary format rather than as text.
        </para>
       </listitem>
      </varlistentry>
@@ -193,7 +193,7 @@ ERROR: <replaceable>reason</replaceable>
    </title>
    <para>
     The BINARY keyword will force all data to be
-    stored/read as binary objects rather than as text.  It is
+    stored/read as binary format rather than as text.  It is
     somewhat faster than the normal copy command, but is not
     generally portable, and the files generated are somewhat larger,
     although this factor is highly dependent on the data itself.  By