diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md
index 5567b42aad..e63db935a5 100644
--- a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md
+++ b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md
@@ -22,7 +22,7 @@ In the shared database model, all the application data stored in a single physic
 
 ![single-shared-database](single-shared-database.png)
 
-This is the default behavior when you [create a new ABP application](https://abp.io/docs/latest/get-started), because it is simple to begin with and proper for must applications.
+This is the default behavior when you [create a new ABP application](https://abp.io/docs/latest/get-started), because it is simple to begin with and proper for most applications.
 
 In this model, a single database table may contain data of multiple tenants. Each row in these tables have a `TenantId` field which is used to distinguish the tenant data and isolate a tenant's data from other tenant users. To make your entities multi-tenant aware, all you have to do is to implement the `IMultiTenant` interface provided by the ABP Framework.