Expunge "UNIX" in favor of "Unix".

A few other changes, but I forget what :(

doc/src/sgml/advanced.sgml

@@ -282,7 +282,7 @@ SELECT name, population
 
     <note>
      <para>
-      On UNIX systems, this is always  midnight,  January  1, 1970 GMT.
+      On Unix systems, this is always  midnight,  January  1, 1970 GMT.
      </para>
     </note>
    </para>

doc/src/sgml/arch-dev.sgml

@@ -174,7 +174,7 @@
       <para>
        The <firstterm>parser</firstterm> defined in
        <filename>gram.y</filename> and <filename>scan.l</filename> is
-       built using the UNIX tools <application>yacc</application>
+       built using the Unix tools <application>yacc</application>
        and <application>lex</application>.
       </para>
      </listitem>
@@ -194,7 +194,7 @@
      The parser has to check the query string (which arrives as
      plain ASCII text) for valid syntax. If the syntax is correct a
      <firstterm>parse tree</firstterm> is built up and handed back otherwise an error is
-     returned. For the implementation the well known UNIX
+     returned. For the implementation the well known Unix
      tools <application>lex</application> and <application>yacc</application>
      are used.
     </para>

doc/src/sgml/arch-pg.sgml

@@ -11,7 +11,7 @@
      somewhat clearer.
      In  database  jargon,  <ProductName>Postgres</ProductName> uses a simple "process  
      per-user" client/server model.  A <ProductName>Postgres</ProductName> session 
-     consists of the following cooperating UNIX processes (programs):
+     consists of the following cooperating Unix processes (programs):
 
 <ItemizedList>
 <ListItem>
@@ -75,7 +75,7 @@ Note that the <ProductName>Postgres</ProductName> superuser does not
 have  to  be  a special user (e.g., a user named 
 "postgres"), although many systems are installed that way.
 Furthermore,  the  <ProductName>Postgres</ProductName>  superuser should
-     definitely  not  be the UNIX superuser, "root"!  In any
+     definitely  not  be the Unix superuser, "root"!  In any
      case, all files relating to a database should belong to
      this <ProductName>Postgres</ProductName> superuser.
 </Para>

doc/src/sgml/arch.sgml

@@ -11,7 +11,7 @@
      somewhat clearer.
      In  database  jargon,  <ProductName>Postgres</ProductName> uses a simple "process  
      per-user" client/server model.  A <ProductName>Postgres</ProductName> session 
-     consists of the following cooperating UNIX processes (programs):
+     consists of the following cooperating Unix processes (programs):
 </Para>
 
 <ItemizedList>
@@ -80,7 +80,7 @@
      have  to  be  a special user (e.g., a user named 
      "postgres").  Furthermore,  the  <ProductName>Postgres</ProductName>  superuser  
      should
-     definitely  not  be the UNIX superuser ("root")!  In any
+     definitely  not  be the Unix superuser ("root")!  In any
      case, all files relating to a database should belong to
      this <ProductName>Postgres</ProductName> superuser.
 </Para>

doc/src/sgml/docguide.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.18 1999/07/06 17:19:41 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.19 1999/10/04 15:18:53 thomas Exp $
 Documentation Guide
 Thomas Lockhart
 
@@ -1334,7 +1334,7 @@ but it is almost certainly a good candidate for use.
 <itemizedlist>
 <listitem><para>A working installation of GCC 2.7.2</para></listitem>
 <listitem><para>A working installation of Emacs 19.19 or later</para></listitem>
-<listitem><para>An unzip program for UNIX to unpack things</para></listitem>
+<listitem><para>An unzip program for Unix to unpack things</para></listitem>
 </itemizedlist>
 
 </para>

doc/src/sgml/environ.sgml

@@ -42,7 +42,7 @@ $ export PATH
      variable</Quote>  or  <Quote>setting an environment variable</Quote> throughout
      this document.  If you did  not  fully  understand  the
      last  paragraph  on  modifying  your  search  path, you
-     should consult the UNIX manual pages that describe your
+     should consult the Unix manual pages that describe your
      shell before going any further.
 </Para>
 

doc/src/sgml/intro-pg.sgml

@@ -34,7 +34,7 @@
   </para>
 
   <para>
-   We assume proficiency with UNIX and C programming.
+   We assume proficiency with Unix and C programming.
   </para>
 
    &info;

doc/src/sgml/layout.sgml

@@ -41,7 +41,7 @@ export PATH
      variable"  or  "setting an environment variable" throughout
      this document.  If you did  not  fully  understand  the
      last  paragraph  on  modifying  your  search  path, you
-     should consult the UNIX manual pages that describe your
+     should consult the Unix manual pages that describe your
      shell before going any further.
 </Para>
 

doc/src/sgml/legal.sgml

@@ -32,7 +32,7 @@
  </para>
 
  <para>
-  <acronym>UNIX</acronym> is a trademark of X/Open, Ltd.  Sun4,  SPARC,  SunOS
+  <acronym>Unix</acronym> is a trademark of X/Open, Ltd.  Sun4,  SPARC,  SunOS
   and  Solaris  are trademarks of Sun Microsystems, Inc.  DEC,
   DECstation, Alpha AXP and ULTRIX are trademarks  of  Digital
   Equipment   Corp.   PA-RISC  and  HP-UX  are  trademarks  of

doc/src/sgml/manage-ag.sgml

@@ -116,7 +116,7 @@ You are currently connected to the database: <replaceable>dbname</replaceable>
 <replaceable>dbname</replaceable>=> \i <replaceable class="parameter">filename</replaceable>
     </programlisting>
 
-    To get out of <application>psql</application> and return to UNIX, type
+    To get out of <application>psql</application> and return to Unix, type
 
     <programlisting>
 <replaceable>dbname</replaceable>=&gt; \q
@@ -140,13 +140,13 @@ You are currently connected to the database: <replaceable>dbname</replaceable>
 
    <para>
     If you are the database administrator for the  database
-    mydb,  you can destroy it using the following UNIX command:
+    mydb,  you can destroy it using the following Unix command:
 
     <programlisting>
 % destroydb <replaceable class="parameter">dbname</replaceable>
     </programlisting>
 
-    This action physically removes all of  the  UNIX  files
+    This action physically removes all of  the  Unix  files
     associated  with  the database and cannot be undone, so
     this should only be done with a  great  deal  of  forethought.
    </para>

doc/src/sgml/manage.sgml

@@ -243,7 +243,7 @@ mydb=> \g
 mydb=> \i fileName
 </ProgramListing>
 
-     To get out of <Application>psql</Application> and return to UNIX, type
+     To get out of <Application>psql</Application> and return to Unix, type
 <ProgramListing>
 mydb=> \q
 </ProgramListing>
@@ -281,11 +281,11 @@ TBD
 
 <Para>
      If you are the database administrator for the  database
-     <Database>mydb</Database>,  you can destroy it using the following UNIX command:
+     <Database>mydb</Database>,  you can destroy it using the following Unix command:
 <ProgramListing>
 % destroydb mydb
 </ProgramListing>
-     This action physically removes all of  the  UNIX  files
+     This action physically removes all of  the  Unix  files
      associated  with  the database and cannot be undone, so
      this should only be done with a  great  deal  of  forethought.
 </Para>

doc/src/sgml/security.sgml

@@ -138,8 +138,8 @@
     </para>
 
     <para>
-     Connections from clients can be made using UNIX domain sockets or Internet
-     domain sockets (ie. TCP/IP).  Connections made using UNIX domain sockets
+     Connections from clients can be made using Unix domain sockets or Internet
+     domain sockets (ie. TCP/IP).  Connections made using Unix domain sockets
      are controlled using records of the following format:
 
      <synopsis>
@@ -158,7 +158,7 @@ local <replaceable>database</replaceable> <replaceable>authentication method</re
       <member>
        <replaceable>authentication method</replaceable>
        specifies the method a user must use to authenticate themselves when
-       connecting to that database using UNIX domain sockets.  The different methods
+       connecting to that database using Unix domain sockets.  The different methods
        are described below.
       </member>
      </simplelist>
@@ -199,7 +199,7 @@ host <replaceable>database</replaceable> <replaceable>TCP/IP address</replaceabl
      <title>Authentication Methods</title>
 
      <para>
-      The following authentication methods are supported for both UNIX and TCP/IP
+      The following authentication methods are supported for both Unix and TCP/IP
       domain sockets:
 
       <variablelist>
@@ -299,7 +299,7 @@ host <replaceable>database</replaceable> <replaceable>TCP/IP address</replaceabl
 
      <para>
       <programlisting>
-# Trust any connection via UNIX domain sockets.
+# Trust any connection via Unix domain sockets.
 local	trust
 # Trust any connection via TCP/IP from this machine.
 host	all	127.0.0.1	255.255.255.255		trust

doc/src/sgml/start.sgml

@@ -13,7 +13,7 @@ How to begin work with <ProductName>Postgres</ProductName> for a new user.
      the site database administrator.  This site administrator 
      is the person who installed the  software,  created
      the  database  directories  and  started the <Application>postmaster</Application>
-     process.  This person does not  have  to  be  the  UNIX
+     process.  This person does not  have  to  be  the  Unix
      superuser (<Quote>root</Quote>)
  or the computer system administrator; a person can install and use
 <ProductName>Postgres</ProductName> without any special accounts or privileges.
@@ -28,7 +28,7 @@ to this guide when the installation is complete.
 <Para>
      Throughout this manual, any examples  that  begin  with
      the  character  <Quote>%</Quote> are commands that should be typed
-     at the UNIX shell prompt.  Examples that begin with the
+     at the Unix shell prompt.  Examples that begin with the
      character <Quote>*</Quote> are commands in the Postgres query 
      language, Postgres <Acronym>SQL</Acronym>.
 </Para>
@@ -77,7 +77,7 @@ of a client application is the interactive monitor <Application>psql</Applicatio
      variable</Quote>  or  <Quote>setting an environment variable</Quote> throughout
      this document.  If you did  not  fully  understand  the
      last  paragraph  on  modifying  your  search  path, you
-     should consult the UNIX manual pages that describe your
+     should consult the Unix manual pages that describe your
      shell before going any further.
 </Para>
 
@@ -282,7 +282,7 @@ mydb=> \g
 mydb=> \i fileName
 </ProgramListing>
 
-     To get out of <Application>psql</Application> and return to UNIX, type
+     To get out of <Application>psql</Application> and return to Unix, type
 <ProgramListing>
 mydb=> \q
 </ProgramListing>
@@ -303,11 +303,11 @@ mydb=> \q
 
 <Para>
      If you are the database administrator for the  database
-     <Database>mydb</Database>,  you can destroy it using the following UNIX command:
+     <Database>mydb</Database>,  you can destroy it using the following Unix command:
 <ProgramListing>
 % destroydb mydb
 </ProgramListing>
-     This action physically removes all of  the  UNIX  files
+     This action physically removes all of  the  Unix  files
      associated  with  the database and cannot be undone, so
      this should only be done with a  great  deal  of  forethought.
 </Para>

doc/src/sgml/xfunc.sgml

@@ -116,7 +116,7 @@ select function hobbies (EMP) returns set of HOBBIES
 
     <para>
      The simplest possible <acronym>SQL</acronym> function has no arguments and
-     simply returns a base type, such as <acronym>int4</acronym>:
+     simply returns a base type, such as <literal>int4</literal>:
      
      <programlisting>
     CREATE FUNCTION one() RETURNS int4
@@ -291,10 +291,11 @@ WARN::function declared to return type EMP does not retrieve (EMP.*)
     <para>
      Any collection of commands in the  <acronym>SQL</acronym>  query  
      language can be packaged together and defined as a function.
-     The commands can include updates (i.e., <acronym>insert</acronym>,  
-     <acronym>update</acronym> and <acronym>delete</acronym>) as well 
-     as <acronym>select</acronym> queries.  However, the final command 
-     must be a <acronym>select</acronym> that returns whatever is
+     The commands can include updates (i.e.,
+     <command>INSERT</command>, <command>UPDATE</command>, and
+     <command>DELETE</command>) as well
+     as <command>SELECT</command> queries.  However, the final command 
+     must be a <command>SELECT</command> that returns whatever is
      specified as the function's returntype.
 
      <programlisting>
@@ -392,7 +393,7 @@ WARN::function declared to return type EMP does not retrieve (EMP.*)
     code file for the function, bracketed by quotation marks.  If a
     link symbol is used in the AS clause, the link symbol should also be
     bracketed by single quotation marks, and should be exactly the
-    same as the name of the function in the C source code. On UNIX systems
+    same as the name of the function in the C source code. On Unix systems
     the command <command>nm</command> will print all of the link
     symbols in a dynamically loadable object.
     (<productname>Postgres</productname> will not compile a function
@@ -608,12 +609,12 @@ WARN::function declared to return type EMP does not retrieve (EMP.*)
      only passes integer types by value.  You should be careful 
      to define your types such that  they  will  be  the  same  
      size (in bytes) on all architectures.  For example, the 
-     <acronym>long</acronym> type is dangerous because  it  
+     <literal>long</literal> type is dangerous because  it  
      is 4 bytes on some machines and 8 bytes on others, whereas 
-     <acronym>int</acronym>  type  is  4  bytes  on  most  
-     <acronym>UNIX</acronym> machines  (though  not  on most 
+     <literal>int</literal>  type  is  4  bytes  on  most  
+     Unix machines  (though  not  on most 
      personal computers).  A reasonable implementation of  
-     the  <acronym>int4</acronym>  type  on  <acronym>UNIX</acronym>
+     the  <literal>int4</literal>  type  on  Unix
      machines might be:
      
      <programlisting>
@@ -779,7 +780,7 @@ memmove(destination-&gt;data, buffer, 40);
      a  procedural interface for accessing fields of composite types  
      from C.  As <productname>Postgres</productname> processes 
      a set of instances, each instance will be passed into your 
-     function as an  opaque  structure of type <acronym>TUPLE</acronym>.
+     function as an  opaque  structure of type <literal>TUPLE</literal>.
      Suppose we want to write a function to answer the query
 
      <programlisting>
@@ -809,16 +810,16 @@ memmove(destination-&gt;data, buffer, 40);
     </para>
 
     <para>
-     <acronym>GetAttributeByName</acronym> is the 
+     <function>GetAttributeByName</function> is the 
      <productname>Postgres</productname> system function that
      returns attributes out of the current instance.  It has
      three arguments: the argument of type TUPLE passed into
      the  function, the name of the desired attribute, and a
      return parameter that describes whether  the  attribute
-     is  null.   <acronym>GetAttributeByName</acronym> will 
+     is  null.   <function>GetAttributeByName</function> will 
      align data properly so you can cast its return value to 
      the  desired  type. For  example, if you have an attribute 
-     name which is of the type name, the <acronym>GetAttributeByName</acronym> 
+     name which is of the type name, the <function>GetAttributeByName</function> 
      call would look like:
 
      <programlisting>