Merge pull request #9770 from mendix/lint-docs

[Auto] Lint docs

Author: MarkvanMents

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.

content/en/docs/deployment/mendix-cloud-deploy/change-plan.md

@@ -35,7 +35,6 @@ Before requesting a plan change, verify the following:
 Changing your app environment's plan does not change the additional storage attached to it. To change the additional storage, you must request an [environment resize](/support/new-app-node-request-template/#resize) through [Mendix Support](https://support.mendix.com/).
 {{% /alert %}}
 
-
 ## Changing a Plan {#changing-plan}
 
 {{% alert color="info" %}}

content/en/docs/deployment/mendix-cloud-deploy/custom-domains.md

@@ -100,7 +100,6 @@ To create a CSR and an RSA (Rivest–Shamir–Adleman) encryption key, follow th
 
 4. Click **Generate**.
 
-
     An SSL/TLS private key and a certificate request is generated. The certificate request will be shown in PEM (Privacy-Enhanced Mail) format.
 
     {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/new-pem-format.png" >}}

content/en/docs/developerportal/digital-execution/compass/lead-mendix-implementation-your-organization.md

@@ -950,4 +950,4 @@ Here are some resources help familiarize yourself with the Mendix platform:
 * The [Mendix Partner Hub](https://www.mendix.com/partners/) allows you to explore our Partner Network. 
 * The [Mendix Marketplace](https://marketplace.mendix.com/) provides access to modules, widgets, solutions, and other content provided by Mendix, partners or the community. 
 * The [Siemens Annual Reports](https://www.siemens.com/global/en/company/investor-relations/events-publications-ad-hoc/annualreports.html?gclid=CjwKCAjwzo2mBhAUEiwAf7wjkpk1onH3tK1d_kOzGxjbQa5MTFF91cbKKfp7a6F3AS8mDpov1_M6choCbE8QAvD_BwE&acz=1) offer details on financial, corporate governance, and sustainability.
-* The [DEP Manual](https://www.mendix.com/resources/digital-execution-manual/) provides information about the 5 P’s and how to best leverage the Mendix low-code platform.
+* The [DEP Manual](https://www.mendix.com/resources/digital-execution-manual/) provides information about the 5 P’s and how to best leverage the Mendix low-code platform.

content/en/docs/developerportal/general/settings/_index.md

@@ -33,7 +33,7 @@ The page header displays the following information:
 
 * The app image – You can change the image by clicking it.
 * The app name – You can change the name of the app by clicking the pencil icon next to it.    
-    Renaming the app in the Mendix Portal does not rename it in Studio Pro. The app name in Studio Pro is tied to its *.mpr* file. However, changing the name of the *.mpr* file is not supported, and we strongly advise against it. For more information, refer to the [Mendix MPR Storage ](/refguide/version-control/#mpr-format) section in *Version Control*. 
+    Renaming the app in the Mendix Portal does not rename it in Studio Pro. The app name in Studio Pro is tied to its *.mpr* file. However, changing the name of the *.mpr* file is not supported, and we strongly advise against it. For more information, refer to the [Mendix MPR Storage](/refguide/version-control/#mpr-format) section in *Version Control*. 
 * The company that owns the app.
 * The **Watch** / **Stop Watching** toggle – You can enable or disable notifications for this app.
 

content/en/docs/marketplace/create-content/create-solutions/implement-solutions/sol-upgrade.md

@@ -41,4 +41,4 @@ To upgrade a solution, follow these steps:
 
 ### Read More
 
-* [Setting Up Solutions](/appstore/creating-content/sol-set-up/) 
+* [Setting Up Solutions](/appstore/creating-content/sol-set-up/) 

content/en/docs/marketplace/create-content/upload-content/oss-compliance.md

@@ -44,7 +44,7 @@ To ensure your Marketplace contribution is OSS-compliant, you must include the f
     * List each OSS component, its license, and any required attributions.
     * Follow all license conditions around modification or redistribution.
 
- ## Prohibited or High-Risk OSS Licenses
+## Prohibited or High-Risk OSS Licenses
 
 Certain OSS licenses impose strong copyleft obligations that may conflict with how Mendix modules are distributed or used in customer environments.
 

content/en/docs/marketplace/platform-supported-content/widgets/charts/charts-custom-usage.md

@@ -93,7 +93,7 @@ If need be, the layout can also be generated in the same way as the data. In mos
 
 Editing the JSON configuration in Studio Pro can be cumbersome. With the live preview editor, developers can directly see the output of their changes. 
 
-See (Chart advanced tuning)[/appstore/widgets/chart-advanced-tuning/] for more information on fine tuning **Custom Chart** with using **Chart Playground** widget.
+See [Chart advanced tuning](/appstore/widgets/chart-advanced-tuning/) for more information on fine tuning **Custom Chart** with using **Chart Playground** widget.
 
 {{% alert color="info" %}}
 Since the introduction of design mode, react-ready widgets can render data as it is entered. This makes it possible for user to see Static data and configurations directly in design mode without the needs of running the apps.
@@ -103,17 +103,16 @@ Since the introduction of design mode, react-ready widgets can render data as it
 
 These are the dimension configurations for custom charts:
 
-- **Width** — Determines the width size for the custom charts. User can choose to use either pixels (px) or percentage (%).
-- **Height** — Determine the height size for the custom charts. User can choose to use either pixels (px), percentage (%), or Viewport (vh). Choosing setting to **Auto** will allow user to set minimum and maximum height instead.
-- **Minimum Height** — Determines the minimum size for the custom charts container.
-- **Maximum Height** — Determines the maximum size for the custom charts container.
-- **Vertical Overflow** — If maximum height is set, vertical overflow will determine the widget's behavior to show overflowing content if it reached height size larger than the maximum height allowed.
-
+* **Width** — Determines the width size for the custom charts. User can choose to use either pixels (px) or percentage (%).
+* **Height** — Determine the height size for the custom charts. User can choose to use either pixels (px), percentage (%), or Viewport (vh). Choosing setting to **Auto** will allow user to set minimum and maximum height instead.
+* **Minimum Height** — Determines the minimum size for the custom charts container.
+* **Maximum Height** — Determines the maximum size for the custom charts container.
+* **Vertical Overflow** — If maximum height is set, vertical overflow will determine the widget's behavior to show overflowing content if it reached height size larger than the maximum height allowed.
 
 ## Events
 
-- **On Click** — Determines the actions that will be triggered if parts of the custom charts is clicked.
-- **Event data attribute** — The string value that the chart uses when click events occur. User can use this same attribute as the parameters for on-click events action to retrieve the data from the custom chart:
+* **On Click** — Determines the actions that will be triggered if parts of the custom charts is clicked.
+* **Event data attribute** — The string value that the chart uses when click events occur. User can use this same attribute as the parameters for on-click events action to retrieve the data from the custom chart:
 
     {{< figure src="/attachments/appstore/platform-supported-content/widgets/charts/charts-tutorials/charts-any-usage/custom-chart-events-attribute.png" alt="Setup on click events" class="no-border" >}}
 

content/en/docs/marketplace/platform-supported-content/widgets/document-viewer.md

@@ -39,11 +39,11 @@ To configure this widget, follow these steps:
 
 These are the dimension configurations for document viewer:
 
-- **Width** — Determines the width size for the document viewer. The developer can choose to use either pixels (px), percentage (%), or **Fit to content**.
-- **Height** — Determine the height size for the document viewer. The developer can choose to use either pixels (px), percentage (%), or **Viewport** (vp). Choosing setting to **Auto** will allow the developer to set minimum and maximum heights instead.
-- **Minimum Height** — Determines the minimum size for the custom charts container.
-- **Maximum Height** — Determines the maximum size for the custom charts container.
-- **Vertical Overflow** — If maximum height is set, vertical overflow will determine the widget's behavior to show overflowing content if that content exceeded the maximum height allowed.
+* **Width** — Determines the width size for the document viewer. The developer can choose to use either pixels (px), percentage (%), or **Fit to content**.
+* **Height** — Determine the height size for the document viewer. The developer can choose to use either pixels (px), percentage (%), or **Viewport** (vp). Choosing setting to **Auto** will allow the developer to set minimum and maximum heights instead.
+* **Minimum Height** — Determines the minimum size for the custom charts container.
+* **Maximum Height** — Determines the maximum size for the custom charts container.
+* **Vertical Overflow** — If maximum height is set, vertical overflow will determine the widget's behavior to show overflowing content if that content exceeded the maximum height allowed.
 
 ### Common Tab
 
@@ -61,4 +61,3 @@ This widget is not intended to replace the standalone file viewer application. I
 * **Excel**
     * The widget is only able to display the first sheet from an xlsx document.
     * The Excel 1997-2003 document format (*.xls) is not supported.
-

content/en/docs/refguide/mobile/distributing-mobile-apps/distributing-native-apps.md

@@ -154,4 +154,4 @@ To publish in the Android Google Play Console, do the following:
 1. Upload your signed *.apk* or *.aab* file.
 1. Review and roll out your release to production.
 
-Be sure to enroll in Google Play App Signing if you plan to use AAB files. Also, don’t forget to set up content rating, privacy policies, and testing tracks if needed.
+Be sure to enroll in Google Play App Signing if you plan to use AAB files. Also, don’t forget to set up content rating, privacy policies, and testing tracks if needed.

content/en/docs/refguide/modeling/application-logic/workflows/jump-to.md

@@ -49,4 +49,4 @@ For more information about jumping rules in a boundary event path, see the [Jump
 ## Read More
 
 * [Generate Jump-To Options](/refguide/generate-jump-to-options/)
-* [Apply Jump-To Option](/refguide/apply-jump-to-option/)
+* [Apply Jump-To Option](/refguide/apply-jump-to-option/)

content/en/docs/refguide/modeling/domain-model/oql/_index.md

@@ -86,4 +86,4 @@ In OQL, `FLOAT` is a reserved word for legacy reasons. Mendix no longer supports
 
 {{% alert color="info" %}}
 In OQL, `DELETE`, `INSERT`, `REPLACE`, `UPDATE`, `UPSERT`, `INTO`, `SET`, `VALUES`, `IGNORE`, `MATCHED`, `DUPLICATE`, `KEY`, `CONFLICT`, `MERGE`, `USING`, `SOURCE`, `TARGET`, and `WITH` are reserved but not yet used.
-{{% /alert %}}
+{{% /alert %}}

content/en/docs/refguide/modeling/pages/data-widgets/data-sources/listen-to-grid-source.md

@@ -14,7 +14,6 @@ A data view in an image above listens to a data grid. In this example, the data
 
 List views, template grids, and data grids are list widgets and can be listened to. If no object is selected in the list widget, the data view will remain empty and unresponsive.
 
-
 To enable **Listen to widget** in common data sources, do the following per your use case: 
 
 * DataGrid2: Select **Selection** > **Single** and **Selection method** > **Row click**  to be able to select a  DataGrid2 as a **Listen to widget** data source in your dataview.

content/en/docs/refguide/runtime/mendix-client/react.md

@@ -121,8 +121,8 @@ Because the reference set selector widget is technically a grid, while combo box
 
 The [HTML/JavaScript snippet](/appstore/widgets/html-javascript-snippet/) widget is not supported in the React Client. To leverage React, this widget can be replaced using [HTML Element](/appstore/widgets/htmlelement/) widget or [JavaScript actions](/refguide/javascript-actions/):
 
-*  **Content Type** HTML — The HTML Element can be downloaded [here](https://marketplace.mendix.com/link/component/204843).
-*  **Content Type** JavaScript — Write the code inside the supported JavaScript actions. If the user needs to execute the code in a certain way, calling the JavaScript action via nanoflow that triggers by [Events](/appstore/widgets/events/) widget is recommended.
+* **Content Type** HTML — The HTML Element can be downloaded [here](https://marketplace.mendix.com/link/component/204843).
+* **Content Type** JavaScript — Write the code inside the supported JavaScript actions. If the user needs to execute the code in a certain way, calling the JavaScript action via nanoflow that triggers by [Events](/appstore/widgets/events/) widget is recommended.
 
 #### Data Grid{#data-grid}
 

content/en/docs/refguide/version-control/version-control-troubleshooting/repository-size.md

@@ -36,7 +36,6 @@ Other places where you might encounter performance issues or timeouts are the fo
 
 ### MPR Storage Format {#mpr-format}
 
-
 In Studio Pro 11, apps are automatically converted to the MPRv2 storage format. For more information of the effects of the MPRv1 storage format, please see the [MPR Storage Format](/refguide10/troubleshoot-repository-size/#mpr-format) section in *Troubleshooting Repository Size* in *Studio Pro 10 Guide*.
 
 MPRv2 storage format prevents your repository from a rapid growth. Documents such as microflows, are not stored as part of the *.mpr* file but as separate files in the *mprcontents* directory. The *.mpr* file functions as an index file pointing to all the different files on disk.
@@ -214,4 +213,4 @@ Follow the decision tree in the image below to troubleshoot Git-related performa
 
 \** For more information on partial clone, see [Clone Type](/refguide/clone-type/).
 
-\*** For more information on Git cleanup, see the [Cleanup](/refguide/troubleshoot-repository-size/#cleanup-tool) section in *Troubleshooting Repository Size*.
+\*** For more information on Git cleanup, see the [Cleanup](/refguide/troubleshoot-repository-size/#cleanup-tool) section in *Troubleshooting Repository Size*.

content/en/docs/refguide10/mobile/distributing-mobile-apps/distributing-native-apps.md

@@ -154,4 +154,4 @@ To publish in the Android Google Play Console, do the following:
 1. Upload your signed *.apk* or *.aab* file.
 1. Review and roll out your release to production.
 
-Be sure to enroll in Google Play App Signing if you plan to use AAB files. Also, don’t forget to set up content rating, privacy policies, and testing tracks if needed.
+Be sure to enroll in Google Play App Signing if you plan to use AAB files. Also, don’t forget to set up content rating, privacy policies, and testing tracks if needed.

content/en/docs/refguide10/modeling/menus/edit-menu/preferences-dialog.md

@@ -260,8 +260,6 @@ This option allows you to change the user interface language you work in while u
 | Korean                 | 10.17      | 10.24                |
 | Portuguese (Brazilian) | 10.23      | TBD                  |
 
-
-
 ### Editor Tabs Closing Policy {#closing-policy}
 
 It is recommended to limit the number of open tabs (open documents) to improve the performance of Studio Pro. This option is enabled by default and set to a limit of 15 tabs. However, you can disable this behavior completely or change the limit value.