diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 34989f1dfacf5fc56f59469a9bc886e1b5735ce8..1b79c29f6e2d4735cc7e765e21b7bc53b8926e1b 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.91 2009/09/18 13:13:32 meskes Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.92 2009/11/30 14:47:37 momjian Exp $ -->
 
 <chapter id="ecpg">
  <title><application>ECPG</application> - Embedded <acronym>SQL</acronym> in C</title>
@@ -352,13 +352,13 @@ EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...;
 </programlisting>
    This option is particularly suitable if the application needs to
    use several connections in mixed order.
-      </para>
+  </para>
 
-      <para>
-      If your application uses multiple threads of execution, they cannot share a
-      connection concurrently. You must either explicitly control access to the connection
-      (using mutexes) or use a connection for each thread. If each thread uses its own connection,
-      you will need to use the AT clause to specify which connection the thread will use.
+  <para>
+   If your application uses multiple threads of execution, they cannot share a
+   connection concurrently. You must either explicitly control access to the connection
+   (using mutexes) or use a connection for each thread. If each thread uses its own connection,
+   you will need to use the AT clause to specify which connection the thread will use.
   </para>
 
   <para>