docs: 3.3 release notes cleanup and other small fixes

diff --git a/docs/basic/transactions.rst b/docs/basic/transactions.rst
index 20dc76f3fc2cd3707dc3a775e4b361b36330bd08..f69b68acfbe06818ba61113443aa8523c7b6f116 100644 (file)
--- a/docs/basic/transactions.rst
+++ b/docs/basic/transactions.rst
@@ -309,8 +309,8 @@ Each `!Transaction` object exposes a `~Transaction.status` property allowing
 to inspect the current state of the transaction. This can be useful for
 debugging, logging, or implementing custom transaction management logic.
 
-The `!status` property is a `~psycopg.Transaction.Status` enum value:
-please check the enum documentation for the possible values.
+The `!status` property is a `psycopg.Transaction.Status` enum value:
+please check its documentation for the possible values.
 
 Here are a few examples of how to use the `!status` property:
 
@@ -346,7 +346,7 @@ Here are a few examples of how to use the `!status` property:
 
 The `!status` property remains accessible after the transaction context has
 exited, allowing you to check the final outcome of the transaction even after
-the `!with` block completes. This is particularly useful when you need to log
+the `!with` block has exited. This is particularly useful when you need to log
 transaction outcomes or implement retry logic based on the transaction status.
 
 

diff --git a/docs/basic/tstrings.rst b/docs/basic/tstrings.rst
index 15d5413e8a5edb3d381080cec8f393a0260871fd..ccd7f37eb701fa4c6662d666fa9b112159ca06fe 100644 (file)
--- a/docs/basic/tstrings.rst
+++ b/docs/basic/tstrings.rst
@@ -144,7 +144,7 @@ result in executing the statement ``NOTIFY "foo.bar", 'O''Reilly'``.
 Example: nested templates
 -------------------------
 
-A string template merges literal parts of the query with parameter. It is also
+A string template merges literal parts of the query with parameters. It is also
 possible to pass templates to templates in order to compose more and more
 complex and dynamic SQL statements.
 

diff --git a/docs/news.rst b/docs/news.rst
index 8136ca051ce1391c35d707c13ebc5d0a86a4b574..8ac93a2cd4b4b40920d3f2364708c84034ad16fd 100644 (file)
--- a/docs/news.rst
+++ b/docs/news.rst
@@ -19,8 +19,9 @@ Psycopg 3.3.0 (unreleased)
 - More flexible :ref:`composite adaptation<adapt-composite>`: it is now possible
   to adapt Python objects to PostgreSQL composites and back even if they are not
   sequences or if they take keyword arguments (:ticket:`#932`, :ticket:`#1202`).
-- Cursors are now *iterators*, not only *iterables*. This means you can call
-  ``next(cur)`` to fetch the next row (:ticket:`#1064`).
+- Cursors are now iterators_, not just iterables_. This means you can call
+  `next`\ ``(cur)`` or `anext`\ ``(cur)``, which is useful as a :ref:`type-safe
+  expression <typing-fetchone>` (:ticket:`#1064`).
 - Add `Cursor.set_result()` and `Cursor.results()` to move across the result
   sets of queries executed though `~Cursor.executemany()` or
   `~Cursor.execute()` with multiple statements (:tickets:`#1080, #1170`).
@@ -50,6 +51,9 @@ Psycopg 3.3.0 (unreleased)
 
 - Drop support for Python 3.8 (:ticket:`#976`) and 3.9 (:ticket:`#1056`).
 
+.. _iterators: https://docs.python.org/3/glossary.html#term-iterator
+.. _iterables: https://docs.python.org/3/glossary.html#term-iterable
+
 
 Current release
 ---------------