[Zope3-checkins] CVS: Zope3/src/transaction - _transaction.py:1.1.2.3

[Tim Peters]

Update of /cvs-repository/Zope3/src/transaction
In directory cvs.zope.org:/tmp/cvs-serv15617/src/transaction

Modified Files:
      Tag: jeremy-txn-branch
	_transaction.py 
Log Message:
Minor grammar changes in docstrings.


=== Zope3/src/transaction/_transaction.py 1.1.2.2 => 1.1.2.3 ===
--- Zope3/src/transaction/_transaction.py:1.1.2.2	Fri Mar 19 15:28:23 2004
+++ Zope3/src/transaction/_transaction.py	Fri Mar 19 15:46:03 2004
@@ -48,7 +48,7 @@
 Subtransactions add a lot of complexity to the transaction
 implementation.  Some resource managers support subtransactions, but
 they are not required to.  (ZODB Connection is the only standard
-resource manager that supports subtransactions.)  Resources managers
+resource manager that supports subtransactions.)  Resource managers
 that do support subtransactions implement abort_sub() and commit_sub()
 methods and support a second argument to tpc_begin().
 
@@ -58,7 +58,7 @@
 or tpc_abort() call applies just to that subtransaction.
 
 Once a resource manager is involved in a subtransaction, all
-subsequent transactions will be treated as subtransaction until
+subsequent transactions will be treated as subtransactions until
 abort_sub() or commit_sub() is called.  abort_sub() will undo all the
 changes of the subtransactions.  commit_sub() will begin a top-level
 transaction and store all the changes from subtransactions.  After
@@ -68,7 +68,7 @@
 If the resource manager does not support subtransactions, nothing
 happens when the subtransaction commits.  Instead, the resource
 manager is put on a list of managers to commit when the actual
-top-level transaction commits.  If this happen, it will not be
+top-level transaction commits.  If this happens, it will not be
 possible to abort subtransactions.
 
 Two-phase commit