acrolinx

Author: gewarren

docs/ide/code-snippets.md

@@ -22,7 +22,7 @@ ms.workload:
 ---
 # Code snippets
 
-Code snippets are small blocks of reusable code that can be inserted in a code file using a context menu command or a combination of hotkeys. They typically contain commonly-used code blocks such as `try-finally` or `if-else` blocks, but they can be used to insert entire classes or methods.
+Code snippets are small blocks of reusable code that can be inserted in a code file using a context menu command or a combination of hotkeys. They typically contain commonly used code blocks such as `try-finally` or `if-else` blocks, but they can be used to insert entire classes or methods.
 
 Code snippets are available for a multitude of languages, including C#, C++, Visual Basic, XML, and T-SQL, to name a few. To view all the available installed snippets for a language, open the **Code Snippets Manager** from the **Tools** menu in Visual Studio, and choose the language from the drop-down menu at the top.
 
@@ -68,7 +68,7 @@ if (true)
 
 Snippets can contain replacement parameters, which are placeholders that you must replace to fit the precise code you are writing. In the previous example `true` is a replacement parameter, which you would replace with the appropriate condition. The replacement you make is repeated for every instance of the same replacement parameter in the snippet.
 
-For example, in Visual Basic there is a code snippet that inserts a property. To insert the snippet, choose **Snippet** > **Insert Snippet** from the right-click or context menu in a Visual Basic code file. Then, choose **Code Patterns** > **Properties, Procedures, Events** > **Define a Property**.
+For example, in Visual Basic there's a code snippet that inserts a property. To insert the snippet, choose **Snippet** > **Insert Snippet** from the right-click or context menu in a Visual Basic code file. Then, choose **Code Patterns** > **Properties, Procedures, Events** > **Define a Property**.
 
 ![Code snippet menu for Define a Property](media/code-snippets-vb-property.png)
 

docs/test/unit-testing-a-visual-cpp-dll-for-store-apps.md

@@ -129,7 +129,7 @@ This topic describes one way to create unit tests for a C++ DLL for Universal Wi
 
     2.  On the RooterLib Project Properties dialog box, expand **Common Properties** and choose **Framework and References**.
 
-    3.  Choose **Add New Reference.**
+    3.  Choose **Add New Reference**
 
     4.  In the **Add Reference** dialog box, expand **Solution** and then choose **Projects**. Then select the **RouterLib** item.
 

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

@@ -15,7 +15,7 @@ ms.workload:
 ---
 # InitializeCorrelation Activity Designer
 
-The **InitializeCorrelation** activity designer is used to create and configure an <xref:System.ServiceModel.Activities.InitializeCorrelation> activity that is used to establish a correlation between messages prior to sending or receiving them.
+The **InitializeCorrelation** activity designer is used to create and configure an <xref:System.ServiceModel.Activities.InitializeCorrelation> activity. The <xref:System.ServiceModel.Activities.InitializeCorrelation> activity establishes a correlation between messages before sending or receiving them.
 
 ## The InitializeCorrelation Activity
 
@@ -25,21 +25,21 @@ An <xref:System.ServiceModel.Activities.InitializeCorrelation> activity is used
 
 Access the **InitializeCorrelation** activity designer in the **Messaging** category of the **Toolbox**.
 
-The **InitializeCorrelation** activity designer can be dragged from the **Toolbox** and dropped on to the Workflow Designer surface. This creates a <xref:System.ServiceModel.Activities.InitializeCorrelation> activity with a default <xref:System.Activities.Activity.DisplayName%2A> of InitializeCorrelation.The <xref:System.Activities.Activity.DisplayName%2A> can be edited in the header of the **InitializeCorrelation** activity designer or in the **DisplayName** box of the **Properties** window.
+The **InitializeCorrelation** activity designer can be dragged from the **Toolbox** and dropped on to the Workflow Designer surface. Dropping the activity designer creates a <xref:System.ServiceModel.Activities.InitializeCorrelation> activity with a default <xref:System.Activities.Activity.DisplayName%2A> of InitializeCorrelation. The <xref:System.Activities.Activity.DisplayName%2A> can be edited in the header of the **InitializeCorrelation** activity designer or in the **DisplayName** box of the **Properties** window.
 
 The <xref:System.ServiceModel.Activities.CorrelationHandle> can be specifies in the **Correlation** field in **Properties** window on the **InitializeCorrelation** activity designer surface.
 
-To display the **Initialize Correlation** dialog box where you can specify the correlation handle and the key-value pairs used to initialize it, select the ellipsis button next to the **CorrelationData** field in **Properties** window. Or, select the "View ..." hint text on  the **InitializeCorrelation** activity designer surface. For more information about using this dialog box, see the [Type Collection Editor Dialog Box](../workflow-designer/type-collection-editor-dialog-box.md) topic.
+To display the **Initialize Correlation** dialog box where you can specify the correlation handle and the key-value pairs used to initialize it, select the ellipsis button next to the **CorrelationData** field in **Properties** window. Or, select the "View ..." hint text on  the **InitializeCorrelation** activity designer surface. For more information about using this dialog box, see the [Type Collection Editor Dialog Box](../workflow-designer/type-collection-editor-dialog-box.md) article.
 
 ### The InitializeCorrelation Properties
 
-The following table shows the <xref:System.ServiceModel.Activities.InitializeCorrelation> properties and describes how they are used in the designer. These properties can be edited in **Properties** window or on Workflow Designer surface.
+The following table shows the <xref:System.ServiceModel.Activities.InitializeCorrelation> properties and describes how they're used in the designer. These properties can be edited in **Properties** window or on Workflow Designer surface.
 
 |Property Name|Required|Usage|
 |-------------------|--------------|-----------|
-|<xref:System.Activities.Activity.DisplayName%2A>|False|The friendly name of the <xref:System.ServiceModel.Activities.InitializeCorrelation> activity. The default value is InitializeCorrelation.<br /><br /> Although the use of a non-default value for the friendly <xref:System.Activities.Activity.DisplayName%2A> is not strictly required, it is a best practice to use such a value.|
+|<xref:System.Activities.Activity.DisplayName%2A>|False|The friendly name of the <xref:System.ServiceModel.Activities.InitializeCorrelation> activity. The default value is InitializeCorrelation.<br /><br /> Although the use of a non-default value for the friendly <xref:System.Activities.Activity.DisplayName%2A> isn't strictly required, it is recommended.|
 |<xref:System.ServiceModel.Activities.InitializeCorrelation.Correlation%2A>|False|The <xref:System.ServiceModel.Activities.CorrelationHandle> used to associate workflow activities in the correlation.|
-|<xref:System.ServiceModel.Activities.InitializeCorrelation.CorrelationData%2A>|False|A dictionary of correlation data that relates messages to the workflow instance.<br /><br /> Use the **Initialize Correlation** dialog box to configure the <xref:System.ServiceModel.Activities.InitializeCorrelation.CorrelationData%2A>. For more information about the use this dialog box, see the [Type Collection Editor Dialog Box](../workflow-designer/type-collection-editor-dialog-box.md) topic.|
+|<xref:System.ServiceModel.Activities.InitializeCorrelation.CorrelationData%2A>|False|A dictionary of correlation data that relates messages to the workflow instance.<br /><br /> Use the **Initialize Correlation** dialog box to configure the <xref:System.ServiceModel.Activities.InitializeCorrelation.CorrelationData%2A>. For more information about the use this dialog box, see the [Type Collection Editor Dialog Box](../workflow-designer/type-collection-editor-dialog-box.md) article.|
 
 ## See also
 

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

@@ -37,7 +37,7 @@ The following table shows the <xref:System.ServiceModel.Activities.Receive> prop
 |-------------------|--------------|-----------|
 |<xref:System.Activities.Activity.DisplayName%2A>|False|Specifies the friendly name of the <xref:System.ServiceModel.Activities.Receive> activity. The default value is Receive.<br /><br /> Although the use of a non-default value for the friendly <xref:System.Activities.Activity.DisplayName%2A> is not strictly required, it is a best practice to use such a value.|
 |<xref:System.ServiceModel.Activities.Receive.OperationName%2A>|True|Specifies the name of the service operation implemented by this <xref:System.ServiceModel.Activities.Receive> activity. This property is used to construct the default value for the **Action** property if the **Action** property is not explicitly set.|
-|<xref:System.ServiceModel.Activities.Receive.ServiceContractName%2A>|False|Specifies the name of the service contract. This property is used to group service operations into individual service contracts. All <xref:System.ServiceModel.Activities.Receive> activities that have the same <xref:System.ServiceModel.Activities.Receive.ServiceContractName%2A> are grouped into the same service contract (WSDL Port Type). The default value is the fully-qualified CLR name of the top level (root) activity.|
+|<xref:System.ServiceModel.Activities.Receive.ServiceContractName%2A>|False|Specifies the name of the service contract. This property is used to group service operations into individual service contracts. All <xref:System.ServiceModel.Activities.Receive> activities that have the same <xref:System.ServiceModel.Activities.Receive.ServiceContractName%2A> are grouped into the same service contract (WSDL Port Type). The default value is the fully qualified CLR name of the top level (root) activity.|
 |<xref:System.ServiceModel.Activities.Receive.Content%2A>|False|Specifies the message or parameter content to receive. It can be either a <xref:System.ServiceModel.Activities.ReceiveMessageContent> activity or a <xref:System.ServiceModel.Activities.ReceiveParametersContent> activity. Edit this property by selecting the ellipsis button beside the **Content** field in property grid or clicking the **Define...** button beside the **Content** label on the **Receive** activity designer surface. Both display the **Content Definition** dialog. For more information about how to use this box, see the [Content Definition Dialog Box](../workflow-designer/content-definition-dialog-box.md) topic.|
 |<xref:System.ServiceModel.Activities.Receive.CorrelatesOn%2A>|False|Specifies the correlations between <xref:System.ServiceModel.Activities.Receive> activities in service operations of a workflow with a <xref:System.ServiceModel.MessageQuerySet> object. Click the ellipsis button next to the <xref:System.ServiceModel.Activities.Receive.CorrelatesOn%2A> property in the properties grid to open the **CorrelatesOn Definition** dialog box. For more information about the use of this dialog box, see the [Content Definition Dialog Box](../workflow-designer/content-definition-dialog-box.md) topic.|
 |<xref:System.ServiceModel.Activities.Receive.CorrelatesWith%2A>|False|Specifies the <xref:System.ServiceModel.Activities.CorrelationHandle> used to route the message to the appropriate workflow instance.<br /><br /> Click the ellipsis button next to the <xref:System.ServiceModel.Activities.Receive.CorrelatesWith%2A> property in the properties grid to open the **Expression Editor** dialog box. For more information about the use of this dialog box, see the [How to: Use the Expression Editor](../workflow-designer/how-to-use-the-expression-editor.md) topic.|

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

@@ -45,7 +45,7 @@ The following table shows the <xref:System.ServiceModel.Activities.Send> propert
 |<xref:System.ServiceModel.Activities.Send.ProtectionLevel%2A>|True|Specifies the <xref:System.Net.Security.ProtectionLevel> for the message.<br /><br /> 1.  <xref:System.Net.Security.ProtectionLevel> means authentication only.<br />2.  <xref:System.Net.Security.ProtectionLevel> means sign data to help ensure the integrity of transmitted data.<br />3.  <xref:System.Net.Security.ProtectionLevel> means encrypt and sign data to help ensure the confidentiality and integrity of transmitted data.|
 |<xref:System.ServiceModel.Activities.Send.SerializerOption%2A>|True|The serializer to use for the service operation to be called by the <xref:System.ServiceModel.Activities.Send> activity. The default value is <xref:System.Runtime.Serialization.DataContractSerializer>, which serializes and deserializes an instance of a type into an XML stream or document using a supplied data contract.|
 |<xref:System.ServiceModel.Activities.Send.Action%2A>|False|Specifies the action header of the message. If it is not explicitly set, its value defaults to: https://tempuri.org/{service contract namespace}/{service contract name}/{operation name}. If specified on a <xref:System.ServiceModel.Activities.Send> activity, the <xref:System.ServiceModel.Activities.Receive> activity that receives the message must have the same value for the message to be delivered correctly.|
-|<xref:System.ServiceModel.Activities.Send.TokenImpersonationLevel%2A>||The <xref:System.Security.Principal.TokenImpersonationLevel> allowed for the receiver of the message. It defines security impersonation levels which govern the degree to which a server process can act on behalf of a client process.<xref:System.Security.Principal.TokenImpersonationLevel> indicates that an impersonation level is not assigned. <xref:System.Security.Principal.TokenImpersonationLevel> indicates that the server process cannot obtain identification information about the client and it cannot impersonate the client. <xref:System.Security.Principal.TokenImpersonationLevel> indicates that the server process can obtain information about the client, such as security identifiers and privileges, but that it cannot impersonate the client. This is useful for servers that export their own objects, for example, database products that export tables and views. Using the retrieved client-security information, the server can make access-validation decisions without being able to use other services that are using the client's security context. <xref:System.Security.Principal.TokenImpersonationLevel> indicates that the server process can impersonate the client's security context on its local system. The server cannot impersonate the client on remote systems. <xref:System.Security.Principal.TokenImpersonationLevel> indicates that the server process can impersonate the client's security context on remote systems.|
+|<xref:System.ServiceModel.Activities.Send.TokenImpersonationLevel%2A>||The <xref:System.Security.Principal.TokenImpersonationLevel> allowed for the receiver of the message. It defines security impersonation levels, which govern the degree to which a server process can act on behalf of a client process.<xref:System.Security.Principal.TokenImpersonationLevel> indicates that an impersonation level is not assigned. <xref:System.Security.Principal.TokenImpersonationLevel> indicates that the server process cannot obtain identification information about the client and it cannot impersonate the client. <xref:System.Security.Principal.TokenImpersonationLevel> indicates that the server process can obtain information about the client, such as security identifiers and privileges, but that it cannot impersonate the client. This is useful for servers that export their own objects, for example, database products that export tables and views. Using the retrieved client-security information, the server can make access-validation decisions without being able to use other services that are using the client's security context. <xref:System.Security.Principal.TokenImpersonationLevel> indicates that the server process can impersonate the client's security context on its local system. The server cannot impersonate the client on remote systems. <xref:System.Security.Principal.TokenImpersonationLevel> indicates that the server process can impersonate the client's security context on remote systems.|
 |<xref:System.ServiceModel.Activities.Send.Endpoint%2A>||The <xref:System.ServiceModel.Endpoint> that the <xref:System.ServiceModel.Activities.Send> activity sends the message to. If this property is set the <xref:System.ServiceModel.Activities.Send.EndpointConfigurationName%2A> property should be **null**.|
 |<xref:System.ServiceModel.Activities.Send.EndpointAddress%2A>||The <xref:System.ServiceModel.EndpointAddress> to which the message is sent.|
 |<xref:System.ServiceModel.Activities.Send.EndpointConfigurationName%2A>||The name of the endpoint configuration. This property is set when you are configuring an endpoint in a configuration file. This property should be set to the name given in the **\<endpoint>** element in your configuration file. If this property is set, the <xref:System.ServiceModel.Activities.Send.Endpoint%2A> property should be **null**.|