DOC: eliminating erroneous productnames in EE modules

Author: Liudmila Mantrova

doc/src/sgml/aqo.sgml

@@ -132,7 +132,7 @@ where <replaceable>mode</> is the name of the optimization mode to use.
       </para>
       <note><para>
           You can view the
-          current query plan using the standard <productname>&productname;</productname> <command>EXPLAIN</> command with the 
+          current query plan using the standard <productname>&project;</productname> <command>EXPLAIN</> command with the 
           <command>ANALYZE</> option. For details, see the <xref linkend="using-explain">.</para>
         </note>
       <para>

doc/src/sgml/atx.sgml

@@ -7,7 +7,7 @@
   <title>Overview</title>
 
 <para>
-&productname; supports nested transactions: they are rarely explicitly used by programmer and mostly used for error handling and stored
+&project; supports nested transactions: they are rarely explicitly used by programmer and mostly used for error handling and stored
 procedures. It is possible to rollback a subtransaction without affecting the parent transaction. But commit of a subtraction is delayed until
 commit of parent transaction.
 </para>
@@ -121,7 +121,7 @@ deadlock is reported.
 <sect1><title>SQL Grammar Extension for Autonomous Transactions</title>
 
 <para>
-&productname; <literal>BEGIN</literal>/<literal>END</literal> transaction statements are extended by optional keyword <literal>AUTONOMOUS</literal>:
+&project; <literal>BEGIN</literal>/<literal>END</literal> transaction statements are extended by optional keyword <literal>AUTONOMOUS</literal>:
 </para>
 
 <programlisting>
@@ -170,7 +170,7 @@ $$ language plpgsql;
 <para>
 When exception is raised inside <command>BEGIN AUTONOMOUS</command> block, this autonomous transaction is aborted and standard 
 exception handling procedure is started, unwinding stack and executing exception handlers until exception is caught.
-So exception handling is done in the same way as with normal &productname; subtransactions.
+So exception handling is done in the same way as with normal &project; subtransactions.
 </para>
 <para>
 When an error is caught by an <literal>EXCEPTION</literal> clause, the local variables of the PL/pgSQL function remain as they were when the error occurred, but all changes to persistent database state within the block are rolled back.

doc/src/sgml/pghintplan.sgml

@@ -351,7 +351,7 @@ postgres=#
       <para>
         The objects as the hint parameter should be enclosed by double
         quotes if they includes parentheses, double quotes and white
-        spaces. The escaping rule is the same as <productname>&productname;</productname>.
+        spaces. The escaping rule is the same as <productname>&project;</productname>.
       </para>
     </sect3>
     <sect3>

doc/src/sgml/pgpro-scheduler.sgml

@@ -159,7 +159,7 @@ SELECT <function>pg_reload_conf()</>;
         subsystems may also use background workers. The
         <varname>schedule.max_workers</> value cannot exceed the
         total number of workers enabled by the
-        <varname>max_worker_processes</> <productname>&productname;</productname> variable.
+        <varname>max_worker_processes</> <productname>&project;</productname> variable.
       </para>
       <para>
         The <filename>pgpro_scheduler</filename> extension starts a

doc/src/sgml/pgrepack.sgml

@@ -278,7 +278,7 @@ $ psql -f "$(pg_config --sharedir)/contrib/pg_repack.sql" -d <replaceable>your_d
          <application>pg_repack</application> will wait to acquire this lock.
          If the lock cannot be taken after this duration, <application>pg_repack</application>
          will forcibly cancel the conflicting queries. If you are using
-         <productname>&productname;</productname> or <productname>PostgreSQL</productname> version 8.4
+         <productname>&project;</productname> or <productname>PostgreSQL</productname> version 8.4
          or newer, <application>pg_repack</application> will fall back to using
          <function>pg_terminate_backend()</function> to disconnect any remaining backends after
           this timeout has passed twice. The default is 60 seconds.
@@ -458,7 +458,7 @@ $ psql -f "$(pg_config --sharedir)/contrib/pg_repack.sql" -d <replaceable>your_d
     </varlistentry>
    </variablelist>
    <para>
-    This utility, like most other <productname>&productname;</> utilities,
+    This utility, like most other <productname>&project;</> utilities,
     also uses the environment variables supported by <application>libpq</>
     (see <xref linkend="libpq-envars">).
    </para>
@@ -512,7 +512,7 @@ $ pg_repack -d test --index idx --tablespace tbs
     </para>
 
     <para>
-     For <productname>&productname;</productname> or PostgreSQL 9.1 and newer execute:
+     For <productname>&project;</productname> or PostgreSQL 9.1 and newer execute:
 <programlisting>
 DROP EXTENSION pg_repack CASCADE
 </programlisting>