From a545147d1ca2a3f3013605668442585efc2150d8 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:33:58 +0300
Subject: [PATCH] Update Post.md

---
 .../2024-09-01-Do-You-Need-MultiTenancy/Post.md                 | 2 --
 1 file changed, 2 deletions(-)

diff --git a/docs/en/Community-Articles/2024-09-01-Do-You-Need-MultiTenancy/Post.md b/docs/en/Community-Articles/2024-09-01-Do-You-Need-MultiTenancy/Post.md
index b80917f4c4..a294a1f2e6 100644
--- a/docs/en/Community-Articles/2024-09-01-Do-You-Need-MultiTenancy/Post.md
+++ b/docs/en/Community-Articles/2024-09-01-Do-You-Need-MultiTenancy/Post.md
@@ -2,8 +2,6 @@
 
 This article discusses whether you need a multi-tenancy architecture for your next project. Answer my critical questions to decide if multi-tenancy suits your application or not!
 
-![Cover image](cover.png)
-
 ## What’s Multi-tenancy?
 
 It’s an architectural approach to building SaaS solutions. In this model, the hardware and software resources are shared between tenants, and application data is virtually or physically isolated between tenants. Here, **the main goal is minimizing costs and maximizing customer count**.