Merge pull request #10367 from mendix/qt-csapi

Review Mx10 C# docs

Author: quinntracy

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/extensibility-api/csharp/_index.md

@@ -4,8 +4,6 @@ linktitle: "C# Extensibility API"
 url: /apidocs-mxsdk/apidocs/csharp-extensibility-api-10/
 description: "The C# extensibility API allows your custom Studio Pro extensions developed in C# to interact with some internal services of Studio Pro."
 weight: 10
-no_list: false
-description_list: true
 aliases:
     - /apidocs-mxsdk/apidocs/extensibility-api/
 ---
@@ -20,21 +18,25 @@ For information on new releases of the Extensibility API, see [Extensibility: C#
 
 ## Introduction
 
-Extensions can be written in C#, described here, or using a web API which is documented separately in [Extensibility API for Web Developers](/apidocs-mxsdk/apidocs/web-extensibility-api-10/).
+Extensions can be written in C#, described here, or using a web API (for more information about the Web API, see [Extensibility API for Web Developers](/apidocs-mxsdk/apidocs/web-extensibility-api-10/)).
 
-If you need to add your own custom UI to Studio Pro, you can achieve this using web technology. Your web-based UI will be rendered in Studio Pro using a hosted web view, the API provides communication functionality between your web UI and the C# extension logic.
+To add a custom UI to Studio Pro, you can use web technology. Your web-based UI will be rendered in Studio Pro through a hosted web view, and the API provides communication between your UI and the C# extension logic.
 
 ## Prerequisites
 
-* You need at least a basic understanding of the Mendix platform.
-* You need some understanding of the Mendix Model.
-* You need to have some C# development experience. Extensions are developed using [C#](https://docs.microsoft.com/en-us/dotnet/), and compiled into a `.dll` assembly file.
+To use the C# API, you must have:
+
+* A basic understanding of the Mendix platform
+* Some understanding of the Mendix Model
+* Some C# development experience
+
+Extensions are developed using [C#](https://docs.microsoft.com/en-us/dotnet/) and compiled into a `.dll` assembly file.
 
 ## Getting Started
 
-For detailed explanation on how to get started with extensions, check out [Get Started with the Extensibility API](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/get-started/).
+For detailed information on how to get started with extensions, see [Get Started with the Extensibility API](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/get-started/).
 
-You can also check out our examples and [API reference documentation](https://github.com/mendix/ExtensionAPI-Samples).
+You can also review some examples and [API reference documentation](https://github.com/mendix/ExtensionAPI-Samples).
 
 ## How-tos
 
@@ -48,18 +50,14 @@ Here is a list of how-tos for you to begin with:
 
 ## Advanced APIs
 
-APIs for the Mendix platform's advanced users:
+Below are APIs for advanced users:
 
 * [Use the Untyped Model Access API Using C#](/apidocs-mxsdk/apidocs/untyped-model-access-api-10/)
 
-## Learn More
-
-You can dive into the following topics in depth:
+## Reference Guides
 
-* [What are extension points](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/extension-points/)
-* [What are the Extensibility API services](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/services/)
-* [How to Interact with the Model API Using C#](/apidocs-mxsdk/apidocs/interact-with-model-api-10/)
-* [How to host web content via a web view wrapper](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/web-views/)
-* [How to Build a Todo Example Extension Using C#](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/build-todo-example-extension/)
+Review the following reference guides to explore additional Extensibility API topics:
 
-## Documentation in This Category
+* [Extension Points](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/extension-points/)
+* [Extensibility Services](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/services/)
+* [Extensibility Web Views](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/web-views/)

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/extensibility-api/csharp/extensibility-api-howtos/_index.md

@@ -9,4 +9,4 @@ description_list: true
 
 ## Introduction
 
-The following how-tos teach you how to use the Extensibility API for C# Developers in different use cases.
+The following how-tos describe how to use the C# Extensibility API in different use cases.

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/extensibility-api/csharp/extensibility-api-howtos/add-menu.md

@@ -7,15 +7,19 @@ weight: 15
 
 ## Introduction
 
-This how-to describes how you can add a menu that contains submenus, some of which also contain submenus of their own. Before you start this how-to, it is recommended to [Create a Menu Extension Using C#](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/create-menu-extension/) first.
+This how-to describes how to add a menu that contains sub-menus, some of which also contain sub-menus of their own. 
 
 You can download the example in this how-to in [this GitHub repository](https://github.com/mendix/ExtensionAPI-Samples).
 
+## Prerequisites
+
+This how-to uses the results of [Create a Menu Extension Using C#](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/create-menu-extension/). Complete that how-to before starting this one.
+
 ## Creating Menu Extension Class
 
-1. Open the project that you previously created when you followed [Create a Menu Extension Using C#](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/create-menu-extension/).
-2. Add a new class to the project and name it `MyMenuExtension.cs`.
-3. Replace the code in the file with the following code:
+1. Open the project you created when following [Create a Menu Extension Using C#](/apidocs-mxsdk/apidocs/csharp-extensibility-api-10/create-menu-extension/).
+2. Add a new class to the project and name it *MyMenuExtension.cs*.
+3. Replace the code in the file with the following:
 
     ```csharp
     using Mendix.StudioPro.ExtensionsAPI.UI.Menu;
@@ -57,10 +61,41 @@ You can download the example in this how-to in [this GitHub repository](https://
     }
     ```
 
-The code above creates a single menu, `Beverages`, which contains the submenus `Hot` and `Cold`, both of which contain some submenus. Note that when you are creating this menu structure, you only return the main parent menu (in this example, the `Beverages` menu) from the `GetMenus` method. You should only return the topmost parents in your list, so only the ones that do not have a parent should be returned. In the example above, there is only one.
+### Menu Structure Overview
+
+The code above creates a single menu, `Beverages`. This menu contains the following:
+
+* `Beverages` contain two sub-menus: `Hot` and `Cold`
+* `Hot` contains `Coffee` and `Tea`
+* `Coffee` contains `Black Coffee`, `Decaf`, and `Espresso` 
+* `Espresso` contains `Regular Espresso` and `Ristretto` 
+* `Cold` contains `Soda`
+
+Only the top-most parent menu (`Beverages`) is returned from the `GetMenus` method. You should only return menus that do not have a parent.
+
+### Menu Placement
+
+If an app contains one or more extensions, a top-level menu named `Extensions` will appear in the main menu bar of Studio Pro. 
+
+Menus that are created from `MenuExtension` implementations are grouped by their extension entry point name (in this example, `MyCompany`), and are placed under a dedicated sub-menu. For example, `MyMenuExtension` will be placed as follows: **Extensions** > **MyCompany** > **MyMenuExtension**.
+
+### Menu Properties
+
+A menu can either:
+
+* Be a parent (a menu that contains sub-menus), or 
+* Have an action
+
+You cannot create a menu that both contains sub-menus and has an action.
+
+#### Separators
+
+You can add a `MenuSeparator` to a menu using the `Separator` property. The options include:
 
-If an app contains one or more extensions, a top-level menu named `Extensions` will appear in the main menu bar of Studio Pro. Menus that are created from `MenuExtension` implementations will be grouped by their extension entry point name (in this example, `MyCompany`), and then placed under their own dedicated submenu under the main `Extensions` top-level menu. For example, the `MyMenuExtension` above will be placed as follows: **Extensions** > **MyCompany** > **MyMenuExtension**.
+* `After`
+* `Before` 
+* `None` (default). 
 
-A menu can only be a parent (namely, a menu that contains submenus) or have an action. You cannot create a menu with an action which also contains submenus.
+#### Enabling and Disabling Menus
 
-You can add a `MenuSeparator` to a menu, via the `Separator` property. Options are `After`, `Before` or `None`. The default value is `None`. You can also disable a menu by setting its `IsEnabled` property to `false`. Menus are enabled by default.
+Menus are enabled by default. To disable a menu, set its `IsEnabled` property to `false`.