proof-reading

Author: petere

doc/src/sgml/array.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.16 2001/11/21 05:53:40 thomas Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.17 2001/11/28 20:49:09 petere Exp $ -->
 
 <chapter id="arrays">
  <title>Arrays</title>
@@ -68,8 +68,8 @@ SELECT name FROM sal_emp WHERE pay_by_quarter[1] &lt;&gt; pay_by_quarter[2];
   The array subscript numbers are written within square brackets.
   <productname>PostgreSQL</productname> uses the
   <quote>one-based</quote> numbering convention for arrays, that is,
-  an array of n elements starts with <literal>array[1]</literal> and
-  ends with <literal>array[n]</literal>.
+  an array of <replaceable>n</> elements starts with <literal>array[1]</literal> and
+  ends with <literal>array[<replaceable>n</>]</literal>.
  </para>
 
  <para>
@@ -232,7 +232,7 @@ SELECT * FROM sal_emp WHERE pay_by_quarter **= 10000;
 
  <tip>
   <para>
-   Arrays are not lists; using arrays in the manner described in the
+   Arrays are not sets; using arrays in the manner described in the
    previous paragraph is often a sign of database misdesign.  The
    array field should generally be split off into a separate table.
    Tables can obviously be searched easily.

doc/src/sgml/backup.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.21 2001/11/21 05:53:40 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.22 2001/11/28 20:49:09 petere Exp $
 -->
 <chapter id="backup">
  <title>Backup and Restore</title>
@@ -26,7 +26,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.21 2001/11/21 05:53:40 thom
   <title><acronym>SQL</> Dump</title>
 
   <para>
-   The idea behind this method is to generate a text file with SQL
+   The idea behind the SQL-dump method is to generate a text file with SQL
    commands that, when fed back to the server, will recreate the
    database in the same state as it was at the time of the dump.
    <productname>PostgreSQL</> provides the utility program
@@ -107,8 +107,8 @@ psql <replaceable class="parameter">dbname</replaceable> &lt; <replaceable class
     for the pg_dump command. The database <replaceable
     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
-    <replaceable class="parameter">dbname</></userinput>).
+    <application>psql</> (e.g., with <literal>createdb -T template0
+    <replaceable class="parameter">dbname</></literal>).
     <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.
@@ -376,15 +376,14 @@ tar -cf backup.tar /usr/local/pgsql/data
    change between releases of <productname>PostgreSQL</>. This does not
    apply to different <quote>patch levels</quote>, these always have
    compatible storage formats. For example, releases 7.0.1, 7.1.2, and
-   7.2 are not compatible, whereas &version;.1 and &version;.2 are. When you
+   7.2 are not compatible, whereas 7.1.1 and 7.1.2 are. When you
    update between compatible versions, then you can simply reuse the
    data area in disk by the new executables. Otherwise you need to
    <quote>back up</> your data and <quote>restore</> it on the new
    server, using <application>pg_dump</>. (There are checks in place
    that prevent you from doing the wrong thing, so no harm can be done
    by confusing these things.) The precise installation procedure is
-   not subject of this section, the <citetitle>Installation
-   Instructions</citetitle> carry these details.
+   not subject of this section, these details are in <xref linkend="installation">.
   </para>
 
   <para>