Merge pull request #2395 from damabe/v-damabe062618

Content fixes for VS data tools articles

Author: ktoliver

docs/data-tools/troubleshooting-service-references.md

@@ -23,25 +23,25 @@ ms.workload:
 
 This topic lists common issues that may occur when you are working with Windows Communication Foundation (WCF) or WCF Data Services references in Visual Studio.
 
-## Error Returning Data from a Service
+## Error returning data from a service
 
 When you return a `DataSet` or `DataTable` from a service, you may receive a "The maximum size quota for incoming messages has been exceeded" exception. By default, the `MaxReceivedMessageSize` property for some bindings is set to a relatively small value to limit exposure to denial-of-service attacks. You can increase this value to prevent the exception. For more information, see <xref:System.ServiceModel.HttpBindingBase.MaxReceivedMessageSize%2A>.
 
 To fix this error:
 
-1.  In **Solution Explorer**, double-click the app.config file to open it.
+1.  In **Solution Explorer**, double-click the *app.config* file to open it.
 
 2.  Locate the `MaxReceivedMessageSize` property and change it to a larger value.
 
-## Cannot Find a Service in My Solution
+## Cannot find a service in my solution
 
 When you click the **Discover** button in the **Add Service References** dialog box, one or more WCF Service Library projects in the solution do not appear in the services list. This can occur if a Service Library has been added to the solution but has not yet been compiled.
 
 To fix this error:
 
 -   In **Solution Explorer**, right-click the WCF Service Library project and click **Build**.
 
-## Error Accessing a Service over a Remote Desktop
+## Error accessing a service over a remote desktop
 
 When a user accesses a Web-hosted WCF service over a remote desktop connection and the user does not have administrative permissions, NTLM authentication is used. If the user does not have administrative permissions, the user may receive the following error message: "The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'NTLM'."
 
@@ -52,15 +52,15 @@ To fix this error:
 2.  On the **Start Options** tab, clear the **NTLM Authentication** check box.
 
     > [!NOTE]
-    > You should turn off NTLM authentication only for Web sites that exclusively contain WCF services. Security for WCF services is managed through the configuration in the web.config file. This makes NTLM authentication unnecessary.
+    > You should turn off NTLM authentication only for Web sites that exclusively contain WCF services. Security for WCF services is managed through the configuration in the *web.config* file. This makes NTLM authentication unnecessary.
 
-## Access Level for Generated Classes Setting Has No Effect
+## Access level for generated classes setting has no effect
 
 Setting the **Access level for generated classes** option in the **Configure Service References** dialog box to **Internal** or **Friend** may not always work. Even though the option appears to be set in the dialog box, the resulting support classes are generated with an access level of `Public`.
 
 This is a known limitation of certain types, such as those serialized using the <xref:System.Xml.Serialization.XmlSerializer>.
 
-## Error Debugging Service Code
+## Error debugging service code
 
 When you step into the code for a WCF service from client code, you may receive an error related to missing symbols. This can occur when a service that was part of your solution was moved or removed from the solution.
 
@@ -78,13 +78,13 @@ To fix this error, you have to manually rebuild the service project:
 
 4.  Load the WCF service project.
 
-5.  In the **Configuration Manager** dialog box, set the **Active solution configuration** to **Debug**. For more information, see [How to: Create and Edit Configurations](../ide/how-to-create-and-edit-configurations.md).
+5.  In the **Configuration Manager** dialog box, set the **Active solution configuration** to **Debug**. For more information, see [How to: Create and edit configurations](../ide/how-to-create-and-edit-configurations.md).
 
 6.  In **Solution Explorer**, select the WCF service project.
 
 7.  On the **Build** menu, click **Rebuild** to rebuild the WCF service project.
 
-## WCF Data Services Do Not Display in the Browser
+## WCF Data Services do not display in the browser
 
 When it attempts to view an XML representation of data in a [!INCLUDE[ss_data_service](../data-tools/includes/ss_data_service_md.md)], Internet Explorer may misinterpret the data as an RSS feed. Make sure that the option to display RSS feeds is disabled.
 
@@ -98,6 +98,6 @@ To fix this error, disable RSS feeds:
 
 4.  Click **OK** to close the **Internet Options** dialog box.
 
-## See Also
+## See also
 
 - [Windows Communication Foundation Services and WCF Data Services in Visual Studio](../data-tools/windows-communication-foundation-services-and-wcf-data-services-in-visual-studio.md)

docs/data-tools/turn-off-constraints-while-filling-a-dataset.md

@@ -30,7 +30,7 @@ If a dataset contains constraints (such as foreign-key constraints), they can ra
 If there were no mechanism to allow temporary constraint suspension, an error would be raised every time you tried to load a record into the child table. Another way to suspend all constraints in a dataset is with the <xref:System.Data.DataRow.BeginEdit%2A>, and <xref:System.Data.DataRow.EndEdit%2A> properties.
 
 > [!NOTE]
-> Validation events (for example, <xref:System.Data.DataTable.ColumnChanging> and<xref:System.Data.DataTable.RowChanging>) will not be raised when constraints are turned off.
+> Validation events (for example, <xref:System.Data.DataTable.ColumnChanging> and <xref:System.Data.DataTable.RowChanging>) will not be raised when constraints are turned off.
 
 ## To suspend update constraints programmatically
 
@@ -41,11 +41,11 @@ If there were no mechanism to allow temporary constraint suspension, an error wo
 
 ## To suspend update constraints using the Dataset Designer
 
-1.  Open your dataset in the **Dataset Designer**. For more information, see [Walkthrough: Creating a Dataset in the Dataset Designer](walkthrough-creating-a-dataset-with-the-dataset-designer.md).
+1.  Open your dataset in the **Dataset Designer**. For more information, see [Walkthrough: Creating a dataset in the Dataset Designer](walkthrough-creating-a-dataset-with-the-dataset-designer.md).
 
 2.  In the **Properties** window, set the <xref:System.Data.DataSet.EnforceConstraints%2A> property to `false`.
 
-## See Also
+## See also
 
 - [Fill datasets by using TableAdapters](../data-tools/fill-datasets-by-using-tableadapters.md)
 - [Relationships in datasets](../data-tools/relationships-in-datasets.md)

docs/data-tools/typed-vs-untyped-datasets.md

@@ -19,7 +19,7 @@ A typed dataset is a dataset that is first derived from the base <xref:System.Da
 
  An untyped dataset, in contrast, has no corresponding built-in schema. As in a typed dataset, an untyped dataset contains tables, columns, and so on—but those are exposed only as collections. (However, after you manually create the tables and other data elements in an untyped dataset, you can export the dataset's structure as a schema by using the dataset's <xref:System.Data.DataSet.WriteXmlSchema%2A> method.)
 
-## Contrasting data access in typed and untyped datasets
+## Contrast data access in typed and untyped datasets
  The class for a typed dataset has an object model in which its properties take on the actual names of the tables and columns. For example, if you are working with a typed dataset, you can reference a column by using code such as the following:
 
  [!code-csharp[VbRaddataDatasets#4](../data-tools/codesnippet/CSharp/typed-vs-untyped-datasets_1.cs)]

docs/data-tools/update-data-by-using-a-tableadapter.md

@@ -26,7 +26,7 @@ ms.workload:
 After the data in your dataset has been modified and validated, you can send the updated data back to a database by calling the `Update` method of a [TableAdapter](../data-tools/create-and-configure-tableadapters.md). The `Update` method updates a single data table and runs the correct command (INSERT, UPDATE, or DELETE) based on the <xref:System.Data.DataRow.RowState%2A> of each data row in the table. When a dataset has related tables, Visual Studio generates a TableAdapterManager class that you  use to do the updates. The TableAdapterManager class ensures that updates are made in the correct order based on the foreign-key constraints that are defined in the database. When you use data-bound controls, the databinding architecture creates a member variable of the TableAdapterManager class called tableAdapterManager.
 
 > [!NOTE]
-> When you try to update a data source with the contents of a dataset, you can get errors.To avoid errors, we recommend that you put the code that calls the adapter's `Update` method inside a `try`/`catch` block.
+> When you try to update a data source with the contents of a dataset, you can get errors. To avoid errors, we recommend that you put the code that calls the adapter's `Update` method inside a `try`/`catch` block.
 
  The exact procedure for updating a data source can vary depending on business needs, but  includes the following steps:
 

docs/data-tools/upgrade-dot-mdf-files.md

@@ -19,7 +19,7 @@ ms.workload:
 ---
 # Upgrade .mdf files
 
-This topic describes the options for upgrading a database file (.mdf) after you install a newer version of Visual Studio. It includes instructions for the following tasks:
+This topic describes the options for upgrading a database file (*.mdf*) after you install a newer version of Visual Studio. It includes instructions for the following tasks:
 
 - Upgrade a database file to use a newer version of SQL Server Express LocalDB
 
@@ -29,15 +29,15 @@ This topic describes the options for upgrading a database file (.mdf) after you
 
 - Make SQL Server Express the default database engine
 
-You can use Visual Studio to open a  project that contains a database file (.mdf) that was created by using an older version of SQL Server Express or LocalDB. However, to continue to develop your project in Visual Studio, you must have that version of SQL Server Express or LocalDB  installed on the same machine as Visual Studio, or you must upgrade the database file. If you upgrade the database file, you won't be able to access it by using older versions of SQL Server Express or LocalDB.
+You can use Visual Studio to open a  project that contains a database file (*.mdf*) that was created by using an older version of SQL Server Express or LocalDB. However, to continue to develop your project in Visual Studio, you must have that version of SQL Server Express or LocalDB  installed on the same machine as Visual Studio, or you must upgrade the database file. If you upgrade the database file, you won't be able to access it by using older versions of SQL Server Express or LocalDB.
 
 You may also be prompted to upgrade a database file that was created through an earlier version of SQL Server Express or LocalDB if the version of the file isn't compatible with the instance of SQL Server Express or LocalDB that's currently installed. To resolve the issue, Visual Studio will prompt you to upgrade the file.
 
 > [!IMPORTANT]
 > We recommend that you back up the database file before you upgrade it.
 
 > [!WARNING]
-> If you upgrade an .mdf file that was created in LocalDB 2014 (V12) 32 bit to LocalDB 2016 (V13) or later, you will not be able to open the file again in the 32-bit version of LocalDB.
+> If you upgrade an *.mdf* file that was created in LocalDB 2014 (V12) 32 bit to LocalDB 2016 (V13) or later, you will not be able to open the file again in the 32-bit version of LocalDB.
 
 Before you upgrade a database, consider the following criteria:
 
@@ -65,7 +65,7 @@ Before you upgrade a database, consider the following criteria:
 
         -   To use a specific version: `(localdb)\ProjectsV12` or `(localdb)\ProjectsV13`, where V12 is LocalDB 2014 and V13 is LocalDB 2016.
 
-    -   **Attach a database file**: The physical path of the primary .mdf file.
+    -   **Attach a database file**: The physical path of the primary *.mdf* file.
 
     -   **Logical Name**: The name that you want to use with the file.
 
@@ -93,11 +93,11 @@ You can also modify a SQL Server Express connection to use LocalDB by opening th
 
     -   To run the project, select the **F5** key.
 
-    -   To edit the database, open the .mdf file in **Solution Explorer**, and expand the node in **Server Explorer** to work with your database.
+    -   To edit the database, open the *.mdf* file in **Solution Explorer**, and expand the node in **Server Explorer** to work with your database.
 
 ### To make SQL Server Express the default database engine
 
-1.  On the menu bar, select **Tools**, **Options**.
+1.  On the menu bar, select **Tools** > **Options**.
 
 2.  In the **Options** dialog box, expand the **Database Tools** options, and then select **Data Connections**.
 

docs/data-tools/visual-studio-data-tools-for-cpp.md

@@ -27,42 +27,42 @@ To take advantage of custom functionality in SQL Server 2005 and later, use the
 
 2.  If you need a sample SQL database to connect to, download the Northwind database and unzip it to a new location.
 
-3.  Use SQL Server Management Studio to attach the unzipped Northwind.mdf file to localDB. When SQL Server Management Studio starts, connect to (localdb)\MSSQLLocalDB.
+3.  Use SQL Server Management Studio to attach the unzipped *Northwind.mdf* file to localDB. When SQL Server Management Studio starts, connect to (localdb)\MSSQLLocalDB.
 
      ![SSMS connect dialog](../data-tools/media/raddata-ssms-connect-dialog.png)
 
      Then right-click on the localdb node in the left pane, and choose **Attach**.
 
-     ![SSMS Attach database](../data-tools/media/raddata-ssms-attach-database.png)
+     ![SSMS attach database](../data-tools/media/raddata-ssms-attach-database.png)
 
 4.  Download the ODBC Windows SDK Sample, and unzip it to a new location. This sample shows the basic ODBC commands that are used to connect to a database and issue queries and commands. You can learn more about those functions in the [Microsoft Open Database Connectivity (ODBC)](/sql/odbc/microsoft-open-database-connectivity-odbc). When you first load the solution (it's in the C++ folder), Visual Studio will offer to upgrade the solution to the current version of Visual Studio. Click **Yes**.
 
-5.  To use the native client, you need its header file and lib file. These files contain functions and definitions specific to SQL Server, beyond the ODBC functions defined in sql.h. In **Project** > **Properties** > **VC++ Directories**, add the following include directory:
+5.  To use the native client, you need its *header* file and *lib* file. These files contain functions and definitions specific to SQL Server, beyond the ODBC functions defined in sql.h. In **Project** > **Properties** > **VC++ Directories**, add the following include directory:
 
 **%ProgramFiles%\Microsoft SQL Server\110\SDK\Include**
 
 And this library directory:
 
 **%ProgramFiles%\Microsoft SQL Server\110\SDK\Lib**
 
-6.  Add these lines in odbcsql.cpp. The #define prevents irrelevant OLE DB definitions from being compiled.
+6.  Add these lines in *odbcsql.cpp*. The #define prevents irrelevant OLE DB definitions from being compiled.
 
     ```cpp
     #define _SQLNCLI_ODBC_
     #include <sqlncli.h>
     ```
 
-    Note that the sample does not actually use any of the native client functionality, so the preceding steps are not necessary for it to compile and run. But the project is now configured for you to use this functionality. For more information, see [SQL Server Native Client Programming](/sql/relational-databases/native-client/sql-server-native-client).
+    Note that the sample does not actually use any of the native client functionality, so the preceding steps are not necessary for it to compile and run. But the project is now configured for you to use this functionality. For more information, see [SQL Server Native Client programming](/sql/relational-databases/native-client/sql-server-native-client).
 
 7.  Specify which driver to use in the ODBC subsystem. The sample passes the DRIVER connection string attribute in as a command line argument. In **Project** > **Properties** > **Debugging**, add this command argument:
 
     ```cpp
     DRIVER="SQL Server Native Client 11.0"
     ```
 
-8.  Press F5 to build and run the application. You should see a dialog box from the driver that prompts you to enter a database. Enter `(localdb)\MSSQLLocalDB`, and check **Use Trusted Connection**. Press **OK**. You should see a console with messages that indicate a successful connection. You should also see a command prompt where you can type in a SQL statement. The following screen shows an example query and the results:
+8.  Press **F5** to build and run the application. You should see a dialog box from the driver that prompts you to enter a database. Enter `(localdb)\MSSQLLocalDB`, and check **Use Trusted Connection**. Press **OK**. You should see a console with messages that indicate a successful connection. You should also see a command prompt where you can type in a SQL statement. The following screen shows an example query and the results:
 
-     ![ODBC Sample query output](../data-tools/media/raddata-odbc-sample-query-output.png)
+     ![ODBC sample query output](../data-tools/media/raddata-odbc-sample-query-output.png)
 
 ## See also
 

docs/data-tools/work-with-datasets-in-n-tier-applications.md

@@ -24,7 +24,7 @@ ms.workload:
 ---
 # Work with datasets in n-tier applications
 
-*N-tier data applications* are data-centric applications that are separated into multiple logical layers (or *tiers*). In other words, an n-tier data application is an application that is separated into multiple projects, with the data access tier, the business logic tier, and the presentation tier each in its own project. For more information, see [N-Tier Data Applications Overview](../data-tools/n-tier-data-applications-overview.md).
+*N-tier data applications* are data-centric applications that are separated into multiple logical layers (or *tiers*). In other words, an n-tier data application is an application that is separated into multiple projects, with the data access tier, the business logic tier, and the presentation tier each in its own project. For more information, see [N-Tier data applications overview](../data-tools/n-tier-data-applications-overview.md).
 
 Typed datasets have been enhanced so that the TableAdapters and dataset classes can be generated into discrete projects. This provides the ability to quickly separate application layers and generate n-tier data applications.
 
@@ -37,14 +37,14 @@ N-tier support in typed datasets enables iterative development of the applicatio
 
 ## See also
 
-- [N-Tier Data Applications Overview](../data-tools/n-tier-data-applications-overview.md)
-- [Walkthrough: Creating an N-Tier Data Application](../data-tools/walkthrough-creating-an-n-tier-data-application.md)
+- [N-Tier data applications overview](../data-tools/n-tier-data-applications-overview.md)
+- [Walkthrough: Creating an n-tier Data Application](../data-tools/walkthrough-creating-an-n-tier-data-application.md)
 - [Add code to TableAdapters in n-tier applications](../data-tools/add-code-to-tableadapters-in-n-tier-applications.md)
 - [Add code to datasets in n-tier applications](../data-tools/add-code-to-datasets-in-n-tier-applications.md)
 - [Add validation to an n-tier dataset](../data-tools/add-validation-to-an-n-tier-dataset.md)
 - [Separate datasets and TableAdapters into different projects](../data-tools/separate-datasets-and-tableadapters-into-different-projects.md)
 - [Hierarchical update](../data-tools/hierarchical-update.md)
 - [Dataset tools in Visual Studio](../data-tools/dataset-tools-in-visual-studio.md)
 - [Accessing data in Visual Studio](../data-tools/accessing-data-in-visual-studio.md)
-- [Create and Configure TableAdapters](../data-tools/create-and-configure-tableadapters.md)
-- [N-Tier and Remote Applications with LINQ to SQL](/dotnet/framework/data/adonet/sql/linq/n-tier-and-remote-applications-with-linq-to-sql)
+- [Create and configure TableAdapters](../data-tools/create-and-configure-tableadapters.md)
+- [N-Tier and remote applications with LINQ to SQL](/dotnet/framework/data/adonet/sql/linq/n-tier-and-remote-applications-with-linq-to-sql)