Merge pull request #4478 from gewarren/2824

Remove empty article "nesting shapes"

Author: American-Dipper

.openpublishing.redirection.json

@@ -2040,6 +2040,11 @@
             "redirect_url": "/visualstudio/modeling/create-uml-modeling-projects-and-diagrams",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/modeling/nesting-shapes.md",
+            "redirect_url": "/visualstudio/modeling/customizing-presentation-on-the-diagram",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/modeling/open-a-uml-model-by-using-the-visual-studio-api.md",
             "redirect_url": "/visualstudio/modeling/create-uml-modeling-projects-and-diagrams",
@@ -2205,10 +2210,10 @@
             "redirect_url": "/visualstudio/port-migrate-and-upgrade-visual-studio-projects",
             "redirect_document_id": false
         },
-        { 
-            "source_path": "docs/porting/port-migrate-upgrade-visual-studio-projects-2019.md", 
-            "redirect_url": "/visualstudio/porting/port-migrate-and-upgrade-visual-studio-projects", 
-            "redirect_document_id": false 
+        {
+            "source_path": "docs/porting/port-migrate-upgrade-visual-studio-projects-2019.md",
+            "redirect_url": "/visualstudio/porting/port-migrate-and-upgrade-visual-studio-projects",
+            "redirect_document_id": false
         },
         {
             "source_path": "docs/profiling/analyze-cpu-usage-in-a-windows-universal-app.md",

docs/modeling/customizing-presentation-on-the-diagram.md

@@ -10,8 +10,9 @@ manager: jillfra
 ms.workload:
   - "multiple"
 ---
-# Customizing Presentation on the Diagram
-The diagram is the main presentation area of a domain-specific language designer. Usually, users will use the diagram to construct their models. You can customize the diagram as described in the following topics.
+# Customize presentation on the diagram
+
+The diagram is the main presentation area of a domain-specific language designer. Usually, users will use the diagram to construct their models. You can customize the diagram as described in the following articles:
 
 - [Defining Shapes and Connectors](../modeling/defining-shapes-and-connectors.md)
 
@@ -23,10 +24,8 @@ The diagram is the main presentation area of a domain-specific language designer
 
 - [Setting a Background Image on a Diagram](../modeling/setting-a-background-image-on-a-diagram.md)
 
-- [Nesting Shapes](../modeling/nesting-shapes.md)
-
 - [Embedding a Diagram in a Windows Form](../modeling/embedding-a-diagram-in-a-windows-form.md)
 
-## See Also
+## See also
 
 - [Navigating and Updating a Model in Program Code](../modeling/navigating-and-updating-a-model-in-program-code.md)

docs/modeling/defining-shapes-and-connectors.md

@@ -8,11 +8,13 @@ manager: jillfra
 ms.workload:
   - "multiple"
 ---
-# Defining Shapes and Connectors
+# Define shapes and connectors
+
 There are several basic types of shapes that you can used to display information on a diagram in a domain-specific language (DSL).
 
 ## <a name="shapeTypes"></a> Basic Types of Shapes and Connectors
- A DSL diagram shows a collection of *shapes* interlinked by lines or *connectors*.  Typically, but not always:
+
+A DSL diagram shows a collection of *shapes* interlinked by lines or *connectors*. Typically, but not always:
 
 - Shapes are the visible representation of model elements.
 
@@ -22,18 +24,19 @@ There are several basic types of shapes that you can used to display information
 
 - Embedding relationships between model elements are shown by containment. For example, elements representing component ports are embedded in the component.
 
-  These patterns are not enforced, but are more strongly supported. When you design a DSL, bear in mind that the design of the embedding relationships should be influenced by how you want to present the model on the screen. By contrast, the reference relationships should reflect the concepts of your business domain.
+These patterns are not enforced, but are more strongly supported. When you design a DSL, bear in mind that the design of the embedding relationships should be influenced by how you want to present the model on the screen. By contrast, the reference relationships should reflect the concepts of your business domain.
 
-  The following types of shapes are available:
+The following types of shapes are available:
 
 |Shape type|Description|
 |-|-|
-|Geometry shape|General purpose rectangular or elliptical shape. You can display text and icon decorators in specific positions relative to the bounds of the shape.<br /><br /> To nest shapes inside geometry shapes, see [Nesting Shapes](../modeling/nesting-shapes.md).|
+|Geometry shape|General purpose rectangular or elliptical shape. You can display text and icon decorators in specific positions relative to the bounds of the shape. You can also nest shapes inside geometry shapes.|
 |Compartment shape|Rectangle containing a header and compartments, like a UML class. Each compartment can contain a list of text rows.<br /><br /> The rows typically represent elements embedded under the element represented by the shape. For an example, create a DSL from the Class Diagrams solution template.|
 |Image shape|Shape that displays an image.|
 |Port shape|A small rectangle designed to attach to the outline of another shape. Typically used in component models.<br /><br /> The model element represented by a port is typically embedded under the element represented by the parent shape. For an example, create a DSL by using the Components solution template.<br /><br /> By default, a port shape can slide along the sides of its parent. You can define a Bounds Rule to constrain it to a particular position.<br /><br /> By making a port shape very small and transparent, you can use it to provide a fixed connection point on the surface of its parent shape.|
 |Swimlanes|Swimlanes partition a diagram into horizontal or vertical segments. The swimlane always stays underneath the other shapes on the diagram.<br /><br /> Typically the model elements of the swimlane are parented on the model root, and the other elements are parented on them. For an example, create a DSL from the Task Flow solution template.|
 |Connectors|The lines drawn between shapes typically represent reference relationships. You can set options to make a connector straight or rectilinear, and to have different types of arrowhead.|
 
-## <a name="shapeInheritance"></a> Shape Inheritance
- A shape can inherit from another shape. However, the shapes must be the same kind. For example, only a geometry shape can inherit from a geometry shape. Inherited shapes have the compartments and decorators of their base shape. Connectors can inherit from connectors.
+## Shape inheritance
+
+A shape can inherit from another shape. However, the shapes must be the same kind. For example, only a geometry shape can inherit from a geometry shape. Inherited shapes have the compartments and decorators of their base shape. Connectors can inherit from connectors.

docs/modeling/nesting-shapes.md

@@ -98,8 +98,6 @@
           href: customizing-text-and-image-fields.md
         - name: Set a Background Image on a Diagram
           href: setting-a-background-image-on-a-diagram.md
-        - name: Nest Shapes
-          href: nesting-shapes.md
         - name: Embed a Diagram in a Windows Form
           href: embedding-a-diagram-in-a-windows-form.md
       - name: Customize Tools and the Toolbox