diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json
index 53c321fc1b..5ad707ce7c 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json
@@ -29,7 +29,7 @@
     "DomainDrivenDesignExplanation": "Designed and developed based on DDD patterns and principles. Provides a layered model for your application.",
     "Authorization": "Authorization",
     "AuthorizationExplanation": "Advanced authorization with user, role and fine-grained permission system. Built on Microsoft Identity library.",
-    "MultiTenancy": "Multi-Tenancy",
+    "MultiTenancy": "Multi-tenancy",
     "MultiTenancyExplanationShort": "SaaS applications made easy! Integrated multi-tenancy from database to UI.",
     "CrossCuttingConcerns": "Cross Cutting Concerns",
     "CrossCuttingConcernsExplanationShort": "Complete infrastructure for authorization, validation, exception handling, caching, audit logging, transaction management and more.",
@@ -1629,8 +1629,8 @@
     "ArchitecturalInfrastructure_Description": "SaaS applications, modular or microservice systems are most used enterprise software models. Building such systems not only requires a good understanding and experience but also requires a strong software infrastructure. Otherwise, you will find yourself spending a great effort to support these architectural details in your codebase.",
     "Modularity_THEPROBLEM_Description": "Building a truly modular system is not easy! All the aspects of the system (database, entities, APIs, UI pages/components) can be split into modules, and each module can be re-usable without others. The plain ASP.NET Core doesn't provide such a modular architecture. If you need it, you should think about it from scratch.",
     "Modularity_ABPSOLUTION_Description": "The ABP is born to be a modular application development structure. Every feature in the framework is developed to be compatible with modularity. Documentation and guides explain how to develop re-usable modules in a standard way.",
-    "SaaSMultiTenancy": "SaaS / Multi-Tenancy",
-    "SaaSMultiTenancy_THEPROBLEM_Description": "<a href=\"https://abp.io/docs/latest/framework/architecture/multi-tenancy\">Multi-Tenancy</a> is a common way to implement SaaS systems. However, implementing a consistent multi-tenant infrastructure may become complicated.",
+    "SaaSMultiTenancy": "SaaS / Multi-tenancy",
+    "SaaSMultiTenancy_THEPROBLEM_Description": "<a href=\"https://abp.io/docs/latest/framework/architecture/multi-tenancy\">Multi-tenancy</a> is a common way to implement SaaS systems. However, implementing a consistent multi-tenant infrastructure may become complicated.",
     "SaaSMultiTenancy_ABPSOLUTION_Description": "ABP provides a complete multi-tenant infrastructure and abstract complexity from your business code. Your application code will be mostly multi-tenancy aware, while the ABP automatically isolates the database, cache and other details of the tenants from each other. It supports single database, per tenant database and hybrid approaches. It properly configures the libraries like Microsoft Identity and OpenIddict, which are not normally multi-tenancy compatible.",
     "Microservices": "Microservices",
     "Microservices_THEPROBLEM_Description": "Building a microservice system requires many infrastructure details: Authenticating and authorizing applications and microservices and implementing asynchronous messaging and synchronous (Rest/GRPC) communication patterns between microservices are the most fundamental issues.",