In documentation, use "lower case"/"upper case" consistently (use space

between words).

doc/src/sgml/citext.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/citext.sgml,v 1.3 2010/06/03 03:04:55 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/citext.sgml,v 1.4 2010/06/29 22:29:13 momjian Exp $ -->
 
 <sect1 id="citext">
  <title>citext</title>
@@ -58,8 +58,8 @@
     The <type>citext</> data type allows you to eliminate calls
     to <function>lower</> in SQL queries, and allows a primary key to
     be case-insensitive. <type>citext</> is locale-aware, just
-    like <type>text</>, which means that the comparison of uppercase and
-    lowercase characters is dependent on the rules of
+    like <type>text</>, which means that the comparison of upper case and
+    lower case characters is dependent on the rules of
     the <literal>LC_CTYPE</> locale setting. Again, this behavior is
     identical to the use of <function>lower</> in queries. But because it's
     done transparently by the datatype, you don't have to remember to do

doc/src/sgml/client-auth.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.138 2010/05/26 23:49:18 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.139 2010/06/29 22:29:13 momjian Exp $ -->
 
 <chapter id="client-authentication">
  <title>Client Authentication</title>
@@ -994,7 +994,7 @@ omicron         bryanh                  guest1
     on the same host.
     Some Kerberos implementations might also require a different service name,
     such as Microsoft Active Directory which requires the service name
-    to be in uppercase (<literal>POSTGRES</literal>).
+    to be in upper case (<literal>POSTGRES</literal>).
    </para>
 
    <para>

doc/src/sgml/config.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.286 2010/06/29 22:23:02 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.287 2010/06/29 22:29:13 momjian Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -1015,7 +1015,7 @@ SET ENABLE_SEQSCAN TO OFF;
         <literal>mylib.so</> (or on some platforms,
         <literal>mylib.sl</>) to be preloaded from the installation's
         standard library directory.
-        All library names are converted to lowercase unless double-quoted.
+        All library names are converted to lower case unless double-quoted.
         If more than one library is to be loaded, separate their names
         with commas.  This parameter can only be set at server start.
        </para>
@@ -4840,7 +4840,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
         This variable specifies one or more shared libraries that are
         to be preloaded at connection start.  If more than one library
         is to be loaded, separate their names with commas.  All library
-        names are converted to lowercase unless double-quoted.
+        names are converted to lower case unless double-quoted.
         This parameter cannot be changed after the start of a particular
         session.
        </para>

doc/src/sgml/func.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.519 2010/06/17 01:32:09 rhaas Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.520 2010/06/29 22:29:13 momjian Exp $ -->
 
  <chapter id="functions">
   <title>Functions and Operators</title>
@@ -1227,7 +1227,7 @@
       <row>
        <entry><literal><function>upper</function>(<parameter>string</parameter>)</literal></entry>
        <entry><type>text</type></entry>
-       <entry>Convert string to uppercase</entry>
+       <entry>Convert string to upper case</entry>
        <entry><literal>upper('tom')</literal></entry>
        <entry><literal>TOM</literal></entry>
       </row>
@@ -1457,8 +1457,8 @@
        <entry><literal><function>initcap</function>(<parameter>string</parameter>)</literal></entry>
        <entry><type>text</type></entry>
        <entry>
-        Convert the first letter of each word to uppercase and the
-        rest to lowercase. Words are sequences of alphanumeric
+        Convert the first letter of each word to upper case and the
+        rest to lower case. Words are sequences of alphanumeric
         characters separated by non-alphanumeric characters.
        </entry>
        <entry><literal>initcap('hi THOMAS')</literal></entry>
@@ -5014,7 +5014,7 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
        </row>
        <row>
         <entry><literal>MONTH</literal></entry>
-        <entry>full uppercase month name (blank-padded to 9 chars)</entry>
+        <entry>full upper case month name (blank-padded to 9 chars)</entry>
        </row>
        <row>
         <entry><literal>Month</literal></entry>
@@ -5022,11 +5022,11 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
        </row>
        <row>
         <entry><literal>month</literal></entry>
-        <entry>full lowercase month name (blank-padded to 9 chars)</entry>
+        <entry>full lower case month name (blank-padded to 9 chars)</entry>
        </row>
        <row>
         <entry><literal>MON</literal></entry>
-        <entry>abbreviated uppercase month name (3 chars in English, localized lengths vary)</entry>
+        <entry>abbreviated upper case month name (3 chars in English, localized lengths vary)</entry>
        </row>
        <row>
         <entry><literal>Mon</literal></entry>
@@ -5034,7 +5034,7 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
        </row>
        <row>
         <entry><literal>mon</literal></entry>
-        <entry>abbreviated lowercase month name (3 chars in English, localized lengths vary)</entry>
+        <entry>abbreviated lower case month name (3 chars in English, localized lengths vary)</entry>
        </row>
        <row>
         <entry><literal>MM</literal></entry>
@@ -5042,7 +5042,7 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
        </row>
        <row>
         <entry><literal>DAY</literal></entry>
-        <entry>full uppercase day name (blank-padded to 9 chars)</entry>
+        <entry>full upper case day name (blank-padded to 9 chars)</entry>
        </row>
        <row>
         <entry><literal>Day</literal></entry>
@@ -5050,11 +5050,11 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
        </row>
        <row>
         <entry><literal>day</literal></entry>
-        <entry>full lowercase day name (blank-padded to 9 chars)</entry>
+        <entry>full lower case day name (blank-padded to 9 chars)</entry>
        </row>
        <row>
         <entry><literal>DY</literal></entry>
-        <entry>abbreviated uppercase day name (3 chars in English, localized lengths vary)</entry>
+        <entry>abbreviated upper case day name (3 chars in English, localized lengths vary)</entry>
        </row>
        <row>
         <entry><literal>Dy</literal></entry>
@@ -5062,7 +5062,7 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
        </row>
        <row>
         <entry><literal>dy</literal></entry>
-        <entry>abbreviated lowercase day name (3 chars in English, localized lengths vary)</entry>
+        <entry>abbreviated lower case day name (3 chars in English, localized lengths vary)</entry>
        </row>
        <row>
         <entry><literal>DDD</literal></entry>
@@ -5110,19 +5110,19 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
        </row>
        <row>
         <entry><literal>RM</literal></entry>
-        <entry>month in uppercase Roman numerals (I-XII; I=January)</entry>
+        <entry>month in upper case Roman numerals (I-XII; I=January)</entry>
        </row>
        <row>
         <entry><literal>rm</literal></entry>
-        <entry>month in lowercase Roman numerals (i-xii; i=January)</entry>
+        <entry>month in lower case Roman numerals (i-xii; i=January)</entry>
        </row>
        <row>
         <entry><literal>TZ</literal></entry>
-        <entry>uppercase time-zone name</entry>
+        <entry>upper case time-zone name</entry>
        </row>
        <row>
         <entry><literal>tz</literal></entry>
-        <entry>lowercase time-zone name</entry>
+        <entry>lower case time-zone name</entry>
        </row>
       </tbody>
      </tgroup>
@@ -5155,12 +5155,12 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
        </row>
        <row>
         <entry><literal>TH</literal> suffix</entry>
-        <entry>uppercase ordinal number suffix</entry>
+        <entry>upper case ordinal number suffix</entry>
         <entry><literal>DDTH</literal>, e.g., <literal>12TH</></entry>
        </row>   
        <row>
         <entry><literal>th</literal> suffix</entry>
-        <entry>lowercase ordinal number suffix</entry>
+        <entry>lower case ordinal number suffix</entry>
         <entry><literal>DDth</literal>, e.g., <literal>12th</></entry>
        </row>
        <row>
@@ -5521,12 +5521,12 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
        </row>
        <row>
         <entry><literal>TH</literal> suffix</entry>
-        <entry>uppercase ordinal number suffix</entry>
+        <entry>upper case ordinal number suffix</entry>
         <entry><literal>999TH</literal></entry>
        </row>   
        <row>
         <entry><literal>th</literal> suffix</entry>
-        <entry>lowercase ordinal number suffix</entry>
+        <entry>lower case ordinal number suffix</entry>
         <entry><literal>999th</literal></entry>
        </row>
       </tbody>
@@ -8959,7 +8959,7 @@ table2-mapping
    converter will do the work for you.  Just write the sequence name enclosed
    in single quotes so that it looks like a literal constant.  For
    compatibility with the handling of ordinary
-   <acronym>SQL</acronym> names, the string will be converted to lowercase
+   <acronym>SQL</acronym> names, the string will be converted to lower case
    unless it contains double quotes around the sequence name.  Thus:
 <programlisting>
 nextval('foo')      <lineannotation>operates on sequence <literal>foo</literal></>
@@ -12612,7 +12612,7 @@ SELECT pg_type_is_visible('myschema.widget'::regtype);
    with the column.  The first input parameter is a table name with
    optional schema, and the second parameter is a column name.  Because
    the first parameter is potentially a schema and table, it is not treated
-   as a double-quoted identifier, meaning it is lowercased by default,
+   as a double-quoted identifier, meaning it is lower cased by default,
    while the second parameter, being just a column name, is treated as
    double-quoted and has its case preserved.  The function returns a value
    suitably formatted for passing to sequence functions (see <xref

doc/src/sgml/installation.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.346 2010/06/25 16:55:49 rhaas Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.347 2010/06/29 22:29:13 momjian Exp $ -->
 
 <chapter id="installation">
  <title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -912,7 +912,7 @@ su - postgres
          by GSSAPI).
          <literal>postgres</literal> is the default. There's usually no
          reason to change this unless you have a Windows environment,
-         in which case it must be set to uppercase
+         in which case it must be set to upper case
          <literal>POSTGRES</literal>.
         </para>
        </listitem>

doc/src/sgml/libpq.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.310 2010/06/25 17:08:09 rhaas Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.311 2010/06/29 22:29:14 momjian Exp $ -->
 
 <chapter id="libpq">
  <title><application>libpq</application> - C Library</title>
@@ -3157,7 +3157,7 @@ typedef struct {
       This is useful when a user-supplied identifier might contain
       special characters that would otherwise not be interpreted as part
       of the identifier by the SQL parser, or when the identifier might
-      contain uppercase characters whose case should be preserved.
+      contain upper case characters whose case should be preserved.
      </para>
 
      <para>

doc/src/sgml/pgcrypto.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/pgcrypto.sgml,v 1.8 2009/12/08 20:08:30 mha Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/pgcrypto.sgml,v 1.9 2010/06/29 22:29:14 momjian Exp $ -->
 
 <sect1 id="pgcrypto">
  <title>pgcrypto</title>
@@ -267,7 +267,7 @@
     of different hashing algorithms.
     The table shows how much time it would take to try all
     combinations of characters in an 8-character password, assuming
-    that the password contains either only lowercase letters, or
+    that the password contains either only lower case letters, or
     upper- and lower-case letters and numbers.
     In the <literal>crypt-bf</literal> entries, the number after a slash is
     the <parameter>iter_count</parameter> parameter of

doc/src/sgml/plpgsql.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.153 2010/04/27 14:32:40 alvherre Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.154 2010/06/29 22:29:14 momjian Exp $ -->
 
 <chapter id="plpgsql">
   <title><application>PL/pgSQL</application> - <acronym>SQL</acronym> Procedural Language</title>
@@ -219,7 +219,7 @@ END <optional> <replaceable>label</replaceable> </optional>;
 
     <para>
      All key words are case-insensitive.
-     Identifiers are implicitly converted to lowercase
+     Identifiers are implicitly converted to lower case
      unless double-quoted, just as they are in ordinary SQL commands.
     </para>