Minor SGML improvements.

diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml
index 5448913586c1117d420aa43540004a9c4f700e53..2316df99a5cc411e91a67c3e0ea29cd4535af0de 100644 (file)
--- a/doc/src/sgml/perform.sgml
+++ b/doc/src/sgml/perform.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -362,12 +362,13 @@ EXPLAIN ANALYZE SELECT * FROM tenk1 t1, tenk2 t2 WHERE t1.unique1 < 50 AND t1
   
 
   
-   One component of the statistics is the total number of entries in each
-   table and index, as well as the number of disk blocks occupied by each
-   table and index.  This information is kept in the table
-   pg_class in the columns reltuples
-   and relpages.  We can look at it
-   with queries similar to this one:
+   One component of the statistics is the total number of entries in
+   each table and index, as well as the number of disk blocks occupied
+   by each table and index.  This information is kept in the table
+   pg_class, in
+   the columns reltuples and
+   relpages.  We can look at it with
+   queries similar to this one:
 
 
 SELECT relname, relkind, reltuples, relpages FROM pg_class WHERE relname LIKE 'tenk1%';
@@ -406,14 +407,16 @@ SELECT relname, relkind, reltuples, relpages FROM pg_class WHERE relname LIKE 't
 
   
    Most queries retrieve only a fraction of the rows in a table, due
-   to having WHERE clauses that restrict the rows to be examined.
-   The planner thus needs to make an estimate of the
-   selectivity of WHERE clauses, that is, the fraction of
-   rows that match each condition in the WHERE clause.  The information
-   used for this task is stored in the pg_statistic
-   system catalog.  Entries in pg_statistic are
-   updated by ANALYZE and VACUUM ANALYZE commands
-   and are always approximate even when freshly updated.
+   to having WHERE clauses that restrict the rows to be
+   examined.  The planner thus needs to make an estimate of the
+   selectivity of WHERE clauses, that is,
+   the fraction of rows that match each condition in the
+   WHERE clause.  The information used for this task is
+   stored in the pg_statistic
+   system catalog.  Entries in pg_statistic
+   are updated by the ANALYZE and VACUUM
+   ANALYZE commands and are always approximate even when freshly
+   updated.