From ee20e2d0380e3f4f87c0ea386c7365056473d6ad Mon Sep 17 00:00:00 2001
From: "Muhammad N. Fadhil" <34566369+MuhammadNFadhil@users.noreply.github.com>
Date: Mon, 15 Jul 2024 21:57:03 +0300
Subject: [PATCH] Fixed typos in Atomic docstring.

---
 django/db/transaction.py | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/django/db/transaction.py b/django/db/transaction.py
index 4150cbcbbe2..0c2eee8e736 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.
     """