@@ -147,16 +147,16 @@ after the transaction is completed (either committed or aborted). Again, the
147147reasoning is that if a notify were delivered within a transaction that was
148148later aborted, one would want the notification to be undone somehow --- but
149149the backend cannot "take back" a notify once it has sent it to the frontend.
150- So notify events aredelivered only between transactions. The upshot of this
150+ So notify events are only delivered between transactions. The upshot of this
151151is that applications using <command>NOTIFY</command> for real-time signaling
152152should try to keep their transactions short.
153153
154154<para>
155- <command>NOTIFY</command> behavesrather like Unix signals in one important
156- respect: if the samenotify name is signaled multiple times in quick
155+ <command>NOTIFY</command> behaves like Unix signals in one important
156+ respect: if the samecondition name is signaled multiple times in quick
157157succession, recipients may get only one notify event for several executions
158158of <command>NOTIFY</command>. So it is a bad idea to depend on the number
159- of notifies received; instead use <command>NOTIFY</command> to wake up
159+ of notifies received. Instead, use <command>NOTIFY</command> to wake up
160160applications that need to pay attention to something, and use a database
161161object (such as a sequence) to keep track of what happened or how many times
162162it happened.
@@ -201,8 +201,8 @@ table name, even if syntactically valid as a name. That is no longer required.
201201
202202<para>
203203In <productname>Postgres</productname> releases prior to 6.4, the backend
204- PID delivered in a notify messageis always the PID of the frontend's own
205- backend. So itis not possible to distinguish one's own notifies from other
204+ PID delivered in a notify messagewas always the PID of the frontend's own
205+ backend. So itwas not possible to distinguish one's own notifies from other
206206clients' notifies in those earlier releases.
207207
208208</REFSECT2>