fix header name (#4095)

Author: mairaw

xml/System.Data.SqlClient/SqlConnection.xml

@@ -2660,7 +2660,7 @@ class Program {
         <remarks>
           <format type="text/markdown"><![CDATA[
 
-## Example
+## Examples
 
 ```csharp
 Dictionary<string, SqlColumnEncryptionKeyStoreProvider> customKeyStoreProviders = new Dictionary<string, SqlColumnEncryptionKeyStoreProvider>();

xml/System.Diagnostics/OverflowAction.xml

@@ -36,7 +36,7 @@
   
  Use the <xref:System.Diagnostics.EventLog.ModifyOverflowPolicy%2A> method to set the overflow behavior for an <xref:System.Diagnostics.EventLog>. Check the current configured behavior of an <xref:System.Diagnostics.EventLog> through its <xref:System.Diagnostics.EventLog.OverflowAction%2A> property.  
 
-## Example
+## Examples
 
 The following example enumerates the event logs defined on the local computer and displays configuration details for each event log.
   

xml/System.IO/Path.xml

@@ -1359,7 +1359,7 @@ If `path` is an empty path, the method returns `basePath`. If `path` is a fully
 
 Use this method to return a deterministic path based on a specified volume and rooted directory when you're using relative paths. Using a predefined `basePath` rather than one based on the current drive directory guards against unwanted file paths caused by unexpected changes in the current drive and directory. 
 
-## Example
+## Examples
 
 The following example defines a variable, `basePath`, to represent an application's current directory. It then passes it to the `GetFullPath` method to get a fully qualified path to the application's data directory.
 
@@ -2479,7 +2479,7 @@ Unlike the <xref:System.IO.Path.Combine%2A> method, the <xref:System.IO.Path.Joi
 
 Not all invalid characters for directory and file names are interpreted as unacceptable by the `Join` method, because you can use these characters for search wildcard characters. For example, while `Path.Join("c:\\", "*.txt")` might be invalid when creating a file, it is valid as a search string. The `Join` method therefore successfully interprets it. 
 
-## Example
+## Examples
 
 The following example illustrates the difference in the paths returned by the <xref:System.IO.Path.Join(System.ReadOnlySpan%7BSystem.Char%7D,System.ReadOnlySpan%7BSystem.Char%7D)?displayProperty=nameWithType> and <xref:System.IO.Path.Combine(System.String,System.String)?displayProperty=nameWithType> methods. When the first string is an fully qualified path that includes a drive and root directory and the second is a relative path from the first path, the two methods produce identical results. In the second and third calls to the `ShowPathInformation` method, the strings returned by the two methods diverge. In the second method call, the first string argument is a drive, while the second is a rooted directory. The `Join` method concatenates the two strings and preserves duplicate path separators. The `Combine` method abandons the drive and returns a rooted directory on the current drive. If the application's current drive is C:\ and the string is used to access a file or files in the directory, it would access C: instead of D:. Finally, because both arguments in the third call to `ShowPathInformation` are rooted, the `Join` method simply appends them to create a nonsensical file path, while the `Combine` method discards the first string and returns the second. Using this string for file access could give the application unintended access to sensitive files.  
 
@@ -2603,7 +2603,7 @@ Unlike the <xref:System.IO.Path.Combine%2A> method, the <xref:System.IO.Path.Joi
   
 Not all invalid characters for directory and file names are interpreted as unacceptable by the `Join` method, because you can use these characters for search wildcard characters. For example, while `Path.Join("c:\\", "temp", "*.txt")` might be invalid when creating a file, it is valid as a search string. The `Join` method therefore successfully interprets it.
 
-## Example
+## Examples
 
 The following example illustrates the difference in the paths returned by the <xref:System.IO.Path.Join(System.ReadOnlySpan%7BSystem.Char%7D,System.ReadOnlySpan%7BSystem.Char%7D,System.ReadOnlySpan%7BSystem.Char%7D)?displayProperty=nameWithType> and <xref:System.IO.Path.Combine(System.String,System.String,System.String)?displayProperty=nameWithType> methods. When the first string is a fully qualified path that includes a drive and root directory and the second is a relative path from the first path, the two methods produce identical results. In the second and third calls to the `ShowPathInformation` method, the strings returned by the two methods diverge. In the second method call, the first string argument is a drive, while the second is a rooted directory. The `Join` method concatenates the two strings and preserves duplicate path separators. A call to the <xref:System.IO.Path.GetFullPath%2A> method would eliminate the duplication. The `Combine` method abandons the drive and returns a rooted directory on the current drive. If the application's current drive is C:\ and the string is used to access a file or files in the directory, it would access C: instead of D:. Finally, because the final argument in the third call to `ShowPathInformation` are rooted, the `Join` method simply appends it to the first two arguments to create a nonsensical file path, while the `Combine` method discards the first two strings and returns the third. Using this string for file access could give the application unintended access to sensitive files.
 

xml/System.Net.Http/HttpClient.xml

@@ -2572,7 +2572,7 @@ The `DefaultRequestVersion` property can be changed as long as the <xref:System.
   
  The same timeout will apply for all requests using this <xref:System.Net.Http.HttpClient> instance.  You may also set different timeouts for individual requests using a <xref:System.Threading.CancellationTokenSource> on a task. Note that only the shorter of the two timeouts will apply.  
   
- ## Example
+ ## Examples
  
  The following example sets the `Timeout` property.
   

xml/System.Web.UI.WebControls/EntityDataSource.xml

@@ -305,7 +305,7 @@ AutoGenerateOrderByClause="True">
 ## Remarks
  To filter query results by equating an entity type property to an expression, you can use the <xref:System.Web.UI.WebControls.EntityDataSource.AutoGenerateWhereClause%2A> property. When the <xref:System.Web.UI.WebControls.EntityDataSource.AutoGenerateWhereClause%2A> property of the <xref:System.Web.UI.WebControls.EntityDataSource> control is set to `true`, the control automatically generates a `WHERE` clause from the parameters in the <xref:System.Web.UI.WebControls.ParameterCollection> of the <xref:System.Web.UI.WebControls.EntityDataSource.WhereParameters%2A> property. The <xref:System.Web.UI.WebControls.Parameter.Name%2A> property of each parameter has to match an entity type property name that is included in the query results. If you set the <xref:System.Web.UI.WebControls.EntityDataSource.AutoGenerateWhereClause%2A> property to `true`, you should not explicitly assign a `WHERE` clause to the <xref:System.Web.UI.WebControls.EntityDataSource.Where%2A> property.
 
-## Example
+## Examples
  In the following example the <xref:System.Web.UI.WebControls.EntityDataSource.AutoGenerateWhereClause%2A> property is set to `true`. Therefore, the <xref:System.Web.UI.WebControls.Parameter.Name%2A> of the property has to match an entity type property name that is included in the query results. The query selects the SalesOrderID and TotalDue properties of the SalesOrderHeader entity type. The automatically generated `WHERE` clause will filter the query results by comparing the TotalDue value to a value selected in the TotalDueList list box control.
 
 ```
@@ -322,7 +322,7 @@ AutoGenerateOrderByClause="True">
 </asp:EntityDataSource>
 ```
 
-## Example
+## Examples
  By default, the <xref:System.Web.UI.WebControls.EntityDataSource.AutoGenerateWhereClause%2A> property is set to `false`. This means that we have to supply the `WHERE` clause. In the following example, the `WHERE` clause is `Where="it.TotalDue < @totalDueParam"` and totalDueParam is the parameter name.
 
 ```

xml/System/DateTime.xml

@@ -5185,7 +5185,7 @@ This overload attempts to parse `s` by using the formatting conventions of the c
 
 This overload attempts to parse `s` by using <xref:System.Globalization.DateTimeStyles.AllowWhiteSpaces?displayProperty=nameWithType> style.
 
-## Example
+## Examples
 
 The following example parses the string representation of several date and time values by:
 
@@ -5269,7 +5269,7 @@ If `s` contains time zone information, this method returns a <xref:System.DateTi
 
 This overload attempts to parse `s` by using the <xref:System.Globalization.DateTimeStyles.AllowWhiteSpaces?displayProperty=nameWithType> style.
 
-## Example
+## Examples
 
 The following example parses an array of date strings by using the conventions of the en-US, fr-FR, and de-DE cultures. It demonstrates that the string representations of a single date can be interpreted differently across different cultures.  
 
@@ -5395,7 +5395,7 @@ This method overload converts the date and time in `s` and sets the <xref:System
 | `s` contains time zone information, and `styles` includes the <xref:System.Globalization.DateTimeStyles.AdjustToUniversal?displayProperty=nameWithType> flag. | To Coordinated Universal Time (UTC) | <xref:System.DateTimeKind.Utc?displayProperty=nameWithType> |
 | `s` contains the Z or GMT time zone designator, and `styles` includes the <xref:System.Globalization.DateTimeStyles.RoundtripKind?displayProperty=nameWithType>. | None. | <xref:System.DateTimeKind.Utc?displayProperty=nameWithType> |
 
-## Example
+## Examples
 
 The following example demonstrates the <xref:System.DateTime.Parse%28System.String%2CSystem.IFormatProvider%2CSystem.Globalization.DateTimeStyles%29> method and displays the value of the <xref:System.DateTime.Kind%2A> property of the resulting <xref:System.DateTime> values.