Update localization-system.md

docs/en/solution-templates/microservice/localization-system.md

@@ -18,6 +18,8 @@ Like the other fundamental feature modules ([Permission Management](permission-m
 
 ## Language Management
 
+> If the dynamic localization option is enabled, then the *Language Management Module** will be removed from the optional modules and a new microservice named `LanguageService` will be created. The `LanguageService` uses *Language Management Module* behind the scene.
+
 The *Administration* microservice provides a set of APIs to manage localization. The localization resources are defined in each microservice, and when a microservice starts, it registers its localization resources to the related localization tables automatically. After that, you can see the localization resources from the [language texts](../../modules/language-management.md#language-texts) and manage them.
 
 ![language-texts](images/language-management-language-texts-page.png)
@@ -30,9 +32,7 @@ When you create a new microservice solution, you can **enable dynamic localizati
 
 ![](./images/enable-dynamic-localization.png)
 
-When you enable this option, a new microservice named **LanguageService** will be added (with the language management module integrated) and you can use its `LanguageServiceResource` class to use the localization entries in your UI application. It's already configured in your final host application, so you don't need to make any configuration related to that and directly use it.
-
-> **Note:** When you enable this option, then the **Language Management Module** will be removed from the optional module list.
+When you enable this option, a new microservice named **LanguageService** will be added (with the language management module integrated) and you can use its `LanguageServiceResource` class to use the localization entries in your UI application. It's already configured in your final host application, so you don't need to make any configuration related to that. To define a new localization entry you can either use the language files in the `LanguageService` or update the already defined localization entries in the UI (on the *Language Texts* page).
 
 **Example:** You can inject the `IStringLocalizer<>` or `IHtmlLocalizer<>` services and use the localized values in your pages for MVC/Razor Pages UI:
 
@@ -171,4 +171,4 @@ public override void ConfigureServices(ServiceConfigurationContext context)
 }
 ```
 
-> Existing microservices in the solution don't contain the localization text. These localization resources are defined in their own modules. You can add new localization resources to the existing microservices by following the steps above.
+> Existing microservices in the solution don't contain the localization text. These localization resources are defined in their own modules. You can add new localization resources to the existing microservices by following the steps above.