summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMuhammad N. Fadhil <34566369+MuhammadNFadhil@users.noreply.github.com>2024-07-15 21:57:03 +0300
committerSarah Boyce <42296566+sarahboyce@users.noreply.github.com>2024-07-22 08:27:27 +0200
commitee20e2d0380e3f4f87c0ea386c7365056473d6ad (patch)
tree25f2c8931f33b540afccc78ae81f0d29472749d6
parent9cb8baa0c4fa2c10789c5c8b65f4465932d4d172 (diff)
Fixed typos in Atomic docstring.
-rw-r--r--django/db/transaction.py8
1 files changed, 4 insertions, 4 deletions
diff --git a/django/db/transaction.py b/django/db/transaction.py
index 4150cbcbbe..0c2eee8e73 100644
--- a/django/db/transaction.py
+++ b/django/db/transaction.py
@@ -156,7 +156,7 @@ class Atomic(ContextDecorator):
It's possible to disable the creation of savepoints if the goal is to
ensure that some code runs within a transaction without creating overhead.
- A stack of savepoints identifiers is maintained as an attribute of the
+ A stack of savepoint identifiers is maintained as an attribute of the
connection. None denotes the absence of a savepoint.
This allows reentrancy even if the same AtomicWrapper is reused. For
@@ -165,10 +165,10 @@ class Atomic(ContextDecorator):
Since database connections are thread-local, this is thread-safe.
- An atomic block can be tagged as durable. In this case, raise a
- RuntimeError if it's nested within another atomic block. This guarantees
+ An atomic block can be tagged as durable. In this case, a RuntimeError is
+ raised if it's nested within another atomic block. This guarantees
that database changes in a durable block are committed to the database when
- the block exists without error.
+ the block exits without error.
This is a private API.
"""