From 9529f4d53263c7a85d8a5c4291fc4bc3f4c394f1 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 18 Feb 2010 04:14:38 +0000
Subject: [PATCH] Add missing close tag.

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

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 48f6e98f10..91a3e4161e 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.45 2010/02/18 03:16:09 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.46 2010/02/18 04:14:38 momjian Exp $ -->
 
 <chapter id="high-availability">
  <title>High Availability, Load Balancing, and Replication</title>
@@ -1257,7 +1257,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
     recovery is to allow the last two actions, so there are small and
     subtle differences in behaviour between read-only transactions
     run on a standby and run during normal operation.
-    It is possible that <command>LISTEN, <command>UNLISTEN</>,
+    It is possible that <command>LISTEN</>, <command>UNLISTEN</>,
     <command>NOTIFY</>, and temporary tables might be allowed in a
     future release.
    </para>
-- 
2.40.0