Fixing lint errors

Author: OlufunkeMoronfolu

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/extensibility-api/csharp/extensibility-api-howtos/build-todo-example-extension.md

@@ -750,27 +750,27 @@ This HTML page provides a simple interface styled with Tailwind CSS. The JavaScr
 
 1. Add a helper function to simplify the call to the browser API:
 
-```javascript
-function postMessage(message, data) {
-  window.chrome.webview.postMessage({ message, data });
-}
-```
+    ```javascript
+    function postMessage(message, data) {
+        window.chrome.webview.postMessage({ message, data });
+    }
+    ```
 
-1. Initialize message handling and respond to incoming messages: 
+2. Initialize message handling and respond to incoming messages: 
 
-```javascript
-// Register message handler.
-window.chrome.webview.addEventListener("message", handleMessage);
-// Indicate that you are ready to receive messages.
-postMessage("MessageListenerRegistered");
+    ```javascript
+    // Register message handler.
+    window.chrome.webview.addEventListener("message", handleMessage);
+    // Indicate that you are ready to receive messages.
+    postMessage("MessageListenerRegistered");
 
-async function handleMessage(event) {
-  const { message, data } = event.data;
-  if (message === "RefreshToDos") {
-      await refreshToDos();
-  }
-}
-```
+    async function handleMessage(event) {
+        const { message, data } = event.data;
+        if (message === "RefreshToDos") {
+            await refreshToDos();
+        }
+    }
+    ```
 
 {{% alert color="warning" %}}
 

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/extensibility-api/web/get-started.md

@@ -30,7 +30,7 @@ This section will show you how to build and test an extension.
 ### Create a Test App
 
 1. Create a new app using the **Blank Web App** template.
-1. Install the [Studio Pro Web Extension Template](https://github.com/mendix/web-extension-template) from GitHub using the instructions in the repository.
+2. Install the [Studio Pro Web Extension Template](https://github.com/mendix/web-extension-template) from GitHub using the instructions in the repository.
 
 ### Building the Extension
 
@@ -54,7 +54,7 @@ You can explore the extension to understand what it does when it is installed. D
 
     Reading through the source code you should see the following:
 
-      a. Line 7 adds a menu
+    a. Line 7 adds a menu
 
       ```typescript
       await studioPro.ui.extensionsMenu.add({
@@ -64,24 +64,24 @@ You can explore the extension to understand what it does when it is installed. D
       });
       ```
 
-      1. Line 14 opens a tab
-   
-        ```typescript
-        // Open a tab when the menu item is clicked
-        studioPro.ui.extensionsMenu.addEventListener("menuItemActivated", (args) => {
-          if (args.menuId === "myextension.ShowTabMenuItem") {
-            studioPro.ui.tabs.open(
-              {
-                title: "My Extension Tab",
-              },
-              {
-                componentName: "extension/myextension",
-                uiEntrypoint: "tab",
-              }
-            );
-          }
-        });
-          ```
+    b. Line 14 opens a tab
+
+      ```typescript
+      // Open a tab when the menu item is clicked
+      studioPro.ui.extensionsMenu.addEventListener("menuItemActivated", (args) => {
+        if (args.menuId === "myextension.ShowTabMenuItem") {
+          studioPro.ui.tabs.open(
+            {
+              title: "My Extension Tab",
+            },
+            {
+              componentName: "extension/myextension",
+              uiEntrypoint: "tab",
+            }
+          );
+        }
+      });
+      ```
 
 When you install the extension, you will see a new menu item within Studio Pro.
 

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/extensibility-api/web/web-extensions-howtos/dockable-pane-api.md

@@ -174,7 +174,7 @@ Your `loaded()` method should now look like this:
 Create a new web view endpoint where you define the user interface that will be rendered within the pane. You can use and rename the existing endpoint. Follow the steps below:
 
 1. Rename `ui/index.tsx` to `ui/tab.tsx`.
-1. Add the new endpoint file, `ui/dockablepane.tsx`, by copying `ui/tab.tsx`.
+2. Add the new endpoint file, `ui/dockablepane.tsx`, by copying `ui/tab.tsx`.
 
 You must also alter the `vite.config.ts` and `manifest.json` files to bind to the correct endpoint, as described in the following sections:
 
@@ -255,13 +255,13 @@ You will close your pane using a new menu item. Follow the steps below:
 
 1. Add a new sub-menu item to the menu on line 11.
 
-```typescript {linenos=table linenostart=11}
-                { menuId: "myextension.HideDockMenuItem", caption: "Hide dock pane" },
-```
+    ```typescript {linenos=table linenostart=11}
+    { menuId: "myextension.HideDockMenuItem", caption: "Hide dock pane" },
+    ```
 
-1. Alter the event handler for the new menu at the end of the loaded method:
+2. Alter the event handler for the new menu at the end of the loaded method:
 
-```typescript
+    ```typescript
         // Open a tab when the menu item is clicked
         studioPro.ui.extensionsMenu.addEventListener(
             "menuItemActivated",
@@ -285,7 +285,7 @@ You will close your pane using a new menu item. Follow the steps below:
                 }
             }
         );
-```
+    ```
 
 The loaded method should now look like this:
 

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/csharp/extensibility-api-howtos/build-todo-example-extension.md

@@ -750,27 +750,27 @@ This HTML page provides a simple interface styled with Tailwind CSS. The JavaScr
 
 1. Add a helper function to simplify the call to the browser API:
 
-```javascript
-function postMessage(message, data) {
-  window.chrome.webview.postMessage({ message, data });
-}
-```
+    ```javascript
+    function postMessage(message, data) {
+        window.chrome.webview.postMessage({ message, data });
+    }
+    ```
 
-1. Initialize message handling and respond to incoming messages: 
+2. Initialize message handling and respond to incoming messages: 
 
-```javascript
-// Register message handler.
-window.chrome.webview.addEventListener("message", handleMessage);
-// Indicate that you are ready to receive messages.
-postMessage("MessageListenerRegistered");
+    ```javascript
+    // Register message handler.
+    window.chrome.webview.addEventListener("message", handleMessage);
+    // Indicate that you are ready to receive messages.
+    postMessage("MessageListenerRegistered");
 
-async function handleMessage(event) {
-  const { message, data } = event.data;
-  if (message === "RefreshToDos") {
-      await refreshToDos();
-  }
-}
-```
+    async function handleMessage(event) {
+        const { message, data } = event.data;
+        if (message === "RefreshToDos") {
+            await refreshToDos();
+        }
+    }
+    ```
 
 {{% alert color="warning" %}}
 

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/preference-api.md

@@ -87,16 +87,12 @@ Import the preferences API and use it to fetch the user’s preferences.
     );
     ```
 
-{{% alert color="info" %}}
-The function is `async` in order for you to use `await` when fetching the preferences.
-{{% /alert %}}
+    {{% alert color="info" %}} The function is `async` in order for you to use `await` when fetching the preferences.
+    {{% /alert %}}
 
-1. Use the fetched preferences to update the text in the message box so you can see the user's current theme and language.
-
-The `getPreferences()` function returns an object with two properties:
-
-* Theme — either **Light** or **Dark**, representing the current theme setting in Studio Pro
-* Language — a string representing the current language setting, such as `en_US` for English (United States)
+3. Use the fetched preferences to update the text in the message box so you can see the user's current theme and language. The `getPreferences()` function returns an object with two properties:
+    * Theme – either **Light** or **Dark**, representing the current theme setting in Studio Pro
+    * Language – a string representing the current language setting, such as `en_US` for English (United States)
 
 The complete `src/main/index.ts` file should now look like this:
 

content/en/docs/deployment/mx-azure/configuration/mx-azure-direct-database-access.md

@@ -30,21 +30,21 @@ By default, the read replica for Postgres database is disabled. To enable it, pe
 
 1. On the **Provision > Database Settings** section of the **Initialize Cluster** page, set the **Enable Read Replica** option to **Yes**.
 
-{{% alert color="info" %}} For existing clusters, you can also enable or disable the read replica in the **Edit Cluster** flow.{{% /alert %}}
+    {{% alert color="info" %}} For existing clusters, you can also enable or disable the read replica in the **Edit Cluster** flow.{{% /alert %}}
 
-1. Click **Next** to initialize the cluster.
+2. Click **Next** to initialize the cluster.
 
     {{< figure src="/attachments/deployment/mx-azure/enableReadReplica.png" class="no-border" >}}
 
     After the cluster is initialized, the read replica for PostgreSQL database is enabled, and a read replica for the PostgreSQL database has been created automatically.
 
     {{< figure src="/attachments/deployment/mx-azure/readReplicaEnabled.png" class="no-border" >}}
 
-2. Copy the address value from the record set within the private DNS zone created for your PostgreSQL database. You can find this private DNS zone in the [Managed Resource Group of your Mendix on Azure environment](/developerportal/deploy/mendix-on-azure/configuration/#mrg).
+3. Copy the address value from the record set within the private DNS zone created for your PostgreSQL database. You can find this private DNS zone in the [Managed Resource Group of your Mendix on Azure environment](/developerportal/deploy/mendix-on-azure/configuration/#mrg).
 
     {{< figure src="/attachments/deployment/mx-azure/copyAddressValue.png" class="no-border" >}}
 
-3. Add Entra ID users who should be able to access the replica database by performing the following steps:
+4. Add Entra ID users who should be able to access the replica database by performing the following steps:
 
     1. In the Azure portal, go to the [Managed Resource Group of your Mendix on Azure environment](/developerportal/deploy/mendix-on-azure/configuration/#mrg).
     2. Select the PostgreSQL master database resou.rce (type: Azure Database for PostgreSQL Flexible Server).

content/en/docs/deployment/mx-azure/mx-azure-backups.md

@@ -25,17 +25,18 @@ You must have **Manage Apps Backups** permission for the namespace to use this f
 2. Click **Backups** in the navigation pane.
 3. Choose the environment to back up from the environment dropdown.
 
-{{% alert color="info" %}} 
+    {{% alert color="info" %}}
+<!-- Need to do it this way to satisfy linter and get correct format-->
 Backups cannot be created while the environment is in any of these states:
 
 * Creation in progress
 * Creation failed
 * Deployment package is being deployed
-* Environment is in transition state (runtime processing) 
-{{% /alert %}}
+* Environment is in transition state (runtime processing)
+    {{% /alert %}}
 
 1. Click **Create Backup**.
-2. Monitor progress in the **Status** column.
+1. Monitor progress in the **Status** column.
 
 {{% alert color="info" %}} 
 Tables are locked during backup creation, so if you attempt to start the environment while a backup is in progress, you may encounter a timeout error. Wait for backup completion before restarting. 

content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md

@@ -1359,20 +1359,20 @@ You can invite additional members to the namespace, and configure their role dep
     2. **Administrator** – a standard set of rights needed by an administrator, these are listed on the screen
     3. **Custom** – This option is now deprecated.
 
-{{% alert color="info" %}}
-The custom permission if needed to be edited, a role need to be assigned with appropriate permissions. See [Roles and Permissions](/developerportal/deploy/private-cloud-cluster/#rolesandpermissions) for more information.
-{{% /alert %}}
+    {{% alert color="info" %}}
+    The custom permission if needed to be edited, a role need to be assigned with appropriate permissions. See [Roles and Permissions](/developerportal/deploy/private-cloud-cluster/#rolesandpermissions) for more information.
+    {{% /alert %}}
 
-{{% alert color="info" %}}
-If an application is in the Stopped state, the scaling does not come into effect until the application is Started. This means that you have to click **Start application** in order for the changes to be sent to the cluster.
-Along with this, we have also decoupled the permission for modifying the MxAdmin password and managing environments.
-{{% /alert %}}
+    {{% alert color="info" %}}
+    If an application is in the Stopped state, the scaling does not come into effect until the application is Started. This means that you have to click **Start application** in order for the changes to be sent to the cluster.
+    Along with this, we have also decoupled the permission for modifying the MxAdmin password and managing environments.
+    {{% /alert %}}
 
-1. Click **Send Invite** to send an invite to this person.
+6. Click **Send Invite** to send an invite to this person.
 
     {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/AutoAcceptInvite.png" class="no-border" >}}
 
-2. If you have not enabled the **Automatically accept invites** option, the user will receive an email and will be required to follow a link to confirm that they want to join this namespace. They will need to be logged in to Mendix when they follow the confirmation link.
+7. If you have not enabled the **Automatically accept invites** option, the user will receive an email and will be required to follow a link to confirm that they want to join this namespace. They will need to be logged in to Mendix when they follow the confirmation link.
 
 ##### Editing and Removing Members
 

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md

@@ -51,9 +51,9 @@ To install and configure the Global Operator, perform the following steps:
     2. [Sign into the Platform](/developerportal/deploy/standard-operator/#openshift-signin).
     3. Perform the [Base Installation](/developerportal/deploy/standard-operator/#base-installation).
 
-    {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator6.png" class="no-border" >}}
+        {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator6.png" class="no-border" >}}
 
-    1. You can apply the custom TLS and proxy settings in the Global Operator main namespace by just selecting only the **Custom TLS** and **Proxy** options in the Configuration Tool.
+    4. You can apply the custom TLS and proxy settings in the Global Operator main namespace by just selecting only the **Custom TLS** and **Proxy** options in the Configuration Tool.
 
     {{% alert color="info" %}}Base installation can only be performed on the Global Operator main namespace. Along with base installation, you can also apply custom TLS and proxy settings. However, other configurations such as storage plan, database plan, ingress configuration, or registry configuration are not supported in Global Operator main namespace.{{% /alert %}}
 

content/en/docs/marketplace/platform-supported-content/modules/azure/azure-blob-storage-connector.md

@@ -121,7 +121,7 @@ To use this operation in your microflow, perform the following steps:
 7. Configure a method to trigger the `ACT_PutBlob` microflow. 
     For example, you can call the microflow with a custom button on a page in your app. For an example of how this can be implemented, see [Creating a Custom Save Button with a Microflow](/refguide/creating-a-custom-save-button/).
 
-The operation returns a **PutBlobRequestResponse** object, which is empty on itself, only its generization AbstractResponse entity contains the http status code and optional the http reason phrase.
+The operation returns a **PutBlobRequestResponse** object, which is empty on itself, only its generalization AbstractResponse entity contains the http status code and optional the http reason phrase.
 
 #### GET_v1_Azure_GetBlob
 
@@ -142,7 +142,7 @@ To use this operation in your microflow, perform the following steps:
 3. Call the **GET_v1_Azure_GetBlob** action in your microflow.
 
 The operation returns a **GetBlobResponse** object with the returned Blob associated with it.
-Its generization AbstractResponse entity contains the http status code and optional the http reason phrase.
+Its generalization AbstractResponse entity contains the http status code and optional the http reason phrase.
 
 #### DELETE_v1_Azure_DeleteBlob
 
@@ -161,7 +161,7 @@ To use this operation in your microflow, perform the following steps:
 3. Call the **DELETE_v1_Azure_DeleteBlob** action in your microflow.
 
 The operation returns a **DeleteBlobResponse** object, which is a generalization of **AbstractResponse** and contains the **StatusCode** and **ReasonPhrase**.
-Its generization AbstractResponse entity contains the http status code and optional the http reason phrase.
+Its generalization AbstractResponse entity contains the http status code and optional the http reason phrase.
 
 #### GET_v1_Azure_ListBlobs
 
@@ -182,7 +182,7 @@ To use this operation in your microflow, perform the following steps:
 3. Call the **GET_v1_Azure_ListBlobs** action in your microflow.
 
 The operation returns a list of **Blob** objects associated to the **ListBlobResponse**, which is a generalization of **AbstractResponse** and contains the **StatusCode** and **ReasonPhrase**.
-Its generization AbstractResponse entity contains the http status code and optional the http reason phrase.
+Its generalization AbstractResponse entity contains the http status code and optional the http reason phrase.
 
 #### GET_v1_Azure_ListContainers
 
@@ -202,7 +202,7 @@ To use this operation in your microflow, perform the following steps:
 3. Call the **GET_v1_Azure_ListContainers** action in your microflow.
 
 The operation returns a list of **Container** objects associated to the **ListContainersResponse**, which is a generalization of **AbstractResponse** and contains the **StatusCode** and **ReasonPhrase**.
-Its generization AbstractResponse entity contains the http status code and optional the http reason phrase.
+Its generalization AbstractResponse entity contains the http status code and optional the http reason phrase.
 
 #### POST_v1_Azure_GetApplicationBearerToken
 
@@ -219,7 +219,7 @@ To use this operation in your microflow, perform the following steps:
 2. Call the **POST_v1_Azure_GetApplicationBearerToken** action in your microflow.
 
 The operation returns a **GetApplicationBearerTokenResponse** object with the returned **EntraCredentialsUsage** associated to it. The **EntraCredentialsUsage** entity is a specialization of the **EntraCredentials** entity so the returned object can be used to authenticate Blob operations.
-Its generization AbstractResponse entity contains the http status code and optional the http reason phrase.
+Its generalization AbstractResponse entity contains the http status code and optional the http reason phrase.
 
 #### POST_v1_Azure_GetUserDelegationKey{#get-user-delegation-key}