Review

Author: quinntracy

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/migration-guide.md

@@ -7,12 +7,14 @@ weight: 2
 
 ## Introduction
 
-A breaking change was introduced in version 11.6 of the Extensibility API which changed the way [menus](/apidocs-mxsdk/apidocs/web-extensibility-api-11/menu/) are created. Here we will explain how to fix your extension code if you have upgraded to version 11.6 from an older version.
+A breaking change in the Web Extensibility API was introduced in Studio Pro 11.6, which changed the way [menus](/apidocs-mxsdk/apidocs/web-extensibility-api-11/menu/) are created. This guide explains how to update your extension code after upgrading to Studio Pro 11.6 from an earlier version.
 
-## MenuItemActivated Event
-If your extension created menus using the `menuId` and the `menuItemActivated` event in order to trigger actions, you can now simply use the action that was called when the event was triggered as the actual `action` property of your menu.
+## `MenuItemActivated` Event
+
+If your extension created menus using the `menuId` and the `menuItemActivated` event to trigger actions, you can now use the action that was called when the event was triggered as the actual `action` property of your menu.
+
+For example, if your code looked like this:
 
-So if your code looked like this:
 ```typescript
 
 const menuId = "myextension.menu";
@@ -42,12 +44,18 @@ await studioPro.ui.extensionsMenu.add({
     });
 ```
 
-The `menuItemActivated` event no longer exist so you cannot listen to it anymore.
+The `menuItemActivated` event no longer exist, so you cannot listen to it anymore.
 
 ## Registering Commands
-If your extension created menu by using a command id of a pre-registered command, the action that is sent to the command registration api when registering the command can now be used directly as the action of the menu.
 
-So if your code looked like this:
+{{%alert type="info" %}}
+The command registration API has been removed and it is no longer available for Studio Pro 11.6 and above.
+{{% /alert%}}
+
+If your extension created menus by using a command Id of a pre-registered command, the action that is sent to the command registration API when registering the command can now be used directly as the action of the menu.
+
+For example, if your code looked like this:
+
 ```typescript
 const commandId = "myextension.menu-command";
 
@@ -58,7 +66,7 @@ await studioPro.app.commands.registerCommand(
 await studioPro.ui.extensionsMenu.add({ caption: "My Menu", menuId: "myextension.menu", commandId });
 ```
 
-The same action sent to the command registration api can now instead become the `action` property value on the menu:
+The same action sent to the command registration API can now instead become the `action` property value on the menu:
 
 ```typescript
 await studioPro.ui.extensionsMenu.add({
@@ -68,7 +76,6 @@ await studioPro.ui.extensionsMenu.add({
     });
 ```
 
-The command registration API has also been removed and it is no longer available.
+## Action Arguments
 
-# Action Arguments
-Action arguments are also possible in the new Menu API. Please read our [menus documentation](/apidocs-mxsdk/apidocs/web-extensibility-api-11/menu/) for an in-depth explanation.
+Action arguments are also possible in the new Menu API. Review the [Menus documentation](/apidocs-mxsdk/apidocs/web-extensibility-api-11/menu/) for a detailed explanation.