Review

Author: quinntracy

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

@@ -2,19 +2,20 @@
 title: "Show a Pop-up Notification Using Web API"
 linktitle: "Show Notification"
 url: /apidocs-mxsdk/apidocs/web-extensibility-api-11/notification-api/
+description: "Describes how to display a simple pop-up notification in Studio Pro using the Web Extensibility API."
 ---
 
 ## Introduction
 
-This how-to describes how to show a simple pop-up notification in Studio Pro.
+This document describes how to display a simple pop-up notification in Studio Pro.
 
 ## Prerequisites
 
-This how-to uses the results of [Get Started with the Web Extensibility API](/apidocs-mxsdk/apidocs/web-extensibility-api-11/getting-started/). Make sure to complete that how-to before starting this one.
+This how-to uses the results of [Get Started with the Web Extensibility API](/apidocs-mxsdk/apidocs/web-extensibility-api-11/getting-started/). Complete that how-to before starting this one.
 
 ## Showing a Notification
 
-With the notifications API, you can show a pop-up notification when your extension loads. The notification will disappear after five seconds. To do this, follow the steps below:
+With the notifications API, you can show a pop-up notification when your extension loads. The notification disappears after five seconds. To do this, follow these steps:
 
 1. Create an `assets` folder under your `src` folder.
 2. Find an icon you want to use in your notification and copy it into the `assets` folder. This example uses the file `check.png`.
@@ -32,7 +33,7 @@ With the notifications API, you can show a pop-up notification when your extensi
     ```
 
 5. Create an `images.d.ts` file inside the `assets` folder. This is a `declaration` file, as indicated by the `d` file extension.
-6. Add the line `declare module "*.png";` to the `images.d.ts` file. This tells TypeScript that any import ending in *.png* should be treated as a module. This enables TypeScript to handle *.png* files correctly when you import them in your code and allows you to use images in your extensions.
+6. Add the line `declare module "*.png";` to the `images.d.ts` file. This tells TypeScript that any import ending in *.png* should be treated as a module. This allows TypeScript to handle *.png* files correctly when you import them in your code and use images in your extensions.
 7. Replace your `src/main/index.ts` file with the following, using the appropriate icon name in place of `Check`:
 
     ```typescript
@@ -58,21 +59,21 @@ With the notifications API, you can show a pop-up notification when your extensi
 
     This code does the following:
 
-    * It uses the `notificationsApi` from `studioPro.ui.notifications` to allow you to use the notifications API.
-    * It implements a `loaded` method, which calls the `show` method to show a pop-up notification for five seconds with the title `Extension Loaded`, a message, and the `check.png` icon you set up earlier. For more information, see the [Full Reference for Show Method](#reference) section below.
+    * It uses the `notificationsApi` from `studioPro.ui.notifications` to access the notifications API.
+    * It implements a `loaded` method, which calls the `show` method to display a pop-up notification for five seconds with the title `Extension Loaded`, a message, and the `check.png` icon you set up earlier. For more information, see the [Full Reference for Show Method](#reference) section.
 
-Now, when the extension loads, your notification will show in the top-right corner of Studio Pro:
+Now, when the extension loads, your notification shows in the upper-right corner of Studio Pro:
 
-{{< figure src="/attachments/apidocs-mxsdk/apidocs/extensibility-api/web/notifications/notification.png" >}}
+{{< figure src="/attachments/apidocs-mxsdk/apidocs/extensibility-api/web/notifications/notification.png" alt="" >}}
 
 ## Full Reference for Show Method {#reference}
 
 The show method has the following parameters:
 
-* `title` – the title of the notification
-* `message` – the text content of the notification
-* `displayDurationInSeconds` – an optional duration (in seconds) for the notification to remain visible; if no duration is provided, the pop-up will remain indefinitely until the user removes it themselves
-* `icon` – an optional icon that is displayed inside the notification
+* `title` – The title of the notification.
+* `message` – The text content of the notification.
+* `displayDurationInSeconds` – An optional duration (in seconds) for the notification to remain visible; if no duration is provided, the pop-up remains indefinitely until the user removes it.
+* `icon` – An optional icon that displays inside the notification.
 
 ## Extensibility Feedback
 

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

@@ -2,11 +2,12 @@
 title: "Extension Permissions in Overview Pane"
 linktitle: "Extension Permissions"
 url: /apidocs-mxsdk/apidocs/web-extensibility-api-11/extension-permissions/
+description: "Describes how the permission system works for web extensions in Studio Pro and explains how extensions request and users grant access to sensitive APIs."
 ---
 
 ## Introduction
 
-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.
+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.
@@ -16,9 +17,9 @@ Extension permissions were introduced in version 11.9.0.
 
 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 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.
+* **Opt-in by default** – Extensions cannot access protected APIs unless you request permission 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
 
@@ -44,12 +45,12 @@ Setting a permission to **true** indicates that your extension requests this per
 
 ## Granting Permissions (User Flow)
 
-When a user installs an extension that requests permissions, they can manage those permissions through the Extensions Overview pane. Follow the steps below:
+When a user installs an extension that requests permissions, they can manage those permissions through the Extensions Overview pane:
 
 1. Open Studio Pro and load an app with the extension installed.
-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.
+2. Go to **View** > **Extensions Overview**.
+3. Find the extension in the list.
+4. In the **Permissions** section under the extension details, select or clear the checkbox next to each permission to grant or revoke access.
 
 ## Available Permissions