From 0fe9b399c09dd1c34c82993613b2d2116f948f23 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 14 Apr 2000 23:04:44 +0000
Subject: [PATCH] Fix busted markup.

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

diff --git a/doc/src/sgml/install.sgml b/doc/src/sgml/install.sgml
index 210b98b8cf..2c1c5714cd 100644
--- a/doc/src/sgml/install.sgml
+++ b/doc/src/sgml/install.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/install.sgml,v 1.39 2000/04/07 13:30:58 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/Attic/install.sgml,v 1.40 2000/04/14 23:04:44 tgl Exp $
 -->
 
  <chapter id="install">
@@ -103,16 +103,16 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/install.sgml,v 1.39 2000/04/07 13:30:
       Create the <productname>PostgreSQL</productname> superuser account.
       This is the user the server will run as. For production use you
       should create a separate, unprivileged account
-      (<literal>postgres</literal> is
-      commonly used). If you do not have root access or just want to play around,
+      (<literal>postgres</literal> is commonly used).
+      If you do not have root access or just want to play around,
       your own user account is enough.
      </para>
      <para>
       Running <productname>PostgreSQL</productname> as
-      <literal>tera</literal>teral>, <literal>bin</literal>,
+      <literal>root</literal>, <literal>bin</literal>,
       or any other account with special access rights is a security risk;
       <emphasis>don't do it</emphasis>.  The postmaster will in fact refuse
-      to start as root.
+      to start as <literal>root</literal>.
      </para>
      <para>
       You need not do the building and installation itself under this account
-- 
2.11.0