11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.153 2004/04/24 22:53:44 neilc Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.154 2004/04/24 22:58:40 neilc Exp $
33-->
44
55 <chapter id="libpq">
@@ -15,14 +15,14 @@ $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.153 2004/04/24 22:53:44 neilc Exp
1515
1616 <para>
1717 <application>libpq</application> is the <acronym>C</acronym>
18- application programmer's interface to
19- <productname>PostgreSQL</productname>. < application>libpq</application > is a set
20- of library functions that allow client programs to pass queries to the
21- <productname>PostgreSQL</productname> backend server and to receive the
22- results of these queries. <application>libpq</
application > is also the
23- underlying engine for several other <productname>PostgreSQL</
productname> 24- application interfaces, including those written for C++, TCL, Perl, Python
25- <application>ECPG</application>. So some aspects of <application>libpq</>'s behavior will be
18+ application programmer's interface to <productname>PostgreSQL</>.
19+ <application>libpq</> is a set of library functions that allow
20+ client programs to pass queries to the <productname>PostgreSQL</>
21+ backend server and to receive the results of these queries.
22+ <application>libpq</> is also the underlying engine for several
23+ other <productname>PostgreSQL</> application interfaces, including
24+ those written for C++, TCL, Perl, Python and <application>ECPG</>.
25+ So some aspects of <application>libpq</>'s behavior will be
2626 important to you if you use one of those packages.
2727 </para>
2828
