From bae23d7582d7c65ba07ae2ff591a5590cdf64b9b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ya=C4=9Fmur=20=C3=87elik?=
 <157795849+yagmurcelk@users.noreply.github.com>
Date: Thu, 6 Feb 2025 14:23:26 +0300
Subject: [PATCH] Update POST.md

---
 .../POST.md                                                     | 2 --
 1 file changed, 2 deletions(-)

diff --git a/docs/en/Community-Articles/2025-01-24-Understanding-Transactions-in-ABP-Unit-Of-Work/POST.md b/docs/en/Community-Articles/2025-01-24-Understanding-Transactions-in-ABP-Unit-Of-Work/POST.md
index 49a75b2a25..929203c6a0 100644
--- a/docs/en/Community-Articles/2025-01-24-Understanding-Transactions-in-ABP-Unit-Of-Work/POST.md
+++ b/docs/en/Community-Articles/2025-01-24-Understanding-Transactions-in-ABP-Unit-Of-Work/POST.md
@@ -2,8 +2,6 @@
 
 [The Unit of Work](https://en.wikipedia.org/wiki/Unit_of_work) is a software design pattern that maintains a list of objects affected by a business transaction and coordinates the writing out of changes and the resolution of concurrency problems to ensure that all changes are made within a single transaction. 
 
-![pic](./pic.png)
-
 ## Transaction Management Overview
 
 One of the primary responsibilities of the Unit of Work is managing database transactions. It provides the following transaction management features: