Update HttpHeaders.xml

Author: MihaZupan

xml/System.Net.Http.Headers/HttpHeaders.xml

@@ -127,6 +127,8 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
+ Header names are enforced to be valid HTTP tokens, where a token is defined as any set of ASCII letters, digits, or symbols from the ``"!#$%&'*+-.^_`|~"`` set, matching [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-collected-abnf)'s definition. Non-ASCII characters are not allowed in a header name.  
+
  The header `values` will be parsed and validated.  
   
  If the specified header does not exist, the <xref:System.Net.Http.Headers.HttpHeaders.Add%2A> method inserts a new header into the list of header name/value pairs.  
@@ -138,7 +140,7 @@
         <exception cref="T:System.ArgumentException">The name cannot be null or empty.</exception>
         <exception cref="T:System.ArgumentNullException">The values cannot be null or empty.</exception>
         <exception cref="T:System.InvalidOperationException">Misused header name. Make sure request headers are used with HttpRequestMessage, response headers with HttpResponseMessage, and content headers with HttpContent objects.</exception>
-        <exception cref="T:System.FormatException">Header names are enforced to be valid HTTP tokens, where a token is defined as any set of ASCII letters, digits, or symbols from the ``"!#$%&'*+-.^_`|~"`` set, matching [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-collected-abnf)'s definition. Non-ASCII characters are not allowed in a header name.
+        <exception cref="T:System.FormatException">The header name format is invalid.
 
 -or-
 
@@ -187,7 +189,9 @@ The header value format is invalid for this header name, or the header does not
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The header `value` will be parsed and validated.  
+ Header names are enforced to be valid HTTP tokens, where a token is defined as any set of ASCII letters, digits, or symbols from the ``"!#$%&'*+-.^_`|~"`` set, matching [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-collected-abnf)'s definition. Non-ASCII characters are not allowed in a header name.  
+
+ The header `values` will be parsed and validated.  
   
  If the specified header does not exist, the <xref:System.Net.Http.Headers.HttpHeaders.Add%2A> method inserts a new header into the list of header name/value pairs.  
   
@@ -197,7 +201,7 @@ The header value format is invalid for this header name, or the header does not
         </remarks>
         <exception cref="T:System.ArgumentException">The name cannot be null or empty.</exception>
         <exception cref="T:System.InvalidOperationException">Misused header name. Make sure request headers are used with HttpRequestMessage, response headers with HttpResponseMessage, and content headers with HttpContent objects.</exception>
-        <exception cref="T:System.FormatException">Header names are enforced to be valid HTTP tokens, where a token is defined as any set of ASCII letters, digits, or symbols from the ``"!#$%&'*+-.^_`|~"`` set, matching [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-collected-abnf)'s definition. Non-ASCII characters are not allowed in a header name.
+        <exception cref="T:System.FormatException">The header name format is invalid.
 
 -or-