@@ -312,14 +312,14 @@ current=testdb1 (should be testdb1)
312312 </para>
313313
314314 <para>
315- The third option is to declare asql identifier linked to
315+ The third option is to declare aSQL identifier linked to
316316 the connection, for example:
317317<programlisting>
318318EXEC SQL AT <replaceable>connection-name</replaceable> DECLARE <replaceable>statement-name</replaceable> STATEMENT;
319319EXEC SQL PREPARE <replaceable>statement-name</replaceable> FROM :<replaceable>dyn-string</replaceable>;
320320</programlisting>
321- Once you link asql identifier to a connection,you execute a dynamic SQL
322- withoutAT clause.
321+ Once you link aSQL identifier to a connection, execute dynamic SQL
322+ statements using this identifier withoutthe <literal>AT</literal> clause.
323323 </para>
324324 </sect2>
325325
@@ -1209,8 +1209,8 @@ EXEC SQL END DECLARE SECTION;
12091209 <title id="ecpg-type-bytea">bytea</title>
12101210
12111211 <para>
1212- The handling of the <type>bytea</type> type isalso similar to
1213- the <type>VARCHAR</type>. The definition on an array of type
1212+ The handling of the <type>bytea</type> type is similar to
1213+ that of <type>VARCHAR</type>. The definition on an array of type
12141214 <type>bytea</type> is converted into a named struct for every
12151215 variable. A declaration like:
12161216<programlisting>
@@ -1221,8 +1221,8 @@ bytea var[180];
12211221struct bytea_var { int len; char arr[180]; } var;
12221222</programlisting>
12231223 The member <structfield>arr</structfield> hosts binary format
1224- data. Italso canhandle even <literal>'\0'</literal> as part of
1225- data unlike <type>VARCHAR</type>.
1224+ data. It canalso handle <literal>'\0'</literal> as part of
1225+ data, unlike <type>VARCHAR</type>.
12261226 The data is converted from/to hex format and sent/received by
12271227 ecpglib.
12281228 </para>
@@ -6810,7 +6810,7 @@ EXEC SQL DECLARE cur1 CURSOR FOR stmt1;
68106810 <refentry id="ecpg-sql-declare-statement">
68116811 <refnamediv>
68126812 <refname>DECLARE STATEMENT</refname>
6813- <refpurpose>declares SQL statement identifier associated with connection</refpurpose>
6813+ <refpurpose>declaresa SQL statement identifier associated with connection</refpurpose>
68146814 </refnamediv>
68156815
68166816 <refsynopsisdiv>
@@ -6823,12 +6823,13 @@ EXEC SQL [ AT <replaceable class="parameter">connection_name</replaceable> ] DEC
68236823 <title>Description</title>
68246824
68256825 <para>
6826- <command>DECLARE STATEMENT</command> declares SQL statement identifier.
6827- SQL statement identifier is associated with connection.
6826+ <command>DECLARE STATEMENT</command> declaresa SQL statement identifier
6827+ to be associated with connection.
68286828 </para>
68296829
68306830 <para>
6831- <command>DECLARE CURSOR</command> with a SQL statement identifier can be written before PREPARE.
6831+ <command>DECLARE CURSOR</command> with an SQL statement identifier
6832+ can be written before <command>PREPARE</command>.
68326833 </para>
68336834 </refsect1>
68346835
@@ -6843,7 +6844,8 @@ EXEC SQL [ AT <replaceable class="parameter">connection_name</replaceable> ] DEC
68436844 A database connection name established by the <command>CONNECT</command> command.
68446845 </para>
68456846 <para>
6846- If AT clause is omitted, an SQL statement identifier is associated with the DEFAULT connection.
6847+ If the <literal>AT</literal> clause is omitted, the SQL statement
6848+ identifier is associated with the <literal>DEFAULT</literal> connection.
68476849 </para>
68486850 </listitem>
68496851 </varlistentry>
@@ -6854,7 +6856,8 @@ EXEC SQL [ AT <replaceable class="parameter">connection_name</replaceable> ] DEC
68546856 <term><replaceable class="parameter">statement_name</replaceable></term>
68556857 <listitem>
68566858 <para>
6857- The name of a SQL statement identifier, either as an SQL identifier or a host variable.
6859+ The name of the SQL statement identifier, either as an SQL identifier
6860+ or a host variable.
68586861 </para>
68596862 </listitem>
68606863 </varlistentry>
@@ -6864,26 +6867,27 @@ EXEC SQL [ AT <replaceable class="parameter">connection_name</replaceable> ] DEC
68646867 <refsect1>
68656868 <title>Notes</title>
68666869 <para>
6867- AT clause can be used at other dynamic SQL statements. The following table
6868- gives the connected database when AT clause is used at DECLARE STATEMENT
6869- and other dynamic statements.
6870+ The <literal>AT</literal> clause can be used with both
6871+ <command>DECLARE STATEMENT</command> and other dynamic SQL statements.
6872+ The following table illustrates how it affects the selected database
6873+ connection.
68706874 </para>
68716875 <table tocentry="1" id="ecpg-declare-statement-table">
68726876 <title>Scenario</title>
68736877 <tgroup cols="4">
68746878 <thead>
68756879 <row>
68766880 <entry>
6877- Using Scenario
6881+ Usage Scenario
68786882 </entry>
68796883 <entry>
6880- Declare Statement
6884+ DECLARE STATEMENT
68816885 </entry>
68826886 <entry>
68836887 Other Dynamic Statements
68846888 </entry>
68856889 <entry>
6886- Executed Database
6890+ Target Database
68876891 </entry>
68886892 </row>
68896893 </thead>
@@ -6893,10 +6897,10 @@ EXEC SQL [ AT <replaceable class="parameter">connection_name</replaceable> ] DEC
68936897 1
68946898 </entry>
68956899 <entry>
6896- WithoutAT clause
6900+ Without<literal>AT</literal>
68976901 </entry>
68986902 <entry>
6899- WithoutAT clause
6903+ Without<literal>AT</literal>
69006904 </entry>
69016905 <entry>
69026906 Default connection
@@ -6907,10 +6911,10 @@ EXEC SQL [ AT <replaceable class="parameter">connection_name</replaceable> ] DEC
69076911 2
69086912 </entry>
69096913 <entry>
6910- Using AT clause connecting at con1
6914+ With <literal>AT</literal> that connects to <literal> con1</literal>
69116915 </entry>
69126916 <entry>
6913- WithoutAT clause
6917+ Without<literal>AT</literal>
69146918 </entry>
69156919 <entry>
69166920 con1
@@ -6921,10 +6925,10 @@ EXEC SQL [ AT <replaceable class="parameter">connection_name</replaceable> ] DEC
69216925 3
69226926 </entry>
69236927 <entry>
6924- Using AT clause connecting at con1
6928+ With <literal>AT</literal> that connects to <literal> con1</literal>
69256929 </entry>
69266930 <entry>
6927- Using AT clause connecting at con2
6931+ With <literal>AT</literal> that connects to <literal> con2</literal>
69286932 </entry>
69296933 <entry>
69306934 con1
@@ -6935,10 +6939,10 @@ EXEC SQL [ AT <replaceable class="parameter">connection_name</replaceable> ] DEC
69356939 4
69366940 </entry>
69376941 <entry>
6938- WithoutAT clause
6942+ Without<literal>AT</literal>
69396943 </entry>
69406944 <entry>
6941- Using AT clause connecting at con2
6945+ With <literal>AT</literal> that connects to <literal> con2</literal>
69426946 </entry>
69436947 <entry>
69446948 con2
@@ -6948,7 +6952,7 @@ EXEC SQL [ AT <replaceable class="parameter">connection_name</replaceable> ] DEC
69486952 </tgroup>
69496953 </table>
69506954 <para>
6951- In scenario 4, DECLARE STATEMENT will be ignored.
6955+ In scenario 4,<command> DECLARE STATEMENT</command> will be ignored.
69526956 </para>
69536957 </refsect1>
69546958