Proofread linter

Author: MarkvanMents

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/releasenotes/studio-pro/11/11.0.md

@@ -22,14 +22,12 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro
 * We introduced a new message for Maia generation sessions. It allows to either navigate back to the document related to a session or create a new **Generate** session for the currently active document.
 * We updated the filter button in the **Go to...** dialog to show active filters if any.
 * In the logic editors, pressing <kbd>Shift</kbd> while dragging objects from the **App Explorer**, **Toolbox** or the toolbar will disable snapping the objects to other objects.
-
 * We released workflow interrupting [boundary events](/refguide/workflow-boundary-events/) for general availability (GA). With this new type of boundary event, the workflow can interrupt modeled flows when the timer has expired and start an alternate flow.
 * We now support recurrence on non-interrupting boundary events. You can set an initial execution time, specify how many times the boundary event should recur, and define the interval between executions, which can range from minutes to months.
 * The feature to access online data in offline apps is now generally available. For more information, see [Offline-First Data](/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/#intro).
 * We introduced the OQL Query, a user-friendly interface that represents a view entity and enables users to define and manage OQL queries. 
 * We enabled native mobile builds for PMP customers.
 * We updated the version of Mendix apps that can be opened with Mendix 11.0.0 and above. Now to open (and if necessary to convert) an app in Mendix 11.0.0 and above, the app should be Mendix version 10.21.0 or above.
-
 * You can now use the <kbd>Back</kbd> and <kbd>Forward</kbd> mouse buttons to navigate through the history of active editors in Studio Pro—if your mouse has them.
 * We added support for retrieving the CSRF token using the new client API. You can now use `getCSRFToken` from `mx-api/session` to get the token, which is required when calling secured REST services.
 * We added a selector to the **Edit view entity** dialog that allows you to specify a user for who you want to see the live preview. This allows you to preview queries that use the `[%CurrentUser%]` token.
@@ -54,7 +52,6 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro
 ### Improvements
 
 * We improved the validation of the default value for an AutoNumber attribute in Studio Pro. It now allows values larger than 2,147,483,647. (Ticket 240734).
-
 * The text in the dialog displayed when a page cannot be found is now translatable. (Ticket 242035)
 * We improved the performance of workflow versioning conflict analysis for workflows with many nested outcome-based activities. (Ticket 242615)
 * We added error logging when a page fails to be loaded in the React client when navigating to it. This can happen when a page includes a widget with a corrupted bundle. (Ticket 245516)
@@ -81,7 +78,6 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro
 * We aligned the preview values of page and snippet variables between structure and design mode.
 * We made it easier to use widget action variables when configuring parameter mappings for **Call a Microflow** and **Call a Nanoflow** actions.
 * We changed the default **Role Type** in the **Accessibility** section of **Properties** from the **Link Button** to **Link.** This **Role Type** was set to **Link Button** by default while functionally it is a link.
-
 * In the Consumed REST Service, it is now possible to define the body content in different ways. You can select **Create Entity (JSON)** that allows you to convert the JSON file to an entity and use that as input for your **Send REST Request** activity. You can also select **Use as template** to send text content. Parameters in the text are supported by surrounding them with curly braces, for example `{my_param}`.
 * We added a progress indicator to the **Create entity** button in the response and the body structure of Consumed REST service document.
 * We added a new entity to the System module called **WorkflowEndedUserTask**. Whenever a workflow user task ends (including both **Finished** and **Aborted**) a data about the task is saved in this new entity.
@@ -187,7 +183,6 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro
 * We fixed the issue that microflows using online data where not possible in native pages.
 * We fixed an issue where converting a nanoflow to a microflow did not trigger a warning when the nanoflow was used in a native layout.
 * We block starting the app when there are still file documents on the local file system which are created before Mendix 5.12. Make sure all files are migrated before upgrading to this version. Files are migrated automatically in the background when running apps on Mendix versions since 8.14.0.
-
 * We fixed an issue that caused all the widgets to shift to the right in Design mode on React Client enabled.
 * We fixed an issue where metadata got corrupted when special characters were present.
 * We fixed an issue where the **Revert change** option was missing for deleted files in the **Changes** pane.
@@ -251,7 +246,6 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro
 * We deprecated the Document templates and the **Generate Document** actions. For information on migrating to supported methods, see [Document Templates](/refguide/document-templates/).
 * We deprecated the method `com.mendix.core.actionmanagement.EventActionInfo#representsFunction()`. Use the `function()` method to check whether the `EventActionInfo` instance represents a function.
 * We deprecated the following methods of the class `com.mendix.core.actionmanagement.internal.InternalCoreAction`: `addDatavalidationFeedback(IMendixIdentifier, Map<String, String>)`, `addDataValidationFeedback(DataValidationInfo)`, `handleConcurrentExecution()`, `setEventObjects(List<IMendixObject>)`, `setMetaInfo(JSONObject)`, `setActionName(String)`, `getException()`, `setException(Exception)`, `getState()`, `setState(ActionState)`, `setAllowsConcurrentExecution(Boolean)`, `clone()`. There is no replacement as these method were meant for internal usage only.
-
 * We deprecated the `FeedbackHelper.OpenFormFeedback` methods with the `currentIdentifier` argument. Please use the methods where arguments for the page are passed as a `Map`. 
 * We have deprecated the `com.mendix.core.actionmanagement.internal.InternalCoreAction#setContext(IContext)` method. There is no replacement, this method was meant for internal usage only.
 * We deprecated the Dojo Client. Please switch to the React Client. For more information, see the Mendix React Client’s [Migration Guide](/refguide/mendix-client/react/#migration-guide).