Merge pull request #23418 from abpframework/auto-merge/rel-9-2/3905

Merge branch rel-9.3 with rel-9.2

docs/en/framework/architecture/multi-tenancy/index.md

@@ -42,6 +42,8 @@ ABP supports all the following approaches to store the tenant data in the databa
 
 [Saas module (PRO)](../../../modules/saas.md) allows you to set a connection string for any tenant (as optional), so you can achieve any of the approaches.
 
+> You can see the community article *[Multi-Tenancy with Separate Databases in .NET and ABP Framework](https://abp.io/community/articles/multitenancy-with-separate-databases-in-dotnet-and-abp-51nvl4u9)* for more details about different database architectures with practical implementation details.
+
 ## Usage
 
 Multi-tenancy system is designed to **work seamlessly** and make your application code **multi-tenancy unaware** as much as possible.
@@ -443,8 +445,9 @@ The [Tenant Management module](../../../modules/tenant-management.md) provides a
 ### A note about separate database per tenant approach in open source version
 
 While ABP fully supports this option, managing connection strings of tenants from the UI is not available in open source version. You need to have [Saas module (PRO)](../../../modules/saas.md).
-Alternatively you can implement this feature yourself by customizing the tenant management module and tenant application service to create and migrate the database on the fly.
+Alternatively, you can implement this feature yourself by customizing the tenant management module and tenant application service to create and migrate the database on the fly.
 
 ## See Also
 
 * [Features](../../infrastructure/features.md)
+* [Article: Multi-Tenancy with Separate Databases in .NET and ABP Framework](https://abp.io/community/articles/multitenancy-with-separate-databases-in-dotnet-and-abp-51nvl4u9)