From: Peter Eisentraut <peter_e@gmx.net>
Date: Wed, 14 Mar 2001 22:20:02 +0000 (+0000)
Subject: Fix markup.
X-Git-Tag: REL7_1~183
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2736ad31dc68bc3294bb6c9d1a56c424d62bf2b5;p=postgresql

Fix markup.
---

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 49e139cc6e..89ad624674 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.5 2001/03/13 14:08:18 pjw Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.6 2001/03/14 22:20:02 petere Exp $ -->
 <chapter id="backup">
  <title>Backup and Restore</title>
 
@@ -103,7 +103,7 @@ psql <replaceable class="parameter">dbname</replaceable> &lt; <replaceable class
     class="parameter">dbname</replaceable> will not be created by this
     command, you must create it yourself from template0 before executing
     <application>psql</> (e.g., with <userinput>createdb -t template0
-    <replaceableclass="parameter">dbname</></userinput>).
+    <replaceable class="parameter">dbname</></userinput>).
     <application>psql</> supports similar options to <application>pg_dump</> 
     for controlling the database server location and the user names. See
     its reference page for more information.
@@ -135,7 +135,7 @@ pg_dump -h <replaceable>host1</> <replaceable>dbname</> | psql -h <replaceable>h
   <important>
    <para>
 	The dumps produced by pg_dump are relative to template0. This means 
-    that any languages, procedure etc added to template1 will also be
+    that any languages, procedures, etc. added to template1 will also be
     dumped by <application>pg_dump</>. As a result, when restoring, if 
     you are using a customized template1, you must create the empty
     database from template0, as in the example above.
@@ -293,7 +293,7 @@ pg_dump -Fc <replaceable class="parameter">dbname</replaceable> > <replaceable c
    <para>
     For reasons of backward compatibility, <application>pg_dump</> does
     not dump large objects by default. To dump large objects you must use 
-    either custom or TAR output format, and use the -B option in 
+    either the custom or the TAR output format, and use the -B option in 
     <application>pg_dump</>. See the reference pages for details.
     The directory <filename>contrib/pg_dumplo</> of the
     <productname>Postgres</> source tree also contains a program that can