@@ -3431,7 +3431,7 @@ ALTER TABLE measurement ATTACH PARTITION measurement_y2008m02
34313431 define any check constraints on this table, unless you intend them
34323432 to be applied equally to all partitions. There is no point in
34333433 defining any indexes or unique constraints on it, either. For our
3434- example, master table is the <structname>measurement</structname>
3434+ example,the master table is the <structname>measurement</structname>
34353435 table as originally defined.
34363436 </para>
34373437 </listitem>
@@ -3943,7 +3943,7 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate >= DATE '2008-01-01';
39433943 Constraint exclusion works in a very similar way to partition
39443944 pruning, except that it uses each table's <literal>CHECK</literal>
39453945 constraints — which gives it its name — whereas partition
3946- pruning uses the table's partition bounds, whichexists only in the
3946+ pruning uses the table's partition bounds, whichexist only in the
39473947 case of declarative partitioning. Another difference is that
39483948 constraint exclusion is only applied at plan time; there is no attempt
39493949 to remove partitions at execution time.