8
0
Pārlūkot izejas kodu

Applied suggestions from code review

Co-authored-by: Szymon Cofalik <s.cofalik@cksource.com>
Maciej Bukowski 5 gadi atpakaļ
vecāks
revīzija
abb7a227ee

+ 1 - 1
docs/features/ui-language.md

@@ -146,7 +146,7 @@ If you build CKEditor 5 from scratch or integrate it directly into your applicat
 	// ...
 	```
 
-3. Run webpack. The CKEditor 5 plugin for webpack will emit additional files for each language specified in the `additionalLanguages` option. They will contain translations for messages from the {@link module:utils/locale~Locale#t `t()` function} calls. The files will be created in the `'translations'` directory (or another one if the `outputDirectory` option is specified). Translations from the language specified in the `language` option will be automatically included in the build.
+3. Run webpack. The CKEditor 5 plugin for webpack will emit additional files for each language specified in the `additionalLanguages` option. They will contain translations for messages from the {@link module:utils/locale~Locale#t `t()` function} calls. The files will be created in the `translations` directory (or another one if the `outputDirectory` option is specified). Translations from the language specified in the `language` option will be automatically included in the build.
 
 4. If you want to change the language after the build ends, you will need to edit the `index.html` file, add the translation file, and set the UI language to the target one.
 

+ 1 - 1
docs/framework/guides/architecture/ui-library.md

@@ -12,7 +12,7 @@ The standard UI library of CKEditor 5 is [`@ckeditor/ckeditor5-ui`](https://www.
 Views use [templates](#templates) to build the UI. They also provide observable interfaces that other features (e.g. {@link framework/guides/architecture/core-editor-architecture#plugins plugins}, {@link framework/guides/architecture/core-editor-architecture#commands commands}, etc.) can use to change the DOM without any actual interaction with the native API.
 
 <info-box>
-	All views can be localized using the `locale` instance on which they are created. Check the {@link framework/guides/deep-dive/localization localization guide} to see how to use the `t()` function coming from the `locale` instance.
+	All views can be localized using the `locale` instance with which they were created. Check the {@link framework/guides/deep-dive/localization localization guide} to see how to use the `t()` function available in the `locale` instance.
 </info-box>
 
 ### Definition

+ 2 - 2
docs/framework/guides/deep-dive/localization.md

@@ -8,7 +8,7 @@ category: framework-deep-dive
 
 All CKEditor 5 WYSIWYG editor features support message localization. It means that the user interface of any feature can be translated into various languages and regions depending on the user's preferences.
 
-Starting with the release of CKEditor 5 v19.0.0 as well as CKEditor 5 development tools we opened the translation system to third-party plugins. We also provided a way for adding missing or fixing invalid translations to the editor and introduced support for translating plural forms.
+CKEditor 5 translation system is opened to third-party plugins. Any custom features that you might introduce can be localized. We also provided a way for adding missing or overwriting existing translations and we support translating plural forms.
 
 <info-box warning>
 	Make sure to use up-to-date CKEditor 5 development tool packages. Older versions of the tools do not provide support for features described in this guide.
@@ -49,7 +49,7 @@ As the first argument, the `t()` function accepts either a string literal or an
 
 As the second argument, the translation function accepts a value or an array of values. These values will be used to fill the placeholders in more advanced translation scenarios. If the `plural` property is specified, the first value will be used as the quantity determining the plural form.
 
-When using the `t()` function, you can create your own *localizable messages* or reuse *messages* created in CKEditor 5 packages that your project depends on. In case of reusing *messages*, you will not need to worry about translating them as all work will be done by the CKEditor 5 team and [Transifex translators](https://www.transifex.com/ckeditor/ckeditor5/) anyway. Obviously, your help in translating will still be appreciated!
+When using the `t()` function, you can create your own *localizable messages* or reuse *messages* created in CKEditor 5 packages that your project depends on. In case of reusing *messages*, you will not need to worry about translating them as all work will be done by the CKEditor 5 team and [Transifex translators](https://www.transifex.com/ckeditor/ckeditor5/). Obviously, your help in translating will still be appreciated!
 
 For simple *localizable messages*, use the string form for simplicity: