Small corrections based on review comments.

Author: LizCasey

docs/data-tools/how-to-add-update-or-remove-a-wcf-data-service-reference.md

@@ -55,7 +55,7 @@ A *service reference* enables a project to access one or more [!INCLUDE[ssAstori
 
 2.  Click **Discover**.
 
-     All services (both, [!INCLUDE[ssAstoria](../data-tools/includes/ssastoria_md.md)] and WCF services) in the current solution are added to the **Services** list.
+     All services (both [!INCLUDE[ssAstoria](../data-tools/includes/ssastoria_md.md)] and WCF services) in the current solution are added to the **Services** list.
 
 3.  In the **Services** list, expand the node for the service that you want to use and select an entity set.
 

docs/data-tools/how-to-assign-stored-procedures-to-perform-updates-inserts-and-deletes-o-r-designer.md

@@ -45,15 +45,15 @@ Stored procedures can be added to the **O/R Designer** and executed as typical <
 
 8.  Select the desired stored procedure in the **Customize** list.
 
-9. Inspect the list of **Method Arguments** and **Class Properties** to verify that the **Method Arguments** map to the appropriate **Class Properties**. Map the original method arguments (`Original_\<ArgumentName>`) to the original properties (`\>PropertyName>` (Original)) for the `Update` and `Delete` commands.
+9. Inspect the list of **Method Arguments** and **Class Properties** to verify that the **Method Arguments** map to the appropriate **Class Properties**. Map the original method arguments (`Original_<ArgumentName>`) to the original properties (`<PropertyName>` (Original)) for the `Update` and `Delete` commands.
 
     > [!NOTE]
     >  By default, method arguments map to class properties when the names match. If changed property names no longer match between the table and the entity class, you might have to select the equivalent class property to map to if the designer cannot determine the correct mapping.
 
 10. Click **OK** or **Apply**.
 
     > [!NOTE]
-    >  You can continue to configure the behavior for each class and behavior combination as long as you click **Apply** after you make each change. If you change the class or behavior before you click **Apply**, a warning dialog box appears and provids you an opportunity to apply your changes.
+    >  You can continue to configure the behavior for each class and behavior combination as long as you click **Apply** after you make each change. If you change the class or behavior before you click **Apply**, a warning dialog box appears and provides you an opportunity to apply your changes.
 
 To revert to using the default runtime logic for updates, click the ellipsis next to the **Insert**, **Update**, or **Delete** command in the **Properties** window and then select **Use runtime** in the **Configure Behavior** dialog box.
 

docs/data-tools/how-to-connect-to-data-in-a-service.md

@@ -23,7 +23,7 @@ ms.workload:
 
 You connect your application to the data returned from a service by running the [Data Source Configuration Wizard](../data-tools/media/data-source-configuration-wizard.png) and selecting **Service** on the **Choose a Data Source Type** page.
 
-Upon completion of the wizard, a service reference is added to your project and immediately available in the [Data Sources Window](add-new-data-sources.md).
+Upon completion of the wizard, a service reference is added to your project and is immediately available in the [Data Sources Window](add-new-data-sources.md).
 
 > [!NOTE]
 > The items that appear in the **Data Sources** window are dependent on the information that the service returns. Some services might not provide enough information for the **Data Source Configuration Wizard** to create bindable objects. For example, if the service returns an untyped dataset, no items appear in the **Data Sources Window** upon completing the wizard. This is because untyped datasets do not provide schema, so the wizard does not have enough information to create the data source.

docs/data-tools/linq-to-sql-tools-in-visual-studio2.md

@@ -13,7 +13,7 @@ ms.workload:
 ---
 # LINQ to SQL tools in Visual Studio
 
-LINQ to SQL was the first object-relational mapping technology released by Microsoft. It works well in basic scenarios and continues to be supported in **Visual Studio**, but it's no longer under active development. Use LINQ to SQL when maintaining a legacy application that's already using it, or in simple applications that use SQL Server and do not require multi-table mapping. In general, new applications should use the Entity Framework when an object-relational mapper layer is required.
+LINQ to SQL was the first object-relational mapping technology released by Microsoft. It works well in basic scenarios and continues to be supported in Visual Studio, but it's no longer under active development. Use LINQ to SQL when maintaining a legacy application that's already using it, or in simple applications that use SQL Server and do not require multi-table mapping. In general, new applications should use the Entity Framework when an object-relational mapper layer is required.
 
 In Visual Studio, you create LINQ to SQL classes that represent SQL tables by using the **Object Relational Designer** (**O/R Designer**).