Update reference documentation on may/can/might:

Standard English uses "may", "can", and "might" in different ways:

        may - permission, "You may borrow my rake."

        can - ability, "I can lift that log."

        might - possibility, "It might rain today."

Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice.  Similarly, "It may crash" is better stated, "It might crash".

doc/src/sgml/ref/alter_domain.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_domain.sgml,v 1.20 2006/09/16 00:30:16 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_domain.sgml,v 1.21 2007/01/31 23:26:02 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -64,7 +64,7 @@ ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
     <listitem>
      <para>
       These forms change whether a domain is marked to allow NULL
-      values or to reject NULL values.  You may only <literal>SET NOT NULL</>
+      values or to reject NULL values.  You can only <literal>SET NOT NULL</>
       when the columns using the domain contain no null values.
      </para>
     </listitem>

doc/src/sgml/ref/alter_index.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_index.sgml,v 1.11 2006/09/16 00:30:16 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_index.sgml,v 1.12 2007/01/31 23:26:02 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -67,7 +67,7 @@ ALTER INDEX <replaceable class="PARAMETER">name</replaceable> RESET ( <replaceab
       <xref linkend="SQL-CREATEINDEX" endterm="sql-createindex-title">
       for details on the available parameters.  Note that the index contents
       will not be modified immediately by this command; depending on the
-      parameter you may need to rebuild the index with
+      parameter you might need to rebuild the index with
       <xref linkend="SQL-REINDEX" endterm="sql-reindex-title">
       to get the desired effects.
      </para>
@@ -80,7 +80,7 @@ ALTER INDEX <replaceable class="PARAMETER">name</replaceable> RESET ( <replaceab
      <para>
       This form resets one or more index-method-specific storage parameters to
       their defaults.  As with <literal>SET</>, a <literal>REINDEX</literal>
-      may be needed to update the index entirely.
+      might be needed to update the index entirely.
      </para>
     </listitem>
    </varlistentry>

doc/src/sgml/ref/alter_opfamily.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_opfamily.sgml,v 1.1 2007/01/23 05:07:17 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_opfamily.sgml,v 1.2 2007/01/31 23:26:02 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -202,7 +202,7 @@ ALTER OPERATOR FAMILY <replaceable>name</replaceable> USING <replaceable class="
 
   <para>
    The <literal>OPERATOR</> and <literal>FUNCTION</>
-   clauses may appear in any order.
+   clauses can appear in any order.
   </para>
 
  </refsect1>
@@ -216,7 +216,7 @@ ALTER OPERATOR FAMILY <replaceable>name</replaceable> USING <replaceable class="
    type(s).  The name of the operator or function occupying the slot is not
    mentioned.  Also, for <literal>DROP FUNCTION</> the type(s) to specify
    are the input data type(s) the function is intended to support; for
-   GIN and GiST indexes this may have nothing to do with the actual input
+   GIN and GiST indexes this might have nothing to do with the actual input
    argument types of the function.
   </para>
 

doc/src/sgml/ref/alter_sequence.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_sequence.sgml,v 1.15 2006/09/16 00:30:16 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_sequence.sgml,v 1.16 2007/01/31 23:26:02 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -136,7 +136,7 @@ ALTER SEQUENCE <replaceable class="parameter">name</replaceable> SET SCHEMA <rep
       <term><literal>CYCLE</literal></term>
       <listitem>
        <para>
-        The optional <literal>CYCLE</literal> key word may be used to enable
+        The optional <literal>CYCLE</literal> key word can be used to enable
         the sequence to wrap around when the
         <replaceable class="parameter">maxvalue</replaceable> or
         <replaceable class="parameter">minvalue</replaceable> has been

doc/src/sgml/ref/alter_table.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.92 2006/10/23 18:10:32 petere Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.93 2007/01/31 23:26:02 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -110,7 +110,7 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
       These forms set or remove the default value for a column.
       The default values only apply to subsequent <command>INSERT</command>
       commands; they do not cause rows already in the table to change.
-      Defaults may also be created for views, in which case they are
+      Defaults can also be created for views, in which case they are
       inserted into <command>INSERT</> statements on the view before
       the view's <literal>ON INSERT</literal> rule is applied.
      </para>
@@ -200,7 +200,7 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
       A disabled trigger is still known to the system, but is not executed
       when its triggering event occurs.  For a deferred trigger, the enable
       status is checked when the event occurs, not when the trigger function
-      is actually executed.  One may disable or enable a single
+      is actually executed.  One can disable or enable a single
       trigger specified by name, or all triggers on the table, or only
       user triggers (this option excludes triggers that are used to implement
       foreign key constraints).  Disabling or enabling constraint triggers
@@ -261,7 +261,7 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
       <xref linkend="SQL-CREATETABLE" endterm="sql-createtable-title">
       for details on the available parameters.  Note that the table contents
       will not be modified immediately by this command; depending on the
-      parameter you may need to rewrite the table to get the desired effects.
+      parameter you might need to rewrite the table to get the desired effects.
       That can be done with <xref linkend="SQL-CLUSTER"
       endterm="sql-cluster-title"> or one of the forms of <command>ALTER
       TABLE</> that forces a table rewrite.
@@ -284,7 +284,7 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
     <listitem>
      <para>
       This form resets one or more storage parameters to their
-      defaults.  As with <literal>SET</>, a table rewrite may be
+      defaults.  As with <literal>SET</>, a table rewrite might be
       needed to update the table entirely.
      </para>
     </listitem>
@@ -309,7 +309,7 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
       <literal>CHECK</literal> constraints of the parent. Currently
       <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and
       <literal>FOREIGN KEY</literal> constraints are not considered, but
-      this may change in the future.
+      this might change in the future.
      </para>
     </listitem>
    </varlistentry>
@@ -607,7 +607,7 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
    <para>
     Adding a column with a non-null default or changing the type of an
     existing column will require the entire table to be rewritten.  This
-    may take a significant amount of time for a large table; and it will
+    might take a significant amount of time for a large table; and it will
     temporarily require double the disk space.
    </para>
 
@@ -656,7 +656,7 @@ ALTER TABLE table ALTER COLUMN anycol TYPE anytype;
     expression is not applied to the column's default value (if any); the
     result might not be a constant expression as required for a default.
     This means that when there is no implicit or assignment cast from old to
-    new type, <literal>ALTER TYPE</> may fail to convert the default even
+    new type, <literal>ALTER TYPE</> might fail to convert the default even
     though a <literal>USING</literal> clause is supplied.  In such cases,
     drop the default with <literal>DROP DEFAULT</>, perform the <literal>ALTER
     TYPE</>, and then use <literal>SET DEFAULT</> to add a suitable new

doc/src/sgml/ref/analyze.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/analyze.sgml,v 1.20 2006/09/16 00:30:16 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/analyze.sgml,v 1.21 2007/01/31 23:26:02 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -109,7 +109,7 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ (<rep
    The statistics collected by <command>ANALYZE</command> usually
    include a list of some of the most common values in each column and
    a histogram showing the approximate data distribution in each
-   column.  One or both of these may be omitted if
+   column.  One or both of these can be omitted if
    <command>ANALYZE</command> deems them uninteresting (for example,
    in a unique-key column, there are no common values) or if the
    column data type does not support the appropriate operators.  There
@@ -123,7 +123,7 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ (<rep
    allows even very large tables to be analyzed in a small amount of
    time.  Note, however, that the statistics are only approximate, and
    will change slightly each time <command>ANALYZE</command> is run,
-   even if the actual table contents did not change.  This may result
+   even if the actual table contents did not change.  This might result
    in small changes in the planner's estimated costs shown by
    <command>EXPLAIN</command>. In rare situations, this
    non-determinism will cause the query optimizer to choose a
@@ -146,7 +146,7 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ (<rep
    <command>ANALYZE</command> and the amount of space occupied in
    <literal>pg_statistic</literal>.  In particular, setting the
    statistics target to zero disables collection of statistics for
-   that column.  It may be useful to do that for columns that are
+   that column.  It might be useful to do that for columns that are
    never used as part of the <literal>WHERE</>, <literal>GROUP BY</>,
    or <literal>ORDER BY</> clauses of queries, since the planner will
    have no use for statistics on such columns.

doc/src/sgml/ref/begin.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/begin.sgml,v 1.34 2006/09/16 00:30:17 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/begin.sgml,v 1.35 2007/01/31 23:26:02 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -109,7 +109,7 @@ where <replaceable class="parameter">transaction_mode</replaceable> is one of:
 
   <para>
    For reasons of backwards compatibility, the commas between successive
-   <replaceable class="parameter">transaction_modes</replaceable> may be
+   <replaceable class="parameter">transaction_modes</replaceable> can be
    omitted.
   </para>
  </refsect1>

doc/src/sgml/ref/checkpoint.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/checkpoint.sgml,v 1.14 2006/09/16 00:30:17 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/checkpoint.sgml,v 1.15 2007/01/31 23:26:02 momjian Exp $ -->
 
 <refentry id="sql-checkpoint">
  <refmeta>
@@ -42,7 +42,7 @@ CHECKPOINT
   </para>
 
   <para>
-   Only superusers may call <command>CHECKPOINT</command>.  The command is
+   Only superusers can call <command>CHECKPOINT</command>.  The command is
    not intended for use during normal operation.
   </para>
  </refsect1>

doc/src/sgml/ref/cluster.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/cluster.sgml,v 1.38 2006/11/04 19:03:51 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/cluster.sgml,v 1.39 2007/01/31 23:26:02 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -132,7 +132,7 @@ CLUSTER
     Because the planner records statistics about the ordering of
     tables, it is advisable to run <xref linkend="sql-analyze"
     endterm="sql-analyze-title"> on the newly clustered table.
-    Otherwise, the planner may make poor choices of query plans.
+    Otherwise, the planner might make poor choices of query plans.
    </para>
 
    <para>

doc/src/sgml/ref/comment.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/comment.sgml,v 1.34 2007/01/23 05:07:17 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/comment.sgml,v 1.35 2007/01/31 23:26:03 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -93,7 +93,7 @@ COMMENT ON
      <para>
       The name of the object to be commented.  Names of tables,
       aggregates, domains, functions, indexes, operators, operator classes,
-      operator families, sequences, types, and views may be schema-qualified.
+      operator families, sequences, types, and views can be schema-qualified.
      </para>
     </listitem>
    </varlistentry>

doc/src/sgml/ref/copy.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.77 2006/09/18 19:54:01 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.78 2007/01/31 23:26:03 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -358,9 +358,9 @@ COPY <replaceable class="parameter">count</replaceable>
     should not lead to problems in the event of a <command>COPY
     TO</command>, but the target table will already have received
     earlier rows in a <command>COPY FROM</command>. These rows will not
-    be visible or accessible, but they still occupy disk space. This may
+    be visible or accessible, but they still occupy disk space. This might
     amount to a considerable amount of wasted disk space if the failure
-    happened well into a large copy operation. You may wish to invoke
+    happened well into a large copy operation. You might wish to invoke
     <command>VACUUM</command> to recover the wasted space.
    </para>
  </refsect1>
@@ -395,7 +395,7 @@ COPY <replaceable class="parameter">count</replaceable>
    </para>
 
    <para>
-    Backslash characters (<literal>\</>) may be used in the
+    Backslash characters (<literal>\</>) can be used in the
     <command>COPY</command> data to quote data characters that might
     otherwise be taken as row or column delimiters. In particular, the
     following characters <emphasis>must</> be preceded by a backslash if
@@ -694,7 +694,7 @@ There is no alignment padding or any other extra data between fields.
     <para>
 Presently, all data values in a <command>COPY BINARY</command> file are
 assumed to be in binary format (format code one).  It is anticipated that a
-future extension may add a header field that allows per-column format codes
+future extension might add a header field that allows per-column format codes
 to be specified.
     </para>
 

doc/src/sgml/ref/create_aggregate.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.36 2006/09/16 00:30:17 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.37 2007/01/31 23:26:03 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -96,7 +96,7 @@ CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> (
   </para>
   
   <para>
-   An aggregate function may provide an initial condition,
+   An aggregate function can provide an initial condition,
    that is, an initial value for the internal state value.
    This is specified and stored in the database as a value of type
    <type>text</type>, but it must be a valid external representation

doc/src/sgml/ref/create_cast.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/create_cast.sgml,v 1.23 2006/09/16 00:30:17 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/create_cast.sgml,v 1.24 2007/01/31 23:26:03 momjian Exp $ -->
 
 <refentry id="SQL-CREATECAST">
  <refmeta>
@@ -44,7 +44,7 @@ SELECT CAST(42 AS text);
   </para>
 
   <para>
-   Two types may be <firstterm>binary compatible</firstterm>, which
+   Two types can be <firstterm>binary compatible</firstterm>, which
    means that they can be converted into one another <quote>for
    free</quote> without invoking any function.  This requires that
    corresponding values use the same internal representation.  For
@@ -145,7 +145,7 @@ SELECT 'The time is ' || CAST(now() AS text);
 
      <listitem>
       <para>
-       The function used to perform the cast.  The function name may
+       The function used to perform the cast.  The function name can
        be schema-qualified.  If it is not, the function will be looked
        up in the schema search path.  The function's result data type must
        match the target type of the cast.   Its arguments are discussed below.
@@ -169,7 +169,7 @@ SELECT 'The time is ' || CAST(now() AS text);
 
      <listitem>
       <para>
-       Indicates that the cast may be invoked implicitly in assignment
+       Indicates that the cast can be invoked implicitly in assignment
        contexts.
       </para>
      </listitem>
@@ -180,14 +180,14 @@ SELECT 'The time is ' || CAST(now() AS text);
 
      <listitem>
       <para>
-       Indicates that the cast may be invoked implicitly in any context.
+       Indicates that the cast can be invoked implicitly in any context.
       </para>
      </listitem>
     </varlistentry>
    </variablelist>
 
   <para>
-   Cast implementation functions may have one to three arguments.
+   Cast implementation functions can have one to three arguments.
    The first argument type must be identical to the cast's source type.
    The second argument,
    if present, must be type <type>integer</>; it receives the type

doc/src/sgml/ref/create_conversion.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/create_conversion.sgml,v 1.18 2006/09/16 00:30:17 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/create_conversion.sgml,v 1.19 2007/01/31 23:26:03 momjian Exp $ -->
 
 <refentry id="SQL-CREATECONVERSION">
  <refmeta>
@@ -27,7 +27,7 @@ CREATE [ DEFAULT ] CONVERSION <replaceable>name</replaceable>
 
   <para>
    <command>CREATE CONVERSION</command> defines a new conversion between
-   character set encodings.  Conversion names may be used in the
+   character set encodings.  Conversion names can be used in the
    <function>convert</function> function
    to specify a particular encoding conversion.  Also, conversions that
    are marked <literal>DEFAULT</> can be used for automatic encoding
@@ -65,7 +65,7 @@ CREATE [ DEFAULT ] CONVERSION <replaceable>name</replaceable>
 
      <listitem>
       <para>
-       The name of the conversion. The conversion name may be
+       The name of the conversion. The conversion name can be
        schema-qualified. If it is not, the conversion is defined in the
        current schema. The conversion name must be unique within a
        schema.
@@ -98,7 +98,7 @@ CREATE [ DEFAULT ] CONVERSION <replaceable>name</replaceable>
 
      <listitem>
       <para>
-       The function used to perform the conversion.  The function name may
+       The function used to perform the conversion.  The function name can
        be schema-qualified.  If it is not, the function will be looked
        up in the path.
       </para>
@@ -129,7 +129,7 @@ conv_proc(
   </para>
 
   <para>
-   The privileges required to create a conversion may be changed in a future
+   The privileges required to create a conversion might be changed in a future
    release.
   </para>
  </refsect1>

doc/src/sgml/ref/create_database.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_database.sgml,v 1.46 2006/09/16 00:30:17 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_database.sgml,v 1.47 2007/01/31 23:26:03 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -60,7 +60,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
    database containing only the standard objects predefined by your
    version of <productname>PostgreSQL</productname>.  This is useful
    if you wish to avoid copying
-   any installation-local objects that may have been added to
+   any installation-local objects that might have been added to
    <literal>template1</>.
   </para>
  </refsect1>

doc/src/sgml/ref/create_domain.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.29 2006/09/16 00:30:17 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.30 2007/01/31 23:26:03 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -76,7 +76,7 @@ where <replaceable class="PARAMETER">constraint</replaceable> is:
       <term><replaceable class="PARAMETER">data_type</replaceable></term>
       <listitem>
        <para>
-        The underlying data type of the domain. This may include array
+        The underlying data type of the domain. This can include array
         specifiers.
        </para>
       </listitem>

doc/src/sgml/ref/create_function.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.71 2007/01/22 01:35:19 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.72 2007/01/31 23:26:03 momjian Exp $
 -->
 
 <refentry id="SQL-CREATEFUNCTION">
@@ -49,7 +49,7 @@ CREATE [ OR REPLACE ] FUNCTION
    specified schema.  Otherwise it is created in the current schema.
    The name of the new function must not match any existing function
    with the same argument types in the same schema.  However,
-   functions of different argument types may share a name (this is
+   functions of different argument types can share a name (this is
    called <firstterm>overloading</>).
   </para>
 
@@ -125,11 +125,11 @@ CREATE [ OR REPLACE ] FUNCTION
      <listitem>
       <para>
        The data type(s) of the function's arguments (optionally 
-       schema-qualified), if any. The argument types may be base, composite,
-       or domain types, or may reference the type of a table column.
+       schema-qualified), if any. The argument types can be base, composite,
+       or domain types, or can reference the type of a table column.
       </para>
       <para>
-       Depending on the implementation language it may also be allowed
+       Depending on the implementation language it might also be allowed
        to specify <quote>pseudotypes</> such as <type>cstring</>.
        Pseudotypes indicate that the actual argument type is either
        incompletely specified, or outside the set of ordinary SQL data types.
@@ -151,16 +151,16 @@ CREATE [ OR REPLACE ] FUNCTION
      <listitem>
       <para>
        The return data type (optionally schema-qualified). The return type 
-       may be a base, composite, or domain type,
-       or may reference the type of a table column.
-       Depending on the implementation language it may also be allowed
+       can be a base, composite, or domain type,
+       or can reference the type of a table column.
+       Depending on the implementation language it might also be allowed
        to specify <quote>pseudotypes</> such as <type>cstring</>.
        If the function is not supposed to return a value, specify
        <type>void</> as the return type.
       </para>
       <para>
        When there are <literal>OUT</> or <literal>INOUT</> parameters,
-       the <literal>RETURNS</> clause may be omitted.  If present, it
+       the <literal>RETURNS</> clause can be omitted.  If present, it
        must agree with the result type implied by the output parameters:
        <literal>RECORD</> if there are multiple output parameters, or
        the same type as the single output parameter.
@@ -185,10 +185,10 @@ CREATE [ OR REPLACE ] FUNCTION
      <listitem>
       <para>
        The name of the language that the function is implemented in.
-       May be <literal>SQL</literal>, <literal>C</literal>,
+       Can be <literal>SQL</literal>, <literal>C</literal>,
        <literal>internal</literal>, or the name of a user-defined
        procedural language.  For backward compatibility,
-       the name may be enclosed by single quotes.
+       the name can be enclosed by single quotes.
       </para>
      </listitem>
     </varlistentry>
@@ -202,7 +202,7 @@ CREATE [ OR REPLACE ] FUNCTION
       <para>
        These attributes inform the query optimizer about the behavior
        of the function.  At most one choice
-       may be specified.  If none of these appear,
+       can be specified.  If none of these appear,
        <literal>VOLATILE</literal> is the default assumption.
       </para>
 
@@ -326,7 +326,7 @@ CREATE [ OR REPLACE ] FUNCTION
      <listitem>
       <para>
        A string constant defining the function; the meaning depends on the
-       language.  It may be an internal function name, the path to an
+       language.  It can be an internal function name, the path to an
        object file, an SQL command, or text in a procedural language.
       </para>
      </listitem>
@@ -357,7 +357,7 @@ CREATE [ OR REPLACE ] FUNCTION
      <listitem>
       <para>
        The historical way to specify optional pieces of information
-       about the function.  The following attributes may appear here:
+       about the function.  The following attributes can appear here:
 
       <variablelist>
        <varlistentry>

doc/src/sgml/ref/create_index.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_index.sgml,v 1.59 2007/01/09 02:14:10 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_index.sgml,v 1.60 2007/01/31 23:26:03 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -75,7 +75,7 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] <replaceable class="parameter">name</re
   </para>
 
   <para>
-    The expression used in the <literal>WHERE</literal> clause may refer
+    The expression used in the <literal>WHERE</literal> clause can refer
     only to columns of the underlying table, but it can use all columns,
     not just the ones being indexed.  Presently, subqueries and
     aggregate expressions are also forbidden in <literal>WHERE</literal>.
@@ -172,7 +172,7 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] <replaceable class="parameter">name</re
        <para>
         An expression based on one or more columns of the table.  The
         expression usually must be written with surrounding parentheses,
-        as shown in the syntax.  However, the parentheses may be omitted
+        as shown in the syntax.  However, the parentheses can be omitted
         if the expression has the form of a function call.
        </para>
       </listitem>
@@ -324,14 +324,14 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] <replaceable class="parameter">name</re
     significantly longer to complete.  However, since it allows normal
     operations to continue while the index is built, this method is useful for
     adding new indexes in a production environment.  Of course, the extra CPU
-    and I/O load imposed by the index creation may slow other operations.
+    and I/O load imposed by the index creation might slow other operations.
    </para>
 
    <para>
     If a problem arises during the second scan of the table, such as a
     uniqueness violation in a unique index, the <command>CREATE INDEX</>
     command will fail but leave behind an <quote>invalid</> index. This index
-    will be ignored for querying purposes because it may be incomplete;
+    will be ignored for querying purposes because it might be incomplete;
     however it will still consume update overhead.  The recommended recovery
     method in such cases is to drop the index and try again to perform
     <command>CREATE INDEX CONCURRENTLY</>.  (Another possibility is to rebuild
@@ -378,7 +378,7 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] <replaceable class="parameter">name</re
 
   <para>
    Currently, only the B-tree and GiST index methods support
-   multicolumn indexes. Up to 32 fields may be specified by default.
+   multicolumn indexes. Up to 32 fields can be specified by default.
    (This limit can be altered when building
    <productname>PostgreSQL</productname>.)  Only B-tree currently
    supports unique indexes.

doc/src/sgml/ref/create_language.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_language.sgml,v 1.42 2006/09/16 00:30:17 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_language.sgml,v 1.43 2007/01/31 23:26:03 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -107,7 +107,7 @@ CREATE [ TRUSTED ] [ PROCEDURAL ] LANGUAGE <replaceable class="parameter">name</
       </para>
 
       <para>
-       For backward compatibility, the name may be enclosed by single
+       For backward compatibility, the name can be enclosed by single
        quotes.
       </para>
      </listitem>
@@ -192,7 +192,7 @@ CREATE [ TRUSTED ] [ PROCEDURAL ] LANGUAGE <replaceable class="parameter">name</
    To create functions in a procedural language, a user must have the
    <literal>USAGE</literal> privilege for the language.  By default,
    <literal>USAGE</> is granted to <literal>PUBLIC</> (i.e., everyone)
-   for trusted languages.  This may be revoked if desired.
+   for trusted languages.  This can be revoked if desired.
   </para>
 
   <para>
@@ -208,7 +208,7 @@ CREATE [ TRUSTED ] [ PROCEDURAL ] LANGUAGE <replaceable class="parameter">name</
    in <structname>pg_pltemplate</>.  But when there is an entry,
    the functions need not already exist;
    they will be automatically defined if not present in the database.
-   (This can result in <command>CREATE LANGUAGE</> failing, if the
+   (This might result in <command>CREATE LANGUAGE</> failing, if the
    shared library that implements the language is not available in
    the installation.)
   </para>

doc/src/sgml/ref/create_opclass.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_opclass.sgml,v 1.19 2007/01/23 05:07:17 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_opclass.sgml,v 1.20 2007/01/31 23:26:03 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -88,7 +88,7 @@ CREATE OPERATOR CLASS <replaceable class="parameter">name</replaceable> [ DEFAUL
     <term><replaceable class="parameter">name</replaceable></term>
     <listitem>
      <para>
-      The name of the operator class to be created.  The name may be
+      The name of the operator class to be created.  The name can be
       schema-qualified.
      </para>
     </listitem>
@@ -161,7 +161,7 @@ CREATE OPERATOR CLASS <replaceable class="parameter">name</replaceable> [ DEFAUL
       In an <literal>OPERATOR</> clause,
       the operand data type(s) of the operator, or <literal>NONE</> to
       signify a left-unary or right-unary operator.  The operand data
-      types may be omitted in the normal case where they are the same
+      types can be omitted in the normal case where they are the same
       as the operator class's data type.
      </para>
 
@@ -236,7 +236,7 @@ CREATE OPERATOR CLASS <replaceable class="parameter">name</replaceable> [ DEFAUL
 
   <para>
    The <literal>OPERATOR</>, <literal>FUNCTION</>, and <literal>STORAGE</>
-   clauses may appear in any order.
+   clauses can appear in any order.
   </para>
  </refsect1>