From 11fb4c0b542f58d5d408089afcf31e03ee649217 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sinan=20=C3=96zt=C3=BCrk?= Date: Wed, 14 Feb 2024 16:58:06 +0300 Subject: [PATCH] Update Localization.md --- docs/en/UI/Angular/Localization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/UI/Angular/Localization.md b/docs/en/UI/Angular/Localization.md index f7b0df8ba4..b8de3ad353 100644 --- a/docs/en/UI/Angular/Localization.md +++ b/docs/en/UI/Angular/Localization.md @@ -113,7 +113,7 @@ this.localizationService.get({ ## UI Localizations -Localizations can be determined on backend side. Angular UI gets the localizations from the `application-configuration` API's response. You can also determine localizations on the UI side. +Localizations can be determined on backend side. Angular UI gets the localizations resources from the `application-localization` API's response and merges these resources with `configuration state` in [`ConfigStateService`](Config-State-Service.md). You can also determine localizations on the UI side. See an example: