From 0f27139fda9912538e89afe1963b9d3418806db6 Mon Sep 17 00:00:00 2001
From: Mammad Yahyayev <66476643+mammadyahyayev@users.noreply.github.com>
Date: Sun, 1 Dec 2024 20:21:42 +0400
Subject: [PATCH] fix: Fix typo (#3100)

---
 unit-of-work/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/unit-of-work/README.md b/unit-of-work/README.md
index 5b490d296..4b82b7c8c 100644
--- a/unit-of-work/README.md
+++ b/unit-of-work/README.md
@@ -180,7 +180,7 @@ Here is the console output.
 
 ## When to Use the Unit Of Work Pattern in Java
 
-* he Unit of Work pattern is ideal for managing multiple database operations in Java that must be executed as a single transaction, ensuring data consistency and integrity.
+* The Unit of Work pattern is ideal for managing multiple database operations in Java that must be executed as a single transaction, ensuring data consistency and integrity.
 * Ideal in scenarios where changes to the business objects must be tracked and saved in a coordinated manner.
 * Useful when working with object-relational mapping (ORM) frameworks in Java such as Hibernate.