Normalize ‘open transaction’

Author: geryogam

Doc/library/sqlite3.rst

@@ -634,25 +634,25 @@ Connection objects
 
    .. method:: commit()
 
-      Commit any pending transaction to the database.
+      Commit any open transaction to the database.
       If :attr:`autocommit` is ``True``, or there is no open transaction,
       this method does nothing.
       If :attr:`!autocommit` is ``False``, a new transaction is implicitly
-      opened if a pending transaction was committed by this method.
+      opened if an open transaction was committed by this method.
 
    .. method:: rollback()
 
-      Roll back to the start of any pending transaction.
+      Roll back to the start of any open transaction.
       If :attr:`autocommit` is ``True``, or there is no open transaction,
       this method does nothing.
       If :attr:`!autocommit` is ``False``, a new transaction is implicitly
-      opened if a pending transaction was rolled back by this method.
+      opened if an open transaction was rolled back by this method.
 
    .. method:: close()
 
       Close the database connection.
       If :attr:`autocommit` is ``False``,
-      any pending transaction is implicitly rolled back.
+      any open transaction is implicitly rolled back.
       If :attr:`!autocommit` is ``True`` or :data:`LEGACY_TRANSACTION_CONTROL`,
       no implicit transaction control is executed.
       Make sure to :meth:`commit` before closing
@@ -1273,7 +1273,7 @@ Connection objects
         This is currently the default value of :attr:`!autocommit`.
 
       Changing :attr:`!autocommit` to ``False`` will open a new transaction,
-      and changing it to ``True`` will commit any pending transaction.
+      and changing it to ``True`` will commit any open transaction.
 
       See :ref:`sqlite3-transaction-control-autocommit` for more details.
 
@@ -1474,7 +1474,7 @@ Cursor objects
       Execute the SQL statements in *sql_script*.
       If the :attr:`~Connection.autocommit` is
       :data:`LEGACY_TRANSACTION_CONTROL`
-      and there is a pending transaction,
+      and there is an open transaction,
       an implicit ``COMMIT`` statement is executed first.
       No other implicit transaction control is performed;
       any transaction control must be added to *sql_script*.
@@ -2392,7 +2392,7 @@ This means:
 * :mod:`!sqlite3` ensures that a transaction is always open,
   so :meth:`Connection.commit` and :meth:`Connection.rollback`
   will implicitly open a new transaction immediately after closing
-  the pending one.
+  the open one.
   :mod:`!sqlite3` uses ``BEGIN DEFERRED`` statements when opening transactions.
 * Transactions should be committed explicitly using :meth:`!commit`.
 * Transactions should be rolled back explicitly using :meth:`!rollback`.
@@ -2437,7 +2437,7 @@ new transactions are implicitly opened before
 ``INSERT``, ``UPDATE``, ``DELETE``, or ``REPLACE`` statements;
 for other statements, no implicit transaction handling is performed.
 Use the :meth:`~Connection.commit` and :meth:`~Connection.rollback` methods
-to respectively commit and roll back pending transactions.
+to respectively commit and roll back open transactions.
 You can choose the underlying `SQLite transaction behaviour`_ —
 that is, whether and what type of ``BEGIN`` statements :mod:`!sqlite3`
 implicitly executes –
@@ -2452,7 +2452,7 @@ The underlying SQLite library autocommit mode can be queried using the
 :attr:`~Connection.in_transaction` attribute.
 
 The :meth:`~Cursor.executescript` method implicitly commits
-any pending transaction before execution of the given SQL script,
+any open transaction before execution of the given SQL script,
 regardless of the value of :attr:`~Connection.isolation_level`.
 
 .. versionchanged:: 3.6