Correct misspellings of kB.

doc/src/sgml/config.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.96 2006/11/21 01:23:37 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.97 2006/11/25 22:44:48 petere Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -847,7 +847,7 @@ SET ENABLE_SEQSCAN TO OFF;
         margin is needed because the stack depth is not checked in every
         routine in the server, but only in key potentially-recursive routines
         such as expression evaluation.  The default setting is
-        2048 KB (two megabytes), which is conservatively small and unlikely
+        2048 kB (two megabytes), which is conservatively small and unlikely
         to risk crashes.  However, it may be too small to allow execution
         of complex functions.
         Only superusers can change this setting.

doc/src/sgml/runtime.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.373 2006/09/16 00:30:15 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.374 2006/11/25 22:44:48 petere Exp $ -->
 
 <chapter Id="runtime">
  <title>Operating System Environment</title>
@@ -680,7 +680,7 @@ psql: could not connect to server: No such file or directory
 options "SHMALL=8192"
 options "SHMMAX=\(SHMALL*PAGE_SIZE\)"
 </programlisting>
-         <varname>SHMALL</> is measured in 4KB pages, so a value of
+         <varname>SHMALL</> is measured in 4 kB pages, so a value of
          1024 represents 4 MB of shared memory. Therefore the above increases
          the maximum shared memory area to 32 MB.
          For those running 4.3 or later, you will probably also need to increase
@@ -921,7 +921,7 @@ kern.sysv.shmall=1024
        </para>
 
        <para>
-        <varname>SHMALL</> is measured in 4KB pages on this platform.
+        <varname>SHMALL</> is measured in 4 kB pages on this platform.
        </para>
 
        <para>

doc/src/sgml/storage.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.11 2006/06/18 15:38:36 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.12 2006/11/25 22:44:48 petere Exp $ -->
 
 <chapter id="storage">
 
@@ -188,7 +188,7 @@ Oversized-Attribute Storage Technique).
 
 <para>
 <productname>PostgreSQL</productname> uses a fixed page size (commonly
-8Kb), and does not allow tuples to span multiple pages.  Therefore,  it is
+8 kB), and does not allow tuples to span multiple pages.  Therefore,  it is
 not possible to store very large field values directly.  To overcome 
 this limitation, large  field values are compressed and/or broken up into
 multiple physical rows. This happens transparently to the user, with only
@@ -261,7 +261,7 @@ regardless of the actual size of the represented value.
 <para>
 The <acronym>TOAST</> code is triggered only
 when a row value to be stored in a table is wider than <literal>BLCKSZ/4</>
-bytes (normally 2Kb).  The <acronym>TOAST</> code will compress and/or move
+bytes (normally 2 kB).  The <acronym>TOAST</> code will compress and/or move
 field values out-of-line until the row value is shorter than
 <literal>BLCKSZ/4</> bytes or no more gains can be had.  During an UPDATE
 operation, values of unchanged fields are normally preserved as-is; so an
@@ -328,7 +328,7 @@ containing typical HTML pages and their URLs was stored in about half of the
 raw data size including the <acronym>TOAST</> table, and that the main table
 contained only about 10% of the entire data (the URLs and some small HTML
 pages). There was no run time difference compared to an un-<acronym>TOAST</>ed
-comparison table, in which all the HTML pages were cut down to 7Kb to fit.
+comparison table, in which all the HTML pages were cut down to 7 kB to fit.
 </para>
 
 </sect1>
@@ -361,7 +361,7 @@ an item is a row; in an index, an item is an index entry.
 
 <para>
 Every table and index is stored as an array of <firstterm>pages</> of a
-fixed size (usually 8Kb, although a different page size can be selected
+fixed size (usually 8 kB, although a different page size can be selected
 when compiling the server).  In a table, all the pages are logically
 equivalent, so a particular item (row) can be stored in any page.  In
 indexes, the first page is generally reserved as a <firstterm>metapage</>

doc/src/sgml/wal.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.41 2006/10/23 18:10:32 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.42 2006/11/25 22:44:48 petere Exp $ -->
 
 <chapter id="wal">
  <title>Reliability and the Write-Ahead Log</title>
@@ -313,7 +313,7 @@
    <acronym>WAL</acronym> logs are stored in the directory
    <filename>pg_xlog</filename> under the data directory, as a set of
    segment files, normally each 16 MB in size.  Each segment is divided into
-   pages, normally 8 KB each.  The log record headers are described in
+   pages, normally 8 kB each.  The log record headers are described in
    <filename>access/xlog.h</filename>; the record content is dependent
    on the type of event that is being logged.  Segment files are given
    ever-increasing numbers as names, starting at