Merge branch 'development' into CTL-10.24.1-RNs

Author: MariaShaposhnikova

content/en/docs/apidocs-mxsdk/apidocs/deployment/pipelines-api.md

@@ -3,6 +3,7 @@ title: "Pipelines API"
 url: /apidocs-mxsdk/apidocs/pipelines-api/
 type: swagger
 description: "The Pipelines API sends requests to pipelines."
+restapi: true
 weight: 85
 ---
 

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

@@ -754,7 +754,6 @@ To provide translations for your design properties, create a file *locales/{lang
 
 These JSON files follow the format used by the i18next library, specifically v3. See the [the i18next JSON format documentation](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 align": "텍스트 정렬",

content/en/docs/apidocs-mxsdk/apidocs/governance/user-deactivation-api.md

@@ -78,4 +78,4 @@ The following steps lead to deactivating the user based on the UUID provided as
 
 ## API Reference
 
-{{< swaggerui src="/openapi-spec/user-deactivation-api.yaml" >}}
+{{< swaggerui src="/openapi-spec/user-deactivation-api.yaml" >}}

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/pluggable-widgets/_index.md

@@ -332,7 +332,7 @@ Translations for a pluggable widget can be provided in two ways: in the widget p
 
 ### 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 *en-US*, *ja-JP*, *ko-KR*, or *zh-CN*. Other files in the **locales** folder will be ignored. As a result, custom namespaces cannot be used. We recommend using *translation.json*, unless your .MPK contains multiple pluggable widgets. Note that if you use the widget ID as the file name, you will 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 cannot be used. We recommend using *translation.json*, unless your .MPK contains multiple pluggable widgets. Note that if you use the widget ID as the file name, you will 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. For more information, see [the i18nest JSON documentation](https://www.i18next.com/misc/json-format). 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 example:
 
@@ -347,7 +347,7 @@ These JSON files follow the format used by the i18next library, specifically v3.
 
 Translations for a pluggable widget can also be provided by a module. This can be useful when you would like to provide a module that has more than one pluggable widget, or if your pluggable widget uses one or more [/apidocs-mxsdk/apidocs/frontend/design-properties/](design properties).
 
-To achieve this, create a *locales/{language-code}/{widget ID}.json* file in the **Styling** folder of your module. You will 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 will look something like this example:
+To achieve this, create a *locales/{language-code}/{widget ID}.json* file in the **Styling** folder of your module. You will 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 will look something like this example:
 
 {{< 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" max-width=50% >}}
 

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-8/pluggable-widgets/_index.md

@@ -8,4 +8,3 @@ description: "This API helps you to understand pluggable widgets, how they exten
 ---
 
 The following Mendix 8 pluggable widget API documents are available here:
-

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-9/pluggable-widgets/_index.md

@@ -8,4 +8,3 @@ description: "This API helps you to understand pluggable widgets, how they exten
 ---
 
 The following Mendix 9 pluggable widget API documents are available here:
-

content/en/docs/control-center/entitlements/cloud-tokens.md

@@ -98,4 +98,4 @@ You can no longer purchase Legacy Cloud Resources Packs. You can now only purcha
 * Mendix Cloud Tokens are a specific type of Token used to access Cloud Resources in the Mendix Platform.
 * The number of Mendix Cloud Tokens required depends on the CRP you want.
 * You buy Tokens in advance, and can use them to obtain CRPs.
-* If you no longer need those resources, you can reuse the Token to obtain other CRPs, or keep it to be used later.
+* If you no longer need those resources, you can reuse the Token to obtain other CRPs, or keep it to be used later.