From 773bf300276f05ac721ba110537812276003a1ca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ya=C4=9Fmur=20=C3=87elik?=
 <157795849+yagmurcelk@users.noreply.github.com>
Date: Wed, 5 Feb 2025 15:50:04 +0300
Subject: [PATCH] Update background-jobs-vs-background-workers.md

---
 .../background-jobs-vs-background-workers.md                    | 2 --
 1 file changed, 2 deletions(-)

diff --git a/docs/en/Community-Articles/2025-01-03-ABP-Background-Workers-vs-Jobs/background-jobs-vs-background-workers.md b/docs/en/Community-Articles/2025-01-03-ABP-Background-Workers-vs-Jobs/background-jobs-vs-background-workers.md
index 5677b74335..43a3c3a813 100644
--- a/docs/en/Community-Articles/2025-01-03-ABP-Background-Workers-vs-Jobs/background-jobs-vs-background-workers.md
+++ b/docs/en/Community-Articles/2025-01-03-ABP-Background-Workers-vs-Jobs/background-jobs-vs-background-workers.md
@@ -1,7 +1,5 @@
 # ABP Framework: Background Jobs vs Background Workers — When to Use Which?
 
-![cover](cover.png)
-
 In the ABP Framework, **Background Jobs** and **Background Workers** serve different purposes but can sometimes seem interchangeable. Sometimes it can be confusing. Let’s clarify their differences, and I'll show you some real-world cases to help you understand how to decide between these two. We have official documents for these:
 
 📕 **Background Workers ABP Document**  https://abp.io/docs/latest/framework/infrastructure/background-workers