From f124e820a1a352281787275f5eb6d1bf736f37b3 Mon Sep 17 00:00:00 2001
From: Neil Conway <neilc@samurai.com>
Date: Wed, 27 Jul 2005 13:42:01 +0000
Subject: [PATCH] Add some missing SGML markup.

---
 doc/src/sgml/ref/pg_restore.sgml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml
index d4a1a3e0f05..ec19d8e7844 100644
--- a/doc/src/sgml/ref/pg_restore.sgml
+++ b/doc/src/sgml/ref/pg_restore.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.54 2005/07/25 22:12:31 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.55 2005/07/27 13:42:01 neilc Exp $ -->
 
 <refentry id="APP-PGRESTORE">
  <refmeta>
@@ -361,10 +361,10 @@
       <term><option>--use-set-session-authorization</option></term>
       <listitem>
        <para>
-        Output SQL standard SET SESSION AUTHORIZATION commands instead of
-        ALTER OWNER commands.  This makes the dump more standards compatible,
-        but depending on the history of the objects in the dump, may not
-        restore properly.
+        Output SQL standard <command>SET SESSION AUTHORIZATION</>
+        commands instead of <command>ALTER OWNER</> commands.  This
+        makes the dump more standards compatible, but depending on the
+        history of the objects in the dump, may not restore properly.
        </para>
       </listitem>
      </varlistentry>