Merge pull request #685 from MicrosoftDocs/gewarren-ellipses

Changed ellipses to ellipsis where it was singular

Author: ghogen

docs/extensibility/debugger/reference/idebugmodule3-getsymbolinfo.md

@@ -66,7 +66,7 @@ int GetSymbolInfo(
 >  The returned string (in the `MODULE_SYMBOL_SEARCH_INFO` structure) could be empty even if `S_OK` is returned. In this case, there was no search information to return.  
   
 ## Remarks  
- If the `bstrVerboseSearchInfo` field of the `MODULE_SYMBOL_SEARCH_INFO` structure is not empty, then it contains a list of paths searched and the results of that search. The list is formatted with a path, followed by ellipses ("..."), followed by the result. If there is more than one path result pair, then each pair is separated by a "\r\n" (carriage-return/linefeed) pair. The pattern looks like this:  
+ If the `bstrVerboseSearchInfo` field of the `MODULE_SYMBOL_SEARCH_INFO` structure is not empty, then it contains a list of paths searched and the results of that search. The list is formatted with a path, followed by an ellipsis ("..."), followed by the result. If there is more than one path result pair, then each pair is separated by a "\r\n" (carriage-return/linefeed) pair. The pattern looks like this:  
 
  \<path>...\<result>\r\n\<path>...\<result>\r\n\<path>...\<result>  
 

docs/extensibility/debugger/reference/module-symbol-search-info.md

@@ -61,7 +61,7 @@ public struct MODULE_SYMBOL_SEARCH_INFO {
 ## Remarks  
  This structure is returned from a call to the [GetSymbolInfo](../../../extensibility/debugger/reference/idebugmodule3-getsymbolinfo.md) method.  
 
- If the `bstrVerboseSearchInfo` field is not empty, then it contains a list of paths searched and the results of that search. The list is formatted with a path, followed by ellipses ("..."), followed by the result. If there is more than one path result pair, then each pair is separated by a "\r\n" (carriage-return/linefeed) pair. The pattern looks like this:  
+ If the `bstrVerboseSearchInfo` field is not empty, then it contains a list of paths searched and the results of that search. The list is formatted with a path, followed by an ellipsis ("..."), followed by the result. If there is more than one path result pair, then each pair is separated by a "\r\n" (carriage-return/linefeed) pair. The pattern looks like this:  
 
  \<path>...\<result>\r\n\<path>...\<result>\r\n\<path>...\<result>  
 

docs/workflow-designer/bind-to-an-activity-s-property-dialog-box-legacy.md

@@ -35,7 +35,7 @@ This topic describes how use the **Bind to an Activity's Property** dialog box i
 
  An instance type of dependency property can be bound to another activity's public property or event. For more information about activity binding, see [Using Dependency Properties](http://go.microsoft.com/fwlink?LinkID=65007).  
 
- You select a property to bind to using the **Bind to an Activity's Property** dialog box. You open this dialog box by clicking the ellipses **[...]** at the end of the selected property's text box in the **Properties** window, or by clicking the blue exclamation mark icon that appears next to the property name in the property browser.  
+ You select a property to bind to using the **Bind to an Activity's Property** dialog box. You open this dialog box by clicking the ellipsis **[...]** at the end of the selected property's text box in the **Properties** window, or by clicking the blue exclamation mark icon that appears next to the property name in the property browser.  
 
  The following table describes the user interface (UI) elements of the **Bind to an Activity's Property** dialog box.  
 

docs/workflow-designer/browse-and-select-a-dotnet-type-dialog-box-legacy.md

@@ -33,7 +33,7 @@ translation.priority.ht:
 # Browse and Select a .NET Type Dialog Box (Legacy)
 This topic describes how use the **Browse and Select a .NET Type** dialog box in the legacy [!INCLUDE[wfd1](../workflow-designer/includes/wfd1_md.md)]. Use the legacy [!INCLUDE[wfd2](../workflow-designer/includes/wfd2_md.md)] when you need to target either the [!INCLUDE[netfx35_long](../workflow-designer/includes/netfx35_long_md.md)] or the [!INCLUDE[vstecwinfx](../workflow-designer/includes/vstecwinfx_md.md)].  
 
- In the **Properties** window, when you select properties that take a .NET Framework type in a referenced assembly, an ellipses **[...]** appears at the end of the property's text box. Clicking the **[...]** opens the **Browse and Select a .NET Type** dialog box. In this dialog box, you can pick a type from a tree view of the referenced assemblies. For example, when you are using the Activity Designer, in the **Properties** window, click the **Base Class** ellipses **[...]** to select another base class for an activity from the Referenced Assemblies tree.  
+ In the **Properties** window, when you select properties that take a .NET Framework type in a referenced assembly, an ellipsis **[...]** appears at the end of the property's text box. Clicking the **[...]** opens the **Browse and Select a .NET Type** dialog box. In this dialog box, you can pick a type from a tree view of the referenced assemblies. For example, when you are using the Activity Designer, in the **Properties** window, click the **Base Class** ellipsis **[...]** to select another base class for an activity from the Referenced Assemblies tree.  
 
  The following table describes the user interface (UI) elements of the **Browse and Select a .NET Type** dialog box.  
 

docs/workflow-designer/how-to-create-a-declarative-rule-condition-legacy.md

@@ -59,7 +59,7 @@ This topic describes how to declare a rule condition using the legacy [!INCLUDE[
 
 4.  Click the **ConditionName** property.  
 
-5.  Click the **ConditionName** ellipses **[...]** to open the **Select Condition** dialog box.  
+5.  Click the **ConditionName** ellipsis **[...]** to open the **Select Condition** dialog box.  
 
 6.  Click **New Condition** to open the **Rule Condition Editor** dialog box.  
 

docs/workflow-designer/how-to-create-a-policyactivity-rule-set-legacy.md

@@ -48,15 +48,15 @@ This topic describes how to create a policy activity rule set using the legacy [
 
 3.  Do one of the following:  
 
-    -   Click the **RuleSetReference** ellipses **[...]**, and then select an existing rule set in the [Select Rule Set Dialog Box (Legacy)](../workflow-designer/select-rule-set-dialog-box-legacy.md). Then go to step 10.  
+    -   Click the **RuleSetReference** ellipsis **[...]**, and then select an existing rule set in the [Select Rule Set Dialog Box (Legacy)](../workflow-designer/select-rule-set-dialog-box-legacy.md). Then go to step 10.  
 
          -or-  
 
-    -   Type a name for a rule set. Click the **RuleSetReference** ellipses **[...]**, and then select **Edit** in the [Select Rule Set Dialog Box (Legacy)](../workflow-designer/select-rule-set-dialog-box-legacy.md).  
+    -   Type a name for a rule set. Click the **RuleSetReference** ellipsis **[...]**, and then select **Edit** in the [Select Rule Set Dialog Box (Legacy)](../workflow-designer/select-rule-set-dialog-box-legacy.md).  
 
          -or-  
 
-    -   Type a name for a rule set. Expand the **RuleSetReference** property and select the ellipses **[...]** in the **RuleSet Definition** property.  
+    -   Type a name for a rule set. Expand the **RuleSetReference** property and select the ellipsis **[...]** in the **RuleSet Definition** property.  
 
          The [Rule Set Editor Dialog Box (Legacy)](../workflow-designer/rule-set-editor-dialog-box-legacy.md) opens.  
 

docs/workflow-designer/invokedelegate.md

@@ -46,7 +46,7 @@ The **InvokeDelegate** designer is used to create and configure an <xref:System.
 |-------------------|--------------|-----------|  
 |<xref:System.Activities.Activity.DisplayName%2A>|False|The friendly name of the <xref:System.Activities.Statements.InvokeDelegate> activity. The default value is InvokeDelegate.<br /><br /> Although the <xref:System.Activities.Activity.DisplayName%2A> is not strictly required, it is a best practice to use one.|  
 |<xref:System.Activities.Statements.InvokeDelegate.Delegate%2A>|True|The name of the <xref:System.Activities.ActivityDelegate> to be called when the activity executes. This property can be edited on designer surface. This is a mandatory property.|  
-|<xref:System.Activities.Statements.InvokeDelegate.DelegateArguments%2A>|False|The argument collection of the called delegate. The keys are the names of the parameter objects on the <xref:System.Activities.ActivityDelegate> and the values are the arguments whose expressions are evaluated and assigned to the corresponding parameter objects. In the property grid, click the ellipses button in the **DelegateArguments** field, it displays the **DelegateArguments** dialog to let you set this property. Click the **Create Argument** field to add the arguments.|  
+|<xref:System.Activities.Statements.InvokeDelegate.DelegateArguments%2A>|False|The argument collection of the called delegate. The keys are the names of the parameter objects on the <xref:System.Activities.ActivityDelegate> and the values are the arguments whose expressions are evaluated and assigned to the corresponding parameter objects. In the property grid, click the ellipsis button in the **DelegateArguments** field, it displays the **DelegateArguments** dialog to let you set this property. Click the **Create Argument** field to add the arguments.|  
 
 ## See Also  
  [How to: Define and consume activity delegates in the Workflow Designer](../workflow-designer/how-to-define-and-consume-activity-delegates-in-the-workflow-designer.md)

docs/workflow-designer/invokemethod-activity-designer.md

@@ -46,7 +46,7 @@ translation.priority.ht:
 |-------------------|--------------|-----------|  
 |<xref:System.Activities.Activity.DisplayName%2A>|False|The friendly name of the <xref:System.Activities.Statements.InvokeMethod> activity. The default value is InvokeMethod.<br /><br /> Although the <xref:System.Activities.Activity.DisplayName%2A> is not strictly required, it is a best practice to use one.|  
 |<xref:System.Activities.Statements.InvokeMethod.MethodName%2A>|True|The name of the method to be called when the activity executes. The called method must be declared as **public**. This property can be edited on designer surface. This is a mandatory property.|  
-|<xref:System.Activities.Statements.InvokeMethod.Parameters%2A>|False|The parameter collection of the called method. The parameters must be added to the collection in the same order that they appear in the method signature. In the property grid, click the ellipses button in the **Parameters** field, it displays the **Parameters** dialog to let you set this property. Click the **Create Argument** button to add the parameters.|  
+|<xref:System.Activities.Statements.InvokeMethod.Parameters%2A>|False|The parameter collection of the called method. The parameters must be added to the collection in the same order that they appear in the method signature. In the property grid, click the ellipsis button in the **Parameters** field, it displays the **Parameters** dialog to let you set this property. Click the **Create Argument** button to add the parameters.|  
 |<xref:System.Activities.Statements.InvokeMethod.Result%2A>|False|The return value of the method call.|  
 |<xref:System.Activities.Statements.InvokeMethod.RunAsynchronously%2A>|True|Specifies whether the method is called asynchronously. The default value is **False**.|  
 |<xref:System.Activities.Statements.InvokeMethod.TargetObject%2A>|False|The object that contains the method to call. This property can be edited on designer surface.<br /><br /> Either the <xref:System.Activities.Statements.InvokeMethod.TargetObject%2A> or the <xref:System.Activities.Statements.InvokeMethod.TargetType%2A> is required to be set.|  

docs/workflow-designer/using-the-legacy-activity-designer.md

@@ -59,7 +59,7 @@ This topic describes how to use the activity designer in the legacy [!INCLUDE[wf
 |Property|Comments|  
 |--------------|--------------|  
 |**Name**|Name of the activity.|  
-|**Base Class**|Base class that the activity derives from. The default base class is [SequenceActivity](http://go.microsoft.com/fwlink?LinkID=65020). In the **Properties** window, click the **Base Class** ellipses **[...]** to select another base class in the [Browse and Select a .NET Type Dialog Box (Legacy)](../workflow-designer/browse-and-select-a-dotnet-type-dialog-box-legacy.md).|  
+|**Base Class**|Base class that the activity derives from. The default base class is [SequenceActivity](http://go.microsoft.com/fwlink?LinkID=65020). In the **Properties** window, click the **Base Class** ellipsis **[...]** to select another base class in the [Browse and Select a .NET Type Dialog Box (Legacy)](../workflow-designer/browse-and-select-a-dotnet-type-dialog-box-legacy.md).|  
 |**Description**|User-defined description of the activity.|  
 |**Enabled**|Set to **True** by default to enable activity execution and validation. Set to **False** to disable activity execution and validation. For information about activity execution and validation, see [Developing Workflow Activities](http://go.microsoft.com/fwlink?LinkID=65024).|