Review

Author: quinntracy

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/packaging-your-extension.md

@@ -10,7 +10,7 @@ After completing development on your extension, you can package it into an add-o
 
 To package your extension, follow the steps below:
 
-1. Make sure the setting for enabling extension development is checked in the Preferences form. Alternatively, you can start Studio Pro with the `--enable-extension-development` command-line option.
+1. Make sure you have enabled the [Extension Development](/refguide/preferences-dialog/#extension-development) setting in your app's Preferences. Alternatively, you can start Studio Pro with the `--enable-extension-development` command-line option.
 2. In your Studio Pro app, create a new module and include your development extension.
 3. Give the module a name. 
 4. Open the module's settings and in the **Export** tab, choose **Add-on module**. 

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

@@ -24,7 +24,7 @@ Extensions can be built on any operating system, as the underlying framework is
 {{% /alert %}}
 
 {{% alert color="info" %}}
-Extension development is only possible enabling the setting in `Extension Development` under `Advanced` in the Studio Pro preferences form, or by starting Studio Pro using the `--enable-extension-development` feature flag.
+Extension development is only possible by enabling the [Extension Development](/refguide/preferences-dialog/#extension-development) setting in your app's Preferences, or by starting Studio Pro with the `--enable-extension-development` feature flag.
 {{% /alert %}}
 
 ## Creating Your First Extension
@@ -75,14 +75,14 @@ Before you begin, your extension will have to get an instance of the Studio Pro
 
 In the source code, you should see the following:
 
-1. We get an instance of the Studio Pro API by calling `getStudioProApi`.
+1. You get an instance of the Studio Pro API by calling `getStudioProApi`.
 
     ```typescript
     export const component: IComponent = {
         async loaded(componentContext) {
             const studioPro = getStudioProApi(componentContext);
 
-2. We add a menu that opens a tab:
+2. A menu is added that opens a tab:
 
     ```typescript
     await studioPro.ui.extensionsMenu.add({
@@ -109,7 +109,7 @@ In the source code, you should see the following:
     });
     ```
 
-3. If you navigate to `build-extension.mjs`, you can choose the directory to which the extension will be installed to after being built by changing line 6:
+3. If you navigate to `build-extension.mjs`, you can choose the directory where the extension will be installed to after being built by changing line 6:
 
      ```typescript
      const appDir = "C:\\TestApps\\AppTestExtensions"

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

@@ -12,7 +12,7 @@ This how-to describes how to interact with the App Explorer in Studio Pro. In th
 
 Before starting this how-to, make sure you have completed the following prerequisites:
 
-* Read up on how menus work in the Extensibility API [here](/apidocs-mxsdk/apidocs/web-extensibility-api-11/menu/)
+* Review [how menus work](/apidocs-mxsdk/apidocs/web-extensibility-api-11/menu/) in the Web Extensibility API
 * 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.
 
 ## Creating a Context Menu
@@ -21,7 +21,7 @@ Before starting this how-to, make sure you have completed the following prerequi
 Use the full name of the document type to specify which type of document a menu should belong to (for example, `Microflows$Microflow` for microflows or `Pages$Page` for pages). For more information about these document type names, see [Access a Mendix Model Using Web API](/apidocs-mxsdk/apidocs/web-extensibility-api-11/model-api/).
 {{% /alert %}}
 
-The code below uses the `appExplorer` API's `addContextMenu` method to add the menu to all `Microflow` document nodes. When this menu is clicked, the clicked document's ID will be sent as an argument through the `DocumentContext` argument parameter of the menu.
+The code below uses the `appExplorer` API's `addContextMenu` method to add the menu to all `Microflow` document nodes. When this menu is clicked, the document's Id is sent as an argument through the `DocumentContext` argument parameter of the menu.
 
 ```typescript
 import { ComponentContext, DocumentContext, IComponent, Menu, getStudioProApi } from "@mendix/extensions-api";
@@ -49,9 +49,9 @@ export const component: IComponent = {
 };
 ```
 
-The `DocumentContext` payload for the menu action is an object containing a document Id (`{ documentId: string }`). When creating a menu for the `appExplorer`'s `addContextMenu` method, the `DocumentContext` should be used as the context of your menu. The `documentId` will be the Id of the document the menu is attached to (in this scenario, the exact `Microflow` node in the App Explorer).
+The `DocumentContext` payload for the menu action is an object containing a document Id (`{ documentId: string }`). When creating a menu for the `appExplorer`'s `addContextMenu` method, the `DocumentContext` should be used as the context of your menu. The `documentId` will be the Id of the document the menu is attached to (in this example, the exact `Microflow` node in the App Explorer).
 
-As explained in the [menu documentation](/apidocs-mxsdk/apidocs/web-extensibility-api-11/menu/), the `DocumentContext` is not necessary in order to add your menu to Studio Pro, but if it is not used, the menu will never receive the ID of the clicked document when it gets clicked.
+As explained in the [menu documentation](/apidocs-mxsdk/apidocs/web-extensibility-api-11/menu/), the `DocumentContext` is not necessary to add your menu to Studio Pro. However, if it is not used, the menu will not receive the clicked document's ID.
 
 ## Extensibility Feedback