11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.360 2005/08/24 19:34 :33 momjian Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.361 2005/08/24 19:41 :33 momjian Exp $
33
44Typical markup:
55
66[A-Z][A-Z ]+[A-Z] <command>
77[A-Za-z_][A-Za-z0-9_]+() <function>
88[A-Za-z_]/[A-Za-z_]+ <filename>
99PostgreSQL <productname>
10- pg_[A-Za-z0-9_] <appication >
10+ pg_[A-Za-z0-9_] <application >
1111[A-Z][A-Z] <type>, <envar.
1212 <literal>
1313&<> use &
@@ -166,9 +166,9 @@ pg_[A-Za-z0-9_] <appication>
166166 <listitem>
167167 <para>
168168 Moving pgautovacuum from <filename>/contrib</> allows it to be
169- automatically started andstoped in sync with the database
169+ automatically started andstopped in sync with the database
170170 server, and allows for pgautovacuum to be configured from
171- postgresql.conf.
171+ <filename> postgresql.conf</> .
172172 </para>
173173 </listitem>
174174 </varlistentry>
@@ -271,8 +271,8 @@ pg_[A-Za-z0-9_] <appication>
271271 <productname>PostgreSQL</productname> project is planning to
272272 remove the special meaning of backslashes in strings. For
273273 backward compatibility and for users who want special backslash
274- procesing , a new string type will be created. This new string
275- type is formed by having an Epreceed the single quote that
274+ processing , a new string type will be created. This new string
275+ type is formed by having an Eprecede the single quote that
276276 starts the string, e.g. <literal>E'hi\n'</>. While this release
277277 does not change the handling of backslashes in strings, it does
278278 add several new GUC variables to help users migrate applications
@@ -616,7 +616,7 @@ pg_[A-Za-z0-9_] <appication>
616616 <para>
617617 Using <command>ALTER USER</> and <command>ALTER DATABASE</>,
618618 limits can now be enforced on the maximum number of users who
619- can connect as as a specificuesr or to a specific database.
619+ can connect as as a specificuser or to a specific database.
620620 Setting the limit to zero disables user or database connections.
621621 </para>
622622 </listitem>
@@ -1368,7 +1368,7 @@ pg_[A-Za-z0-9_] <appication>
13681368 exception (Pavel Stehule)
13691369 </para>
13701370 <para>
1371- These variables are onlyaccessable inside exception blocks.
1371+ These variables are onlyaccessible inside exception blocks.
13721372 </para>
13731373 </listitem>
13741374
@@ -1478,7 +1478,7 @@ pg_[A-Za-z0-9_] <appication>
14781478 </para>
14791479 <para>
14801480 This is basically implemented by wrapping every statement in a
1481- subtransaction .
1481+ sub-transaction .
14821482 </para>
14831483 </listitem>
14841484
@@ -1710,7 +1710,7 @@ pg_[A-Za-z0-9_] <appication>
17101710
17111711 <listitem>
17121712 <para>
1713- Modify <filename>postgresql.conf</> to usedocumention defaults
1713+ Modify <filename>postgresql.conf</> to usedocumentation defaults
17141714 <literal>on</>/<literal>off</> rather than
17151715 <literal>true</>/<literal>false</> (Bruce)
17161716 </para>
@@ -1793,7 +1793,7 @@ pg_[A-Za-z0-9_] <appication>
17931793
17941794 <listitem>
17951795 <para>
1796- Implemention of OpenPGP symmetric-key and public-key encryption
1796+ implementation of OpenPGP symmetric-key and public-key encryption
17971797 </para>
17981798 <para>
17991799 Supported are both RSA and Elgamal public-key algorithms.
@@ -1802,7 +1802,7 @@ pg_[A-Za-z0-9_] <appication>
18021802
18031803 <listitem>
18041804 <para>
1805- Standalone build: include SHA256/384/512 hashes, Fortuna PRNG
1805+ Stand alone build: include SHA256/384/512 hashes, Fortuna PRNG
18061806 </para>
18071807 </listitem>
18081808
@@ -1872,7 +1872,7 @@ pg_[A-Za-z0-9_] <appication>
18721872
18731873 <para>
18741874 The lesser problem is that the <filename>contrib/tsearch2</> module
1875- creates several functions that aremisdeclared to return
1875+ creates several functions that areimproperly declared to return
18761876 <type>internal</> when they do not accept <type>internal</> arguments.
18771877 This breaks type safety for all functions using <type>internal</>
18781878 arguments.