From 93eab311e4a650f2e01b7134155ccef7ccb6a8f4 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 24 Sep 2008 16:30:26 +0000
Subject: [PATCH] Fix markup tag error, envvar -> envar.

---
 doc/src/sgml/charset.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
index 0aeef78966..a77d3893c0 100644
--- a/doc/src/sgml/charset.sgml
+++ b/doc/src/sgml/charset.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.89 2008/09/23 10:58:03 heikki Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.90 2008/09/24 16:30:26 momjian Exp $ -->
 
 <chapter id="charset">
  <title>Localization</>
@@ -321,7 +321,7 @@ initdb --locale=sv_SE
   <para>
    An important restriction, however, is that each database's character set
    must be compatible with the database's <envar>LC_CTYPE</> and
-   <envvar>LC_COLLATE</> locale settings. For <literal>C</> or
+   <envar>LC_COLLATE</> locale settings. For <literal>C</> or
    <literal>POSIX</> locale, any character set is allowed, but for other
    locales there is only one character set that will work correctly.
   </para>