Merge branch 'development' of https://github.com/SofiBili/docs into pr/10915

Author: quinntracy

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

@@ -8,13 +8,17 @@ url: /apidocs-mxsdk/apidocs/web-extensibility-api-11/extension-permissions/
 
 This how-to describes how the permission system works for web extensions in Studio Pro. Permissions allow extensions to request access to sensitive APIs or data that require explicit user consent.
 
+{{% alert color="info" %}}
+Extension permissions were introduced in version 11.9.0.
+{{% /alert %}}
+
 ## How Permissions Work
 
-Web extensions can request permissions to access sensitive functionalities. The permission system follows these principles:
+Web extensions can request permissions to access sensitive functionality. The permission system follows these principles:
 
-* **Opt-in by default** — Extensions cannot access protected APIs unless they explicitly request the permission and the user grants it
-* **User control** — Users decide which permissions to grant through the Extensions Overview pane in Studio Pro
-* **Per-project settings** — Permission grants are stored per project so users can have different permission settings for the same extension across different projects
+* **Opt-in by default** — Extensions cannot access protected APIs unless you request persmission and the extension user grants it
+* **User control** — You decide which permissions to grant through the Extensions Overview pane in Studio Pro
+* **Per-project settings** — Permission grants are stored per project, so a user’s approval for an extension applies only within that app. This gives them the flexibility to grant a permission in one project and choose different settings for the same extension in another.
 
 ## Requesting Permissions
 

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

@@ -8,6 +8,10 @@ url: /apidocs-mxsdk/apidocs/web-extensibility-api-11/runtime-configuration-api/
 
 This how-to describes how to create a simple menu that retrieves and displays the runtime constants from the active configuration in a message box.
 
+{{% alert color="info" %}}
+Access to runtime constants using the web API was introduced in version 11.9.0.
+{{% /alert %}}
+
 ## Prerequisites
 
 Before starting this how-to, make sure you have completed the following prerequisites:
@@ -80,6 +84,7 @@ The code uses the:
 {{% /alert %}}
 
 The `getConstants()` function returns an array of constant objects, each with the following properties:
+
 * `isPrivate` – a boolean indicating whether the constant value is hidden (true) or accessible (false)
 * `constantName` – the fully qualified name of the constant (for example, `MyModule.MyConstant`)
 * `value` – the constant value as a string (only present when `isPrivate` is false)
@@ -111,7 +116,7 @@ You have to set the permission to true if you want the permission to appear in t
 
 When a user installs your extension, they can grant this permission through the Extensions Overview pane (**View** > **Extensions**) in Studio Pro. Once granted, private constants will be returned with `isPrivate` set to false and their value included.
 
-You can read more about permissions in [Extension Permission](/apidocs-mxsdk/apidocs/web-extensibility-api-11/extension-permissions/).
+You can read more about permissions in [Extension Permissions in Overview Pane](/apidocs-mxsdk/apidocs/web-extensibility-api-11/extension-permissions/).
 
 ## Extensibility Feedback
 

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

@@ -8,6 +8,10 @@ url: /apidocs-mxsdk/apidocs/web-extensibility-api-11/runtime-controller-api/
 
 This how-to describes how to create a simple menu that displays when the connection changed in a message box.
 
+{{% alert color="info" %}}
+Listening for connection changes was introduced in version 11.9.0.
+{{% /alert %}}
+
 ## Prerequisites
 
 Before starting this how-to, make sure you have completed the following prerequisites:
@@ -21,7 +25,7 @@ Before starting this how-to, make sure you have completed the following prerequi
 You can listen for runtime connection state changes to know when the app starts or stops running. To do this, follow the steps below:
 
 1. Add an event listener to respond when the connection state changes.
-2. Replace your `src/main/index.ts` file with the following:
+2. Replace the content of your `src/main/index.ts` file with the following:
 
 ```typescript
 import { IComponent, getStudioProApi } from "@mendix/extensions-api";
@@ -52,7 +56,7 @@ The code uses the:
 {{% alert color="info" %}} The function is `async` in order for you to use `await` when executing the preview action.
 {{% /alert %}}
 
-The `connectionChanged` event provides an object with:
+The `connectionChanged` event returns an object with:
 
 * `isConnected` – a boolean indicating whether the runtime is currently connected (true) or disconnected (false)