Fix misspellings of GB.

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index f1c3aab30e4304af591a5daf18c22f703211c8fc..87483541795ab2a3b5c996ccbddf0bad55b236ec 100644 (file)
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.486 2006/11/25 07:03:57 neilc Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.487 2006/11/25 22:55:59 petere Exp $ -->
 <!--
 
 Typical markup:
@@ -12078,7 +12078,7 @@ On some platforms, building with -fstrict-aliasing causes bugs.
 </para></listitem>
 <listitem><para>Make pg_restore handle 64-bit off_t correctly</para>
 <para>
-This bug prevented proper restoration from archive files exceeding 4Gb.
+This bug prevented proper restoration from archive files exceeding 4 GB.
 </para></listitem>
 <listitem><para>Make contrib/dblink not assume that local and remote type OIDs
 match (Joe)</para></listitem>

diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml
index ac4225b7bd73ae3289cc5d7c79e634c236b72d31..3635370ca3f2fb198305c88d574c9c495113f8c7 100644 (file)
--- a/doc/src/sgml/storage.sgml
+++ b/doc/src/sgml/storage.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.12 2006/11/25 22:44:48 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.13 2006/11/25 22:55:59 petere Exp $ -->
 
 <chapter id="storage">
 
@@ -138,7 +138,7 @@ Avoid assuming that filenode and table OID are the same.
 </caution>
 
 <para>
-When a table or index exceeds 1Gb, it is divided into gigabyte-sized
+When a table or index exceeds 1 GB, it is divided into gigabyte-sized
 <firstterm>segments</>.  The first segment's file name is the same as the
 filenode; subsequent segments are named filenode.1, filenode.2, etc.
 This arrangement avoids problems on platforms that have file size limitations.
@@ -212,7 +212,7 @@ value, but in some cases more efficient approaches are possible.)
 <para>
 <acronym>TOAST</> usurps the high-order two bits of the varlena length word,
 thereby limiting the logical size of any value of a <acronym>TOAST</>-able
-data type to 1Gb (2<superscript>30</> - 1 bytes).  When both bits are zero,
+data type to 1 GB (2<superscript>30</> - 1 bytes).  When both bits are zero,
 the value is an ordinary un-<acronym>TOAST</>ed value of the data type.  One
 of these bits, if set, indicates that the value has been compressed and must
 be decompressed before use.  The other bit, if set, indicates that the value