Address comments

Author: Davoud Eshtehari

docs/connect/ado-net/common-schema-collections.md

@@ -106,6 +106,6 @@ This schema collection exposes information about the words that are reserved by
 
 ## See also
 
-- [Retrieving Database Schema Information](retrieving-database-schema-information.md)
-- [GetSchema and Schema Collections](getschema-and-schema-collections.md)
+- [Retrieving database schema information](retrieving-database-schema-information.md)
+- [GetSchema and schema collections](getschema-and-schema-collections.md)
 - [Microsoft ADO.NET for SQL Server](microsoft-ado-net-sql-server.md)

docs/connect/ado-net/connecting-to-data-source.md

@@ -35,5 +35,5 @@ Describes how to use an **InfoMessage** event to retrieve informational messages
 - [Connection pooling](connection-pooling.md)
 - [Commands and parameters](commands-parameters.md)
 - [DataAdapters and DataReaders](dataadapters-datareaders.md)
-- [Transactions and Concurrency](transactions-and-concurrency.md)
+- [Transactions and concurrency](transactions-and-concurrency.md)
 - [Microsoft ADO.NET for SQL Server](microsoft-ado-net-sql-server.md)

docs/connect/ado-net/connection-pooling.md

@@ -26,5 +26,5 @@ Provides an overview of connection pooling and describes how connection pooling
 
 ## See also
 
-- [Retrieving and Modifying Data in ADO.NET](retrieving-modifying-data.md)
+- [Retrieving and modifying data in ADO.NET](retrieving-modifying-data.md)
 - [Microsoft ADO.NET for SQL Server](microsoft-ado-net-sql-server.md)

docs/connect/ado-net/connection-strings-and-configuration-files.md

@@ -76,7 +76,7 @@ The .NET Framework 2.0 introduced new classes in the <xref:System.Configuration>
 > [!NOTE]
 > The **machine.config** file also contains a **connectionStrings** section, which contains connection strings used by Visual Studio. When retrieving connection strings by provider name from the **app.config** file in a Windows application, the connection strings in **machine.config** get loaded first, and then the entries from **app.config**. Adding **clear** immediately after the **connectionStrings** element removes all inherited references from the data structure in memory, so that only the connection strings defined in the local **app.config** file are considered.
 
-### Work with the configuration classes
+### Work with the configuration files
 
 Starting with the .NET Framework 2.0, <xref:System.Configuration.ConfigurationManager> is used when working with configuration files on the local computer, replacing the deprecated <xref:System.Configuration.ConfigurationSettings>. <xref:System.Web.Configuration.WebConfigurationManager> is used to work with ASP.NET configuration files. It is designed to work with configuration files on a Web server, and allows programmatic access to configuration file sections such as **system.web**.
 
@@ -91,7 +91,7 @@ You can use the <xref:System.Configuration.ConnectionStringSettingsCollection> t
 |<xref:System.Configuration.ConnectionStringSettings.ProviderName%2A>|The fully qualified provider name. Maps to the **providerName** attribute.|  
 |<xref:System.Configuration.ConnectionStringSettings.ConnectionString%2A>|The connection string. Maps to the **connectionString** attribute.|  
 
-### Example: listing all connection strings
+### Example: Listing all connection strings
 
 This example iterates through the <xref:System.Configuration.ConnectionStringSettingsCollection> and displays the <xref:System.Configuration.ConnectionStringSettings.Name%2A?displayProperty=nameWithType>, <xref:System.Configuration.ConnectionStringSettings.ProviderName%2A?displayProperty=nameWithType>, and <xref:System.Configuration.ConnectionStringSettings.ConnectionString%2A?displayProperty=nameWithType> properties in the console window.
 
@@ -100,13 +100,13 @@ This example iterates through the <xref:System.Configuration.ConnectionStringSet
 
 [!code-csharp[DataWorks ConnectionStringSettings.RetrieveFromConfig#1](~/../SqlClient/doc/samples/ConnectionStringSettings_RetrieveFromConfig.cs#1)]
 
-### Example: retrieving a connection string by name
+### Example: Retrieving a connection string by name
 
 This example demonstrates how to retrieve a connection string from a configuration file by specifying its name. The code creates a <xref:System.Configuration.ConnectionStringSettings> object, matching the supplied input parameter to the <xref:System.Configuration.ConfigurationManager.ConnectionStrings%2A> name. If no matching name is found, the function returns `null` (`Nothing` in Visual Basic).
 
 [!code-csharp[DataWorks ConnectionStringSettings.RetrieveFromConfigByName#1](~/../SqlClient/doc/samples/ConnectionStringSettings_RetrieveFromConfigByName.cs#1)]
 
-### Example: retrieving a connection string by provider name
+### Example: Retrieving a connection string by provider name
 
 This example demonstrates how to retrieve a connection string by specifying the provider name in the format *Microsoft.Data.SqlClient*. The code iterates through the <xref:System.Configuration.ConnectionStringSettingsCollection> and returns the connection string for the first <xref:System.Configuration.ConnectionStringSettings.ProviderName%2A> found. If the provider name is not found, the function returns `null` (`Nothing` in Visual Basic).
 
@@ -185,9 +185,9 @@ For more information about securing ASP.NET applications, see [Securing ASP.NET
 
 ## See also
 
-- [Connection String Builders](connection-string-builders.md)
-- [Protecting Connection Information](protecting-connection-information.md)
-- [Using the Configuration Classes](/previous-versions/visualstudio/visual-studio-2008/ms228063(v=vs.90))
-- [Configuring Apps](/dotnet/framework/configure-apps/index)
-- [ASP.NET Web Site Administration](/previous-versions/aspnet/6hy1xzbw(v=vs.100))
+- [Connection string builders](connection-string-builders.md)
+- [Protecting connection information](protecting-connection-information.md)
+- [Using the configuration classes](/previous-versions/visualstudio/visual-studio-2008/ms228063(v=vs.90))
+- [Configuring apps](/dotnet/framework/configure-apps/index)
+- [ASP.NET web site administration](/previous-versions/aspnet/6hy1xzbw(v=vs.100))
 - [Microsoft ADO.NET for SQL Server](microsoft-ado-net-sql-server.md)

docs/connect/ado-net/connection-strings.md

@@ -63,7 +63,7 @@ All connection strings share the same basic syntax described above. The set of r
 
 Typing mistakes can cause errors. For example, `Integrated Security=true` is valid, but `IntegratedSecurity=true` causes an error.
 
-Connection strings constructed manually at run time from unvalidated user input are vulnerable to string-injection attacks and jeopardize security at the data source. To address these problems, the [connection string builder](connection-string-builders.md) has created. This connection string builder exposes parameters as strongly typed properties, and make it possible to validate the connection string before it's sent to the data source.
+Connection strings constructed manually at run time from invalidated user input are vulnerable to string-injection attacks and jeopardize security at the data source. To address these problems, the <xref:Microsoft.Data.SqlClient.SqlConnectionStringBuilder> class has been created. This [connection string builder](connection-string-builders.md) class exposes parameters as strongly typed properties, and makes it possible to validate the connection string before it's sent to the data source.
 
 ## In this section
 
@@ -79,6 +79,6 @@ Describes how to configure provider-specific connection strings for `SqlClient`.
 [Protecting Connection Information](protecting-connection-information.md)\
 Demonstrates techniques for protecting information used to connect to a data source.
 
-## See alos
+## See also
 
 - [Microsoft ADO.NET for SQL Server](microsoft-ado-net-sql-server.md)

docs/connect/ado-net/dbproviderfactories.md

@@ -28,5 +28,5 @@ Demonstrates how to obtain a `SqlClientFactory` from the `DbProviderFactories` c
 
 ## See also
 
-- [Retrieving and Modifying Data in ADO.NET](retrieving-modifying-data.md)
+- [Retrieving and modifying data in ADO.NET](retrieving-modifying-data.md)
 - [Microsoft ADO.NET for SQL Server](microsoft-ado-net-sql-server.md)

docs/connect/ado-net/obtain-sqlclientfactory.md

@@ -17,7 +17,9 @@ ms.reviewer: v-chmalh
 
 [!INCLUDE[Driver_ADONET_Download](../../includes/driver_adonet_download.md)]
 
-The process of obtaining a <xref:System.Data.Common.DbProviderFactory> involves passing information about a data provider to the <xref:System.Data.Common.DbProviderFactories> class. Based on this information, the <xref:System.Data.Common.DbProviderFactories.GetFactory%2A> method creates a strongly typed provider factory. For example, to create a <xref:Microsoft.Data.SqlClient.SqlClientFactory>, you can pass `GetFactory` a string with the provider name specified as "**Microsoft.Data.SqlClient**". The other overload of `GetFactory` takes a <xref:System.Data.DataRow>. Once you create the provider factory, you can then use its methods to create additional objects. Some of the methods of a `SqlClientFactory` include <xref:Microsoft.Data.SqlClient.SqlClientFactory.CreateConnection%2A>, <xref:Microsoft.Data.SqlClient.SqlClientFactory.CreateCommand%2A>, and <xref:Microsoft.Data.SqlClient.SqlClientFactory.CreateDataAdapter%2A>.
+The process of obtaining a <xref:System.Data.Common.DbProviderFactory> involves passing information about a data provider to the <xref:System.Data.Common.DbProviderFactories> class. Based on this information, the <xref:System.Data.Common.DbProviderFactories.GetFactory%2A> method creates a strongly typed provider factory. For example, to create a <xref:Microsoft.Data.SqlClient.SqlClientFactory>, you can pass `GetFactory` a string with the provider name specified as "**Microsoft.Data.SqlClient**".
+
+The other overload of `GetFactory` takes a <xref:System.Data.DataRow>. Once you create the provider factory, you can then use its methods to create additional objects. Some of the methods of a `SqlClientFactory` include <xref:Microsoft.Data.SqlClient.SqlClientFactory.CreateConnection%2A>, <xref:Microsoft.Data.SqlClient.SqlClientFactory.CreateCommand%2A>, and <xref:Microsoft.Data.SqlClient.SqlClientFactory.CreateDataAdapter%2A>.
 
 ## Register SqlClientFactory
 
@@ -37,7 +39,7 @@ To retrieve the <xref:Microsoft.Data.SqlClient.SqlClientFactory> object by the <
 The **invariant** attribute identifies the underlying data provider. This three-part naming syntax is also used when creating a new factory and for identifying the provider in an application configuration file so that the provider name, along with its associated connection string, can be retrieved at run time.  
 
 > [!NOTE]  
-> Since in .NET core, there is no GAC or global configuration anymore, the <xref:Microsoft.Data.SqlClient.SqlClientFactory> object should be register by <xref:System.Data.Common.DbProviderFactories.RegisterFactory%2A> method in your project first.
+> In .NET core, since there is no GAC or global configuration support, the <xref:Microsoft.Data.SqlClient.SqlClientFactory> object should be registered by calling <xref:System.Data.Common.DbProviderFactories.RegisterFactory%2A> method in the project.
 
 The following sample shows how to use the <xref:Microsoft.Data.SqlClient.SqlClientFactory> in a .NET core application.
 
@@ -47,5 +49,5 @@ The following sample shows how to use the <xref:Microsoft.Data.SqlClient.SqlClie
 
 - [DbProviderFactories](dbproviderfactories.md)
 - [Connection strings](connection-strings.md)
-- [Using the Configuration Classes](/previous-versions/aspnet/ms228063(v=vs.100))
+- [Using the configuration classes](/previous-versions/aspnet/ms228063(v=vs.100))
 - [Microsoft ADO.NET for SQL Server](microsoft-ado-net-sql-server.md)

docs/connect/ado-net/performance-counters.md

@@ -75,6 +75,6 @@ The following console application shows how to retrieve performance counter valu
 ## See also
 
 - [Connecting to a data source](connecting-to-data-source.md)
-- [Runtime Profiling](/dotnet/framework/debug-trace-profile/runtime-profiling.md)
-- [Introduction to Monitoring Performance Thresholds](/previous-versions/visualstudio/visual-studio-2008/bd20x32d(v=vs.90))
+- [Runtime profiling](/dotnet/framework/debug-trace-profile/runtime-profiling.md)
+- [Introduction to monitoring performance thresholds](/previous-versions/visualstudio/visual-studio-2008/bd20x32d(v=vs.90))
 - [Microsoft ADO.NET for SQL Server](microsoft-ado-net-sql-server.md)

docs/connect/ado-net/populate-dataset-from-dataadapter.md

@@ -52,7 +52,7 @@ Any number of `DataAdapter` objects can be used with a `DataSet`. Each `DataAdap
 
 ### Example  
 
-The following code example populates a list of customers from the `Northwind` database on Microsoft SQL Server, and a list of orders from the `Northwind` database stored in Microsoft Access 2000. The filled tables are related with a `DataRelation`, and the list of customers is then displayed with the orders for that customer.
+The following code example populates a list of customers from the `Northwind` database on Microsoft SQL Server, and a list of orders from the `Northwind` database stored in Microsoft Access. The filled tables are related with a `DataRelation`, and the list of customers is then displayed with the orders for that customer.
 
 [!code-csharp[SqlDataAdapter_FillDataSet#2](~/../sqlclient/doc/samples/SqlDataAdapter_FillDataSet.cs#2)]
 

docs/connect/ado-net/protecting-connection-information.md

@@ -39,7 +39,7 @@ The fixed identity account should be a low-privilege account that has been grant
 
 A connection string injection attack can occur when dynamic string concatenation is used to build connection strings based on user input. If the user input is not validated and malicious text or characters not escaped, an attacker can potentially access sensitive data or other resources on the server. To address this problem, Microsoft SqlClient Data Provider for SQL Server introduced new connection string builder class to validate connection string syntax and ensure that additional parameters are not introduced. For more information, see [Connection String Builders](connection-string-builders.md).
 
-## Use Persist Security Info=false
+## Use "Persist Security Info=false"
 
 The default value for `Persist Security Info` is false; we recommend using this default in all connection strings. Setting `Persist Security Info` to `true` or `yes` allows security-sensitive information, including the user ID and password, to be obtained from a connection after it has been opened. When `Persist Security Info` is set to `false` or `no`, security information is discarded after it is used to open the connection, ensuring that an untrusted source does not have access to security-sensitive information.