Review View menu

Author: quinntracy

content/en/docs/refguide/modeling/menus/view-menu/_index.md

@@ -7,23 +7,23 @@ weight: 20
 
 ## Introduction
 
-Studio Pro supports a number of dockable window panes, such as the **Changes** and **Errors** panes. You can close some panes to just show the ones you need at the moment, but you can always reopen them via the **View** menu. 
+Studio Pro supports a number of dockable window panes, such as the **Changes** and **Errors** panes. You can close some panes to show only the ones you need, but you can always reopen them from the **View** menu. 
 
-Via this menu you can also enable or disable the [full screen mode](#full-screen) or [reset the layout](#restore-default-layout) of your app to the default.  
+From this menu you can also enable or disable the [full screen mode](#full-screen) or [reset the layout](#restore-default-layout) of your app to the default.  
 
 {{< figure src="/attachments/refguide/modeling/menus/view-menu/view-menu.png" alt="View Menu" width="300" >}}
 
 ## Layout of Panes {#layout-of-panes}
 
-You can change the default layout of panes and arrange them in the layout you like.
+You can change the default layout of panes and arrange them in your preferred layout.
 
 {{% alert color="info" %}}
-Note that this section describes the behavior of panes, not the behavior of documents in the working area. For more information on the behavior of documents open in the working area, see the [Document Tabs](/refguide/studio-pro-overview/#documents) section in *Studio Pro Overview*.
+This section describes the behavior of panes, not the behavior of documents in the working area. For more information on the behavior of documents open in the working area, see the [Document Tabs](/refguide/studio-pro-overview/#documents) section in *Studio Pro Overview*.
 {{% /alert %}}
 
-When you drag a pane, you can see arrows that indicate where you can position this pane. You can position the pane either inside the current pane (arrows grouped together) or make it full-window height or width (individual arrows on the borders). Each position is labelled and explained below:
+When you drag a pane, you can see arrows that indicate where you can position the pane. You can position the pane inside the current pane (arrows grouped together) or make it full-window height or width (individual arrows on the borders). Each position is labeled and explained below:
 
-{{< figure src="/attachments/refguide/modeling/menus/view-menu/interaction-with-panes.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/modeling/menus/view-menu/interaction-with-panes.png" alt="" class="no-border" >}}
 
 1. Within the current *pane* you can position a pane in one of the following ways:
 
@@ -32,8 +32,7 @@ When you drag a pane, you can see arrows that indicate where you can position th
     3. Pane-height – top
     4. Pane-height – bottom
     5. New pane as a new tab
-
-        {{% alert color="info" %}}If you try to position the pane as a new pane inside the working area, it will be opened as a dialog box.{{% /alert %}}
+    {{% alert color="info" %}}If you try to position the pane as a new pane inside the working area, it opens as a dialog box.{{% /alert %}}
 
 2. Within the current *window* you can position a pane in one of the following ways:
 
@@ -46,7 +45,7 @@ If you have several panes grouped together in tabs, you can change the position
 
 ## Menu Items
 
-Menu items of the **View** menu are described in sections below.
+Menu items of the **View** menu are described in the sections below.
 
 ### App Explorer
 
@@ -58,11 +57,11 @@ For details on this virtual AI assistant, see [Best Practice Recommender](/refgu
 
 ### Call Hierarchy
 
-The **Call Hierarchy** pane displays the call hierarchy of a document (for example, a page, a microflow, a nanoflow, and more). This pane helps you understand the application connections, allowing you to visualize both incoming and outgoing calls. For more information on the **Call Hierarchy** pane and how to interact with it, see [Call Hierarchy Pane](/refguide/call-hierarchy-pane/). 
+The **Call Hierarchy** pane displays the call hierarchy of a document (for example, a page, a microflow, or a nanoflow). This pane helps you understand the application connections and visualize both incoming and outgoing calls. For more information, see [Call Hierarchy Pane](/refguide/call-hierarchy-pane/). 
 
 ### Changes
 
-For version control-enabled apps (meaning, those with [Team Server](/developerportal/repository/team-server/) or other Git servers), the [Changes pane](/refguide/changes-pane/) shows the local changes to the app since the last commit. You can commit changes, update to the latest revision, and view the history from here. 
+For version control-enabled apps (those with [Team Server](/developerportal/repository/team-server/) or other Git servers), the [Changes pane](/refguide/changes-pane/) shows the local changes to the app since the last commit. You can commit changes, update to the latest revision, and view the history from here. 
 
 This pane has two levels, so when you zoom into a changed document, you can review all the changes within that document without going back and forth between levels. The zoomed-in level of the pane is split into two grids, with elements on the left and properties on the right. Selecting an element on the left presents the changed properties on the right:
 
@@ -78,7 +77,7 @@ The non-blocking History pane shows commits in your repository and allows you to
 
 ### Connector {#connector}
 
-The **Connector** pane displays elements that can be connected to the currently selected element. For example, when a button is selected, the **Connector** shows microflows that you can drag onto the button to connect them.
+The **Connector** pane displays elements that can be connected to the currently selected element. For example, when you select a button, the **Connector** shows microflows that you can drag onto the button to connect them.
 
 ### Console {#console}
 
@@ -124,17 +123,17 @@ The **Properties** pane displays the properties of the currently selected elemen
 
 ### Stories
 
-For [Team Server](/developerportal/repository/team-server/) app, the **Stories** pane shows the [stories](/developerportal/project-management/epics/planning/) of the current [Sprint](/developerportal/project-management/epics/planning/). For more information on the **Stories** pane and how to interact with it, see [Stories Pane](/refguide/stories-pane/). 
+For [Team Server](/developerportal/repository/team-server/) apps, the **Stories** pane shows the [stories](/developerportal/project-management/epics/planning/) of the current [Sprint](/developerportal/project-management/epics/planning/). For more information, see [Stories Pane](/refguide/stories-pane/). 
 
 ### Toolbox {#toolbox}
 
 The **Toolbox** pane displays the tools that can be used in the current editor. For example, in a page you can insert all kinds of widgets (for example, [data containers](/refguide/data-widgets/)) by dragging them from the **Toolbox** onto your page.
 
-The **Toolbox** has a tile view showing larger icons and a list view showing a list of elements. You can switch between the tile and list view modes at the lower-right corner of the **Toolbox**. 
+The **Toolbox** has a tile view showing larger icons and a list view showing a list of elements. You can switch between the tile and list view modes in the lower-right corner of the **Toolbox**. 
 
 ### Widget Developer Console
 
-This console helps you debug the configuration code of your widget that is responsible for conditionally visible properties, custom consistency checks, and **Structure mode** preview. This console shows logs from the `getProperties`, `getPreview`, `check`, and `getCustomCaption` functions, which can be defined inside the new configuration module (for more information, see the [Widget Developer Console](/apidocs-mxsdk/apidocs/pluggable-widgets-config-api/#widget-dev-console) section of *Configuration Module API for Pluggable Widgets*). 
+This console helps you debug the configuration code of your widget that is responsible for conditionally visible properties, custom consistency checks, and **Structure mode** preview. This console shows logs from the `getProperties`, `getPreview`, `check`, and `getCustomCaption` functions, which can be defined inside the configuration module. For more information, see the [Widget Developer Console](/apidocs-mxsdk/apidocs/pluggable-widgets-config-api/#widget-dev-console) section of *Configuration Module API for Pluggable Widgets*. 
 
 ### Debug Windows
 

content/en/docs/refguide/modeling/menus/view-menu/call-hierarchy-pane.md

@@ -7,9 +7,9 @@ description: "Describes the Call Hierarchy pane in Mendix Studio Pro."
 
 ## Introduction
 
-In large Mendix applications, understanding how different parts of the application interact is important for maintainability, debugging, and identifying the impact of changes. One of the most important tools for this is the Call Hierarchy tree view, which shows how documents such as Pages, Microflows, Nanoflows, and more are interconnected.
+In large Mendix applications, understanding how different parts of the application interact is important for maintainability, debugging, and identifying the impact of changes. One of the most important tools for this is the Call Hierarchy tree view, which shows how documents such as pages, microflows, and nanoflows are interconnected.
 
-This feature helps you understands dependencies and app connections. For example, what microflows are triggered from this page? Which pages call this nanoflow? If I change this microflow, what will be affected?
+This feature helps you understand dependencies and app connections. For example, what microflows are triggered from this page? Which pages call this nanoflow? If you change this microflow, what is affected?
 
 The Call Hierarchy pane consists of:
 
@@ -25,20 +25,20 @@ The Call Hierarchy tree visualizes the full call path in two directions: **Incom
 
 You can visualize the **Call Hierarchy** by right-clicking a document from the **App Explorer** or from within the document editor, then selecting **Show call hierarchy**.
 
-{{< figure src="/attachments/refguide/modeling/menus/view-menu/call-hierarchy-pane/right-click.png" width=200" >}}
+{{< figure src="/attachments/refguide/modeling/menus/view-menu/call-hierarchy-pane/right-click.png" alt="" width="200" >}}
 
- The data is calculated in the background and displayed in a tree view with the first level of the tree is expanded. Deeper levels are lazy loaded on expansion, which helps maintain performance in large projects.
+The data is calculated in the background and displayed in a tree view with the first level of the tree expanded. Deeper levels are lazy-loaded on expansion, which helps maintain performance in large projects.
 
 ## Interacting with the Call Hierarchy Pane
 
 Use the switch button in the pane to toggle between **Incoming calls** and **Outgoing calls**.
 
-* **Incoming calls** - shows the full path of where the currently-selected document is called from elsewhere in the app
-* **Outgoing calls** - shows the full path of documents that are called by the currently-selected document
+* **Incoming calls** – shows the full path of where the currently-selected document is called from elsewhere in the app
+* **Outgoing calls** – shows the full path of documents that are called by the currently-selected document
 
 ## Supported Document Types
 
-When you select **Show call hierarchy**, it is analyzed to receive its interactions with other documents.
+When you select **Show call hierarchy**, the document is analyzed to identify its interactions with other documents.
 
-* For **Incoming calls**, it shows the call hierarchy for most common identifiable document types, including pages, microflows, nanoflows, JavaScript actions, Java actions, and more
-* For **Outgoing calls**, it shows the call hierarchy for pages, microflows, nanoflows, and rules
+* For **Incoming calls**, the pane shows the call hierarchy for most common identifiable document types, including pages, microflows, nanoflows, JavaScript actions, and Java actions
+* For **Outgoing calls**, the pane shows the call hierarchy for pages, microflows, nanoflows, and rules

content/en/docs/refguide/modeling/menus/view-menu/changes-pane.md

@@ -7,16 +7,16 @@ description: "Describes the Changes pane in Mendix Studio Pro."
 
 ## Introduction 
 
-For version control enabled apps (apps with Team Server or other Git servers), the **Changes** pane shows the local changes to the app since the last commit. You can commit changes, update to the latest revision, and view the history from it. 
+For version control-enabled apps (apps with Team Server or other Git servers), the **Changes** pane shows the local changes to the app since the last commit. You can commit changes, update to the latest revision, and view the history from the pane. 
 
 {{% alert color="info" %}}
 The **Changes** pane shows your local changes since the last commit. To compare any historical revision to your current state, use the [Comparison pane](/refguide/comparison-pane/) instead. For more information, see [Comparing Revisions](/refguide/comparing-revisions/).
 {{% /alert %}}
 
 This pane consists of the following:
 
-* The [top bar](#top-bar) contains various buttons, such as **Back**, **Go to**, **Tasks**. 
-* The [top level](#top-level) shows you a list of documents that were changed, for example, a page where a widget was deleted
+* The [top bar](#top-bar) contains various buttons, such as **Back**, **Go to**, and **Tasks**
+* The [top level](#top-level) shows a list of documents that were changed, for example, a page where a widget was deleted
 * The [zoomed-in level](#zoomed-in-level) of the pane is split into two grids, with elements in the left grid and changed or conflicting properties of the selected element in the right grid
 
 ## Top Bar {#top-bar}
@@ -25,7 +25,7 @@ The top bar of the top level of the **Changes** pane consists of various buttons
 
 {{< figure src="/attachments/refguide/modeling/menus/view-menu/changes-pane/changes-top-bar.png" alt="Top Bar of the Changes Pane" class="no-border" >}}
 
-Buttons allow you to perform the following actions:
+The buttons allow you to perform the following actions:
 
 * **Back** – goes back up one level; at the top level, this button is disabled
 * **Go to** – opens a zoomed-in level and opens up the selected document 
@@ -49,13 +49,13 @@ The grid contains information on the following items:
     * **Modified** – changes to an existing document were made, such as adding or deleting elements or changing element properties; indicated with a yellow circle
     * **Deleted** – a document was deleted; indicated with a red circle with a minus
     * **Conflicted** – a document contains conflicting changes; indicated with a red circle with an exclamation mark
-* **Item** – indicates a name of the changes document
-* **Module** – a module where the changed document is
+* **Item** – indicates the name of the changed document
+* **Module** – the module where the changed document is located
 * **Details** – can contain details on the status, for example, when you have conflicting changes 
 
 ## Zoomed-In Level {#zoomed-in-level}
 
-You can zoom into a changed or conflicting document, by doing one of the following:
+You can zoom into a changed or conflicting document by doing one of the following:
 
 * Double-click a line in the grid on the top level 
 * Click the **Go to** button
@@ -67,13 +67,13 @@ There are three types of zoomed-in levels:
 
 * [For modified documents](#modified)
 * [For conflicting documents](#conflicts)
-* [For merging document](#merge-mode)
+* [For merging documents](#merge-mode)
 
-Each of them contains their own set of buttons.
+Each of them contains its own set of buttons.
 
 ### Zoomed-In Level for Modified Documents {#modified}
 
-The zoomed-in level for modified documents is split into two grids, with elements on the left and changed properties on the right. If no properties were changed for an element, for example, when an element was added or deleted, the right grid will be empty:
+The zoomed-in level for modified documents is split into two grids, with elements on the left and changed properties on the right. If no properties were changed for an element (for example, when an element was added or deleted), the right grid is empty:
 
 {{< figure src="/attachments/refguide/modeling/menus/view-menu/changes-pane/element-added.png" alt="No Properties to Show" class="no-border" >}}
 
@@ -92,9 +92,9 @@ The left side of the grid contains the following columns:
 
 The zoomed-in level for conflicted documents is split into two grids, with conflicting elements on the left and conflicting properties on the right.
 
-There are two sorts of conflict:
+There are two types of conflict:
 
-* For a standard conflict a change has been made to the same element in each branch and Mendix cannot automatically choose which is the desired change after the merge
+* For a standard conflict, a change has been made to the same element in each branch and Mendix cannot automatically choose which is the desired change after the merge
 * For a *list order* conflict, denoted by the phrase *(list order)*, Mendix can accept both changes but cannot automatically decide the order they should appear in the document
 
 The toolbar at this level contains the following buttons:
@@ -106,7 +106,7 @@ The toolbar at this level contains the following buttons:
 * **Resolve conflict using their whole document** – other branch's version is applied to all conflicted documents
 * **Show purely visual changes** – shows visual changes, such as dragging an entity to a new location in the domain model
 
-The grid on the left contains the following columns
+The grid on the left contains the following columns:
 
 * **Element** – the name of the modified element or a header identifying whether the subsequent elements conflict or have been accepted
 * **Mine** – indicates the status of the change on the current development line
@@ -121,7 +121,7 @@ The grid on the right contains the following columns:
 
 {{< figure src="/attachments/refguide/modeling/menus/view-menu/changes-pane/merge-algorithm-conflicts.png" alt="Example of conflicts format of Changes pane" class="no-border" >}}
 
-### Merge Mode{#merge-mode}
+### Merge Mode {#merge-mode}
 
 If you have chosen **Interactive Merge** when resolving conflicts, you can revise the combined changes.  
 
@@ -133,11 +133,11 @@ The toolbar will change to show the following buttons:
 * **Go to** – takes you directly to the selected element
 * **Resolve using Mine** – resolves the conflict by choosing the changes shown in the **Mine** column and discarding the changes shown in the **Theirs** column
 * **Resolve using Theirs** – resolves the conflict by choosing the changes shown in the **Theirs** column and discarding the changes shown in the **Mine** column
-* **Mark as Resolved** – either:
-    * keeps things as they were before the **Mine** and the **Theirs** changes were applied
-    * in the case of a *list order* conflict, takes the order of widgets as it is currently shown in the document (you can edit the document to ensure this is correct)
-* **Accept and Exit** – the merge is finalized and the document is saved in its merged form with no conflicts
-* **Cancel** – end merge mode and leave the document with one or more unresolved conflicts
+* **Mark as Resolved** – does one of the following:
+    * Keeps things as they were before the **Mine** and the **Theirs** changes were applied
+    * In the case of a *list order* conflict, takes the order of widgets as it is currently shown in the document (you can edit the document to ensure this is correct)
+* **Accept and Exit** – finalizes the merge and saves the document in its merged form with no conflicts
+* **Cancel** – ends merge mode and leaves the document with one or more unresolved conflicts
 * **Show purely visual changes** – shows visual changes, such as dragging an entity to a new location in the domain model
 
 The left and right panes will contain the same information as in [Zoomed-In Level for Conflicted Documents](#conflicts), above.