Permissions review

Author: quinntracy

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

@@ -1,6 +1,6 @@
 ---
 title: "Extension Permissions in Overview Pane"
-linktitle: "Extension Permissions Guide"
+linktitle: "Extension Permissions"
 url: /apidocs-mxsdk/apidocs/web-extensibility-api-11/extension-permissions/
 ---
 
@@ -10,13 +10,14 @@ This how-to describes how the permission system works for web extensions in Stud
 
 ## How Permissions Work
 
-Web extensions can request permissions to access sensitive functionality. The permission system follows these principles:
+Web extensions can request permissions to access sensitive functionalities. 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 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
 
 ## Requesting Permissions
+
 To request a permission, declare it in your extension's `package.json` file under the `mendix.permissions` object:
 
 ```json
@@ -35,21 +36,21 @@ To request a permission, declare it in your extension's `package.json` file unde
 }
 ```
 
-Setting a permission to true indicates that your extension requests this permission. The user must grant it before your extension can use the protected functionality.
+Setting a permission to **true** indicates that your extension requests this permission. The user must grant it before your extension can use the protected functionality.
 
 ## Granting Permissions (User Flow)
 
-When a user installs an extension that requests permissions, they can manage those permissions through the Extensions Overview pane:
+When a user installs an extension that requests permissions, they can manage those permissions through the Extensions Overview pane. Follow the steps below:
 
 1. Open Studio Pro and load a project with the extension installed.
-2. Go to View > Extensions Overview to open the Extensions Overview pane.
-3. Find the extension in the list.
-4. Under the extension details, a Permissions section displays the requested permissions.
-5. Check or uncheck the checkbox next to each permission to grant or revoke access.
+2. Go to **View** > **Extensions Overview** to open the Extensions Overview pane.
+3. Find the extension in the list. Under the extension details, the **Permissions** section displays the requested permissions.
+4. Check or uncheck the checkbox next to each permission to grant or revoke access.
 
 ## Available Permissions
 
 Currently, the following permissions are available for web extensions:
+
 | Permission | Description |
 |------------|-------------|
 | `runtime-configuration-private` | Allows the extension to access the values of private constants from the active runtime configuration. Without this permission, private constants are returned with `isPrivate: true` and no value. |