typos: xml/System.D*/**/*.* (#2204)

* typo: proccessing -> processing

* typo: thumbrint -> thumbprint

* typo: occuring -> occurring

* typo: Locall -> Local

* typo: deserializad -> deserialized

* typo: declaritive -> declarative

* typo: propert -> property

* typo: implemetation -> implementation

* typo: maintainance -> maintenance

* typo: retuned -> returned

* typo: Adpater -> Adapter

* typo: synchonized -> synchronized

* typo: Enabaled -> Enabled

* typo: Synchornization -> Synchronization

* typo: Resetss -> Resets

* typo: intsance -> instance

* typo: Whenthe -> When the

* typo: betwen -> between

* typo: Securly -> Securely

* typo: aprcified -> specified

* typo: connectiong -> connection

* typo: thead -> thread

* typo: orginal -> original

* typo: Modifed -> Modified

* typo: contraints -> constraints

* typo: Uique -> Unique

* typo: subsytem -> subsystem

* typo: Peformance -> Performance

* typo: langauge -> language

* typo: andcommand -> and command

* typo: printingout -> printing out

* typo: DBnull -> DBNull

* typo: accomodate -> accommodate

* typo: domian -> domain

* typo: Copys -> Copies

* typo: Millenium -> Millennium

* typo: attched -> attached

* typo: s`cale` -> `scale`

* typo: d`ecimal` -> `decimal`

* typo: exceptionif -> exception if

* typo: manipluate -> manipulate

* typo: enumeraton -> enumeration

* typo: tnso -> to

* typo: disjointness -> disjointedness

* typo: byond -> beyond

* typo: structues -> structures

* typo: interger -> integer

* typo: Derefence -> Dereference

* typo: Acccept -> Accept

* typo: specificy -> specify

* typo: byusing -> by using

* typo: forthe -> for the

* typo: structre -> structure

* typo: equl -> equal

* typo: stucture -> structure

* typo: multiplicaion -> multiplication

* typo: Enity -> Entity

* typo: Performa -> Perform a

* typo: equilvalent -> equivalent

* typo: occurence -> occurrence

* typo: realted -> related

* typo: disjointness -> disjointedness

* typo: Sptiaal -> Spatial

* typo: implicitily -> implicitly

* typo: Creidts -> Credits

* typo: deparments -> departments

* typo: destiantion -> destination

* typo: eleted -> Deleted

* Apply suggestions from code review

Co-Authored-By: nschonni <[email protected]>

Author: nschonni

xml/System.Data.Common.CommandTrees.ExpressionBuilder.Spatial/SpatialEdmFunctions.xml

@@ -14,7 +14,7 @@
   </Base>
   <Interfaces />
   <Docs>
-    <summary>Provides an API to construct <see cref="T:System.Data.Common.CommandTrees.DbExpression" />s that invoke spatial realted canonical EDM functions, and, where appropriate, allows that API to be accessed as extension methods on the expression type itself.</summary>
+    <summary>Provides an API to construct <see cref="T:System.Data.Common.CommandTrees.DbExpression" />s that invoke spatial related canonical EDM functions, and, where appropriate, allows that API to be accessed as extension methods on the expression type itself.</summary>
     <remarks>To be added.</remarks>
   </Docs>
   <Members>
@@ -1869,7 +1869,7 @@
         <Parameter Name="spatialValue" Type="System.Data.Common.CommandTrees.DbExpression" RefType="this" />
       </Parameters>
       <Docs>
-        <param name="spatialValue">An expression that specifies the spatial value from which the IsEmptySptiaal value should be retrieved.</param>
+        <param name="spatialValue">An expression that specifies the spatial value from which the IsEmptySpatial value should be retrieved.</param>
         <summary>Creates a <see cref="T:System.Data.Common.CommandTrees.DbFunctionExpression" /> that invokes the canonical 'IsEmptySpatial' function with the specified argument, which must have an Edm.Geography or Edm.Geometry result type. The result type of the expression is Edm.Boolean.</summary>
         <returns>A new DbFunctionExpression that returns a Boolean value indicating whether <paramref name="spatialValue" /> is empty.</returns>
         <remarks>To be added.</remarks>
@@ -2417,7 +2417,7 @@
       </Parameters>
       <Docs>
         <param name="spatialValue1">An expression that specifies the first spatial value.</param>
-        <param name="spatialValue2">An expression that specifies the spatial value that should be compared with <paramref name="spatialValue1" /> for disjointness.</param>
+        <param name="spatialValue2">An expression that specifies the spatial value that should be compared with <paramref name="spatialValue1" /> for disjointedness.</param>
         <summary>Creates a <see cref="T:System.Data.Common.CommandTrees.DbFunctionExpression" /> that invokes the canonical 'SpatialDisjoint' function with the specified arguments, which must each have an Edm.Geography or Edm.Geometry result type. The result type of <paramref name="spatialValue1" /> must match the result type of <paramref name="spatialValue2" />. The result type of the expression is Edm.Boolean.</summary>
         <returns>A new DbFunctionExpression that returns a Boolean value indicating whether <paramref name="spatialValue1" /> and <paramref name="spatialValue2" /> are spatially disjoint.</returns>
         <remarks>To be added.</remarks>

xml/System.Data.Common.CommandTrees.ExpressionBuilder/EdmFunctions.xml

@@ -523,7 +523,7 @@
         <Parameter Name="searchedForString" Type="System.Data.Common.CommandTrees.DbExpression" Index="1" FrameworkAlternate="netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="searchedString">An expression that specifies the string to search for any occurence of **searchedForString**.</param>
+        <param name="searchedString">An expression that specifies the string to search for any occurrence of **searchedForString**.</param>
         <param name="searchedForString">An expression that specifies the string to search for in **searchedString**.</param>
         <summary>Creates a <see cref="T:System.Data.Common.CommandTrees.DbFunctionExpression" /> that invokes the canonical 'Contains' function with the specified arguments, which must each have a string result type. The result type of the expression is Boolean.</summary>
         <returns>A new DbFunctionExpression that returns a Boolean value indicating whether or not **searchedForString** occurs within **searchedString**.</returns>
@@ -1467,7 +1467,7 @@
         <param name="toReplace">An expression that specifies the string that is replaced.</param>
         <param name="replacement">An expression that specifies the replacement string.</param>
         <summary>Creates a <see cref="T:System.Data.Common.CommandTrees.DbFunctionExpression" /> that invokes the canonical 'Replace' function with the specified arguments, which must each have a string result type. The result type of the expression is also string.</summary>
-        <returns>A new DbFunctionExpression than returns a new string based on **stringArgument** where every occurence of **toReplace** is replaced by **replacement**.</returns>
+        <returns>A new DbFunctionExpression than returns a new string based on **stringArgument** where every occurrence of **toReplace** is replaced by **replacement**.</returns>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">**stringArgument** **toReplace** **replacement**</exception>
         <exception cref="T:System.ArgumentException">**stringArgument** **toReplace** **replacement**</exception>

xml/System.Data.Common/DataAdapter.xml

@@ -242,7 +242,7 @@
  During a call to the `Update` method of a `DataAdapter`, the database can send data back to your ADO.NET application as output parameters or as the first returned record of a result set. ADO.NET can retrieve these values and update the corresponding columns in the <xref:System.Data.DataRow> being updated. By default, ADO.NET calls the `AcceptChanges` method of the `DataRow` after the update. However, if you want to merge the updated row back into another <xref:System.Data.DataTable>, you may want to preserver the original value of a primary key column. For example, a primary key column corresponding to an automatically incrementing column in the database, such as an identity column, can contain new values that are assigned by the database that do not match the original values assigned in the `DataRow`. By default, `AcceptChanges` is called implicitly after an update, and the original values in the row, which may have been <xref:System.Data.DataColumn.AutoIncrement%2A> values assigned by ADO.NET, are lost. You can preserve the original values in the `DataRow` by preventing `ADO.NET` from calling `AcceptChanges` after it performs an update on a row, by setting the <xref:System.Data.Common.DataAdapter.AcceptChangesDuringUpdate%2A> property to `false`, which preserves the original values.  
   
 > [!NOTE]
->  Setting the `AcceptChangesDuringUpdate` property to `false` applies to all data modifications, not only inserts. If you want to edit or delete rows in the same update, and if you want to suppress the call to `AcceptChanges` only for inserts, then instead of setting `AccceptChangesDuringUpdate` to `false`, use an event handler for the `RowUpdated` event of the `DataAdapter`. In the event handler you can check the <xref:System.Data.Common.RowUpdatedEventArgs.StatementType%2A> to determine if the data modification is an insert, and if `true`, set the <xref:System.Data.Common.RowUpdatedEventArgs.Status%2A> property of the <xref:System.Data.Common.RowUpdatedEventArgs> to <xref:System.Data.UpdateStatus.SkipCurrentRow>. For more information and an example, see [Retrieving Identity or Autonumber Values](~/docs/framework/data/adonet/retrieving-identity-or-autonumber-values.md).  
+>  Setting the `AcceptChangesDuringUpdate` property to `false` applies to all data modifications, not only inserts. If you want to edit or delete rows in the same update, and if you want to suppress the call to `AcceptChanges` only for inserts, then instead of setting `AcceptChangesDuringUpdate` to `false`, use an event handler for the `RowUpdated` event of the `DataAdapter`. In the event handler, you can check the <xref:System.Data.Common.RowUpdatedEventArgs.StatementType%2A> to determine if the data modification is an insert, and if `true`, set the <xref:System.Data.Common.RowUpdatedEventArgs.Status%2A> property of the <xref:System.Data.Common.RowUpdatedEventArgs> to <xref:System.Data.UpdateStatus.SkipCurrentRow>. For more information and an example, see [Retrieving Identity or Autonumber Values](~/docs/framework/data/adonet/retrieving-identity-or-autonumber-values.md).  
   
    
   
@@ -1573,4 +1573,4 @@ If a unique clustered index is defined on a column or columns in a SQL Server ta
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>

xml/System.Data.Common/DbDataReader.xml

@@ -636,8 +636,8 @@
 ## Remarks  
   
 ```  
-private static void GetDataTypes(String connectiongString) {       
-   using (SqlConnection conn = new SqlConnection(connectiongString)) {  
+private static void GetDataTypes(String connectionString) {       
+   using (SqlConnection conn = new SqlConnection(connectionString)) {  
       String queryString = "Select [CourseID],[Title],[Credits] from [MySchool].[dbo].[Course]";  
       using (DbCommand command = new SqlCommand(queryString, conn)) {  
          conn.Open();               
@@ -1334,8 +1334,8 @@ private static void GetDataTypes(String connectiongString) {
 ## Remarks  
   
 ```  
-private static void GetCredits(String connectiongString) {  
-   using (SqlConnection conn = new SqlConnection(connectiongString)) {  
+private static void GetCredits(String connectionString) {  
+   using (SqlConnection conn = new SqlConnection(connectionString)) {  
       String queryString = "Select [CourseID],[Title],[Credits] from [MySchool].[dbo].[Course]";   
       using (DbCommand command = new SqlCommand(queryString, conn)) {  
          conn.Open();   

xml/System.Data.Common/DbProviderServices.xml

@@ -130,7 +130,7 @@
       <Docs>
         <param name="providerManifest">The manifest.</param>
         <param name="commandTree">The command tree.</param>
-        <summary>Creates command definition from specified manifest andcommand tree.</summary>
+        <summary>Creates command definition from specified manifest and command tree.</summary>
         <returns>The created command definition.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -193,7 +193,7 @@
       <Docs>
         <param name="providerManifestToken">The provider manifest token identifying the target version.</param>
         <param name="storeItemCollection">The structure of the database.</param>
-        <summary>Generates a data definition langauge (DDL script that creates schema objects (tables, primary keys, foreign keys) based on the contents of the StoreItemCollection parameter and targeted for the version of the database corresponding to the provider manifest token.</summary>
+        <summary>Generates a data definition language (DDL script that creates schema objects (tables, primary keys, foreign keys) based on the contents of the StoreItemCollection parameter and targeted for the version of the database corresponding to the provider manifest token.</summary>
         <returns>A DDL script that creates schema objects based on the contents of the StoreItemCollection parameter and targeted for the version of the database corresponding to the provider manifest token.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -307,7 +307,7 @@
       <Docs>
         <param name="providerManifestToken">The provider manifest token identifying the target version.</param>
         <param name="storeItemCollection">The structure of the database.</param>
-        <summary>Generates a data definition langauge (DDL script that creates schema objects (tables, primary keys, foreign keys) based on the contents of the StoreItemCollection parameter and targeted for the version of the database corresponding to the provider manifest token.</summary>
+        <summary>Generates a data definition language (DDL script that creates schema objects (tables, primary keys, foreign keys) based on the contents of the StoreItemCollection parameter and targeted for the version of the database corresponding to the provider manifest token.</summary>
         <returns>A DDL script that creates schema objects based on the contents of the StoreItemCollection parameter and targeted for the version of the database corresponding to the provider manifest token.</returns>
         <remarks>To be added.</remarks>
       </Docs>

xml/System.Data.Linq/Table`1.xml

@@ -1046,7 +1046,7 @@ db.SubmitChanges()
         <Parameter Name="asModified" Type="System.Boolean" />
       </Parameters>
       <Docs>
-        <param name="entities">The collection of entities to be attched.</param>
+        <param name="entities">The collection of entities to be attached.</param>
         <param name="asModified">
           <see langword="true" /> to attach the entities as modified; <see langword="false" /> to attach the entities as unmodified.</param>
         <summary>Attaches all entities of a collection to the <see cref="T:System.Data.Linq.DataContext" /> in either a modified or unmodified state.</summary>

xml/System.Data.Metadata.Edm/ObjectItemCollection.xml

@@ -20,7 +20,7 @@
     </Attribute>
   </Attributes>
   <Docs>
-    <summary>Class for representing a collection of items for the object layer. Most of the implemetation for actual maintainance of the collection is done by ItemCollection.</summary>
+    <summary>Class for representing a collection of items for the object layer. Most of the implementation for actual maintenance of the collection is done by ItemCollection.</summary>
     <remarks>To be added.</remarks>
   </Docs>
   <Members>

xml/System.Data.Objects.DataClasses/EntityReference`1.xml

@@ -174,7 +174,7 @@
   
  When loaded, the related object is accessed from the <xref:System.Data.Objects.DataClasses.EntityReference%601.Value%2A> property.  
   
- To explicitly load related objects, you must call the `Load` method on the related end retuned by the navigation property. For a one-to-many relationship, call the <xref:System.Data.Objects.DataClasses.EntityCollection%601.Load%2A> method on <xref:System.Data.Objects.DataClasses.EntityCollection%601>, and for a one-to-one relationship, call the <xref:System.Data.Objects.DataClasses.EntityReference%601.Load%2A> on <xref:System.Data.Objects.DataClasses.EntityReference%601>. This loads the related object data into the object context. When a query returns results, you can enumerate through the collection of objects using a `foreach` loop (`For Each...Next` in Visual Basic) and conditionally call the `Load` method on <xref:System.Data.Objects.DataClasses.EntityReference%601> and <xref:System.Data.Objects.DataClasses.EntityCollection%601> properties for each entity in the results.  
+ To explicitly load related objects, you must call the `Load` method on the related end returned by the navigation property. For a one-to-many relationship, call the <xref:System.Data.Objects.DataClasses.EntityCollection%601.Load%2A> method on <xref:System.Data.Objects.DataClasses.EntityCollection%601>, and for a one-to-one relationship, call the <xref:System.Data.Objects.DataClasses.EntityReference%601.Load%2A> on <xref:System.Data.Objects.DataClasses.EntityReference%601>. This loads the related object data into the object context. When a query returns results, you can enumerate through the collection of objects using a `foreach` loop (`For Each...Next` in Visual Basic) and conditionally call the `Load` method on <xref:System.Data.Objects.DataClasses.EntityReference%601> and <xref:System.Data.Objects.DataClasses.EntityCollection%601> properties for each entity in the results.  
   
  The <xref:System.Data.Objects.DataClasses.EntityReference%601.Load%2A> method loads related objects from the data source whether or not <xref:System.Data.Objects.DataClasses.RelatedEnd.IsLoaded%2A> is `true`.  
   

xml/System.Data.Objects/ObjectContext.xml

@@ -1474,7 +1474,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.Objects.ObjectContext.ExecuteFunction%2A> method is a helper method that is used to execute stored procedures or functions that are defined in the data source and expressed in the conceptual model. The Entity Data Model tools generate a method for each  in the conceptual model. These methods call a strongly-typed `ExecuteFunction` to return a typed <xref:System.Data.Objects.ObjectResult%601>. For more information, see [Application Code using Stored Procedures (Enity Framework)](https://msdn.microsoft.com/library/d13dd33f-fcf9-4e86-bd00-74bc31521536).  
+ The <xref:System.Data.Objects.ObjectContext.ExecuteFunction%2A> method is a helper method that is used to execute stored procedures or functions that are defined in the data source and expressed in the conceptual model. The Entity Data Model tools generate a method for each [FunctionImport Element](/ef/ef6/modeling/designer/advanced/edmx/csdl-spec#functionimport-element-csdl) in the conceptual model. These methods call a strongly-typed `ExecuteFunction` to return a typed <xref:System.Data.Objects.ObjectResult%601>. For more information, see [Application Code using Stored Procedures (Entity Framework)](https://docs.microsoft.com/previous-versions/cc716795(v=vs.90)).  
   
  All parameters for the function are required in the parameters array and all types are checked against the metadata for the import function, including the type of the function itself. `null` values are permitted for CLR value types. Parameter validation is performed by the provider.  
   
@@ -1535,7 +1535,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.Objects.ObjectContext.ExecuteFunction%2A> method is a helper method that is used to execute stored procedures or functions that are defined in the data source and expressed in conceptual model. The Entity Data Model tools generate a method for each  in the conceptual model. These methods call a strongly-typed `ExecuteFunction` to return a typed <xref:System.Data.Objects.ObjectResult%601>. For more information, see [Application Code using Stored Procedures (Enity Framework)](https://msdn.microsoft.com/library/d13dd33f-fcf9-4e86-bd00-74bc31521536).  
+ The <xref:System.Data.Objects.ObjectContext.ExecuteFunction%2A> method is a helper method that is used to execute stored procedures or functions that are defined in the data source and expressed in conceptual model. The Entity Data Model tools generate a method for each [FunctionImport Element](/ef/ef6/modeling/designer/advanced/edmx/csdl-spec#functionimport-element-csdl) in the conceptual model. These methods call a strongly-typed `ExecuteFunction` to return a typed <xref:System.Data.Objects.ObjectResult%601>. For more information, see [Application Code using Stored Procedures (Entity Framework)](https://docs.microsoft.com/previous-versions/cc716795(v=vs.90)).  
   
  All parameters for the function are required in the parameters array and all types are checked against the metadata for the import function, including the type of the function itself. `null` values are permitted for CLR value types. Parameter validation is performed by the provider.  
   
@@ -2633,4 +2633,4 @@
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>