More release-notes copy editing, from Neil Conway.

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index ea210768ccaa1d6f80c184232c4fee3e2fc1683c..f096e7f11ef3c5a39f1d72d5387d417276ffeccc 100644 (file)
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
 
 
 
@@ -1059,9 +1059,10 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.242 2003/11/15 20:01:11 tg
      Allow cursors outside transactions using WITH HOLD (Neil)
      
       In previous releases, cursors were removed at the end of the
-      transaction. Using WITH HOLD, the current
-      release allows cursors to remain readable after the creating
-      transaction.
+      transaction that created them. Cursors can now be created with
+      the WITH HOLD option, which allows them to
+      continue to be accessed after the creating transaction has
+      committed.
      
     
 
@@ -1091,16 +1092,18 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.242 2003/11/15 20:01:11 tg
      Properly handle SCROLL with cursors, or
      report an error (Neil)
      
-      Certain cursors can not be fetched backwards optimally. By
-      specifying SCROLL, extra work will be
-      performed to guarantee that the cursor can be fetched in reverse
-      or random order.
+      Allowing random access (both forward and backward scrolling) to
+      some kinds of queries cannot be done without some additional
+      work. If SCROLL is specified when the cursor
+      is created, this additional work will be performed. Furthermore,
+      if the cursor has been created with NO SCROLL,
+      no random access is allowed.
      
     
 
     
      
-      Implement SQL-compatible option FIRST,
+      Implement SQL-compatible options FIRST,
       LAST, ABSOLUTE n,
       RELATIVE n for
       FETCH and MOVE (Tom)
@@ -1151,7 +1154,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.242 2003/11/15 20:01:11 tg
      Make TRUNCATE transaction-safe (Rod)
      
       TRUNCATE can now be used inside a
-      transaction, and rolled back if the transaction aborts.
+      transaction. If the transaction aborts, the changes made by the
+      TRUNCATE are automatically rolled back.