Change examples to Korean as German is not supported

Author: MendixBart

content/en/docs/apidocs-mxsdk/apidocs/frontend/design-properties.md

@@ -746,25 +746,25 @@ When the **Small** option is selected, the `borderRadiusSmall` class will be app
 
 Design properties can be translated to match the users preferred user interface language. This includes the name of the design property, its description and any of its options, if it has any, as shown in the styling properties panel. The provided translations do not affect the behavior of the design property.
 
-To provide translations for your design properties, create a file *locales/{language-code}/translation.json* in the Styling folder of your module. The language code can be any of the user interface languages supported by Studio Pro, such as *de-DE*, *en-US*, *ja-JP*, *ko-KR* or *zh-CN*. Other files in the *locales/{language-code}* folders will be ignored. As a result, custom namespaces can't be used. The resulting structure could look like this:
+To provide translations for your design properties, create a file *locales/{language-code}/translation.json* in the Styling folder of your module. The language code can be any of the user interface languages supported by Studio Pro, such as *en-US*, *ja-JP*, *ko-KR* or *zh-CN*. Other files in the *locales/{language-code}* folders will be ignored. As a result, custom namespaces can't be used. The resulting structure could look like this:
 
 {{< figure src="/attachments/apidocs-mxsdk/apidocs/design-properties/translations.png" alt="A translation.json file in the Styling/locales/de-DE folder" class="no-border" >}}
 
-These json files follow the format used by the I18next library, specifically v3. See [their documentation on the format](https://www.i18next.com/misc/json-format) for more information. For example to translate a design property with the name *Text align* with the options *left*, *center* and *right*, the contents of *locales/de-DE/translation.json* might look something like this:
+These json files follow the format used by the I18next library, specifically v3. See [their documentation on the format](https://www.i18next.com/misc/json-format) for more information. For example to translate a design property with the name *Text align* with the options *left*, *center* and *right*, the contents of *locales/ko-KR/translation.json* might look something like this:
 
 
 ```json
 {
-    "Text algin": "Text ausrichten",
-    "left": "links",
-    "center": "zentrieren",
-    "right": "rechts"
+    "Text align": "텍스트 정렬",
+    "left": "왼쪽",
+    "center": "센터",
+    "right": "오른쪽"
 }
 ```
 
 All design properties and options with the same name will be translated the same way, even if they are defined in different modules. When two or more modules define a translation for the same design property or design property option, the one used is not guaranteed to be the same as the one outlined in [Extending or Overriding Design Properties of Other Modules](#extend-existing-design-properties). As a result, it is recommended to only translate design properties and design property options in the same module in which they are defined.
 
-If a translation is not available, the names and descriptions as defined in the *design-properties.json* are used as a fallback instead. For example, the user changes their settings to work with Studio Pro in German, but the module does not have a *locales/de-DE/translation.json* file. This can also happen if the name of a design property, any of its options or descriptions are missing from the corresponding *translation.json* file.
+If a translation is not available, the names and descriptions as defined in the *design-properties.json* are used as a fallback instead. For example, the user changes their settings to work with Studio Pro in Korean, but the module does not have a *locales/ko-KR/translation.json* file. This can also happen if the name of a design property, any of its options or descriptions are missing from the corresponding *translation.json* file.
 
 {{% alert color="warning" %}}
 When adding translations for existing design properties, do not change the name of existing design properties or their options as defined in *design-properties.json*. Those names cannot be changed easily when there are apps already using them. See the [Renaming Design Properties](#old-names) section.

content/en/docs/apidocs-mxsdk/apidocs/frontend/pluggable-widgets/_index.md

@@ -336,14 +336,14 @@ If there's no translations available for a users preferred user interface langua
 
 ### Providing Translations in a Pluggable Widget Package
 
-To support a translation for a specific language and locale, create a *locales/{language-code}/{widget ID}.json* or *locales/{language-code}/translation.json* file. The language code can be any of the user interface languages supported by Studio Pro, such as *de-DE*, *en-US*, *ja-JP*, *ko-KR* or *zh-CN*. Other files in the *locales* folder will be ignored. As a result, custom namespaces can't be used. It's advised to use *translation.json*, unless your mpk contains multiple pluggable widgets. Note that if you use the widget ID as the file name, you'll have to replace any spaces and illegal path characters (if there are any) with underscores. The file name should be all lower case. For example: if your widget ID is *%My Pluggable Widget%*, the name of the file should be *_my_pluggable_widget_.json*.
+To support a translation for a specific language and locale, create a *locales/{language-code}/{widget ID}.json* or *locales/{language-code}/translation.json* file. The language code can be any of the user interface languages supported by Studio Pro, such as *en-US*, *ja-JP*, *ko-KR* or *zh-CN*. Other files in the *locales* folder will be ignored. As a result, custom namespaces can't be used. It's advised to use *translation.json*, unless your mpk contains multiple pluggable widgets. Note that if you use the widget ID as the file name, you'll have to replace any spaces and illegal path characters (if there are any) with underscores. The file name should be all lower case. For example: if your widget ID is *%My Pluggable Widget%*, the name of the file should be *_my_pluggable_widget_.json*.
 
-These json files follow the format used by the I18next library, specifically v3. See [their documentation on the format](https://www.i18next.com/misc/json-format) for more information. For example to translate a widget with the name *Text Box* that has a property *length*, the contents of *locales/de-DE/translation.json* might look something like this:
+These json files follow the format used by the I18next library, specifically v3. See [their documentation on the format](https://www.i18next.com/misc/json-format) for more information. For example to translate a widget with the name *Text Box* that has a property *length*, the contents of *locales/ko-KR/translation.json* might look something like this:
 
 ```json
 {
-    "Text Box": "Textfeld",
-    "length": "Länge"
+    "Text Box": "텍스트 상자",
+    "length": "텍스트 길이"
 }
 ```
 
@@ -353,7 +353,7 @@ Translations for a pluggable widget can also be provided by a module. This can b
 
 To achieve this: create a *locales/{language-code}/{widget ID}.json* file in the Styling folder of your module. You'll have to replace any spaces and illegal path characters (if there are any) with underscores. The file name should be all lower case. For example: if your widget ID is *%My Pluggable Widget%*, the name of the file should be *_my_pluggable_widget_.json*. In addition, create a *locales/metadata.json* file. The resulting structure could look like this:
 
-{{< figure src="attachments/apidocs-mxsdk/apidocs/pluggable-widgets/translations.png" alt="A metadata.json file in the Styling/locales folder and a custom.widget.id.json file in the Styling/locales/de-DE folder" class="no-border" >}}
+{{< figure src="attachments/apidocs-mxsdk/apidocs/pluggable-widgets/translations.png" alt="A metadata.json file in the Styling/locales folder and a custom.widget.id.json file in the Styling/locales/ko-KR folder" class="no-border" >}}
 
 The contents of *locales/metadata.json* should be: