Apply suggestions from code review

Co-authored-by: Genevieve Warren <[email protected]>

Author: antonfirsov

xml/System.Net.Http/HttpClient.xml

@@ -600,11 +600,11 @@ The <paramref name="requestUri" /> is not an absolute URI.
 -or-
 
 <see cref="P:System.Net.Http.HttpClient.BaseAddress" /> is not set.</exception>
-        <exception cref="T:System.Net.Http.HttpRequestException">The request failed due to an issue getting a valid HTTP response such as network connectivity failure, DNS failure, server certificate validation error or invalid server response. On .NET 8+ the reason is indicated by <see cref="P:System.Net.Http.HttpRequestException.HttpRequestError" />
+        <exception cref="T:System.Net.Http.HttpRequestException">The request failed due to an issue getting a valid HTTP response, such as network connectivity failure, DNS failure, server certificate validation error, or invalid server response. On .NET 8 and later versions, the reason is indicated by <see cref="P:System.Net.Http.HttpRequestException.HttpRequestError" />.
 
 -or-
 
-.NET Framework only: the request timed out.</exception>
+.NET Framework only: The request timed out.</exception>
         <exception cref="T:System.OperationCanceledException">.NET Core and .NET 5 and later only: The request failed due to timeout.</exception>
       </Docs>
     </Member>
@@ -1681,15 +1681,15 @@ the respose status code was outside of the range of 200-299 (status codes indica
           ]]></format>
         </remarks>
         <exception cref="T:System.InvalidOperationException">The <paramref name="requestUri" /> must be an absolute URI or <see cref="P:System.Net.Http.HttpClient.BaseAddress" /> must be set.</exception>
-        <exception cref="T:System.Net.Http.HttpRequestException">The request failed due to an issue getting a valid HTTP response such as network connectivity failure, DNS failure, server certificate validation error or invalid server response. On .NET 8+ the reason is indicated by <see cref="P:System.Net.Http.HttpRequestException.HttpRequestError" />
+        <exception cref="T:System.Net.Http.HttpRequestException">The request failed due to an issue getting a valid HTTP response, such as network connectivity failure, DNS failure, server certificate validation error, or invalid server response. On .NET 8+, the reason is indicated by <see cref="P:System.Net.Http.HttpRequestException.HttpRequestError" />.
 
 -or-
 
-the respose status code was outside of the range of 200-299 (status codes indicating success according to the standard)
+The response status code was outside of the range of 200-299 (which indicate success according to the standard).
 
 -or-
 
-.NET Framework only: the request timed out.</exception>
+.NET Framework only: The request timed out.</exception>
         <exception cref="T:System.OperationCanceledException">.NET Core and .NET 5 and later only: The request failed due to timeout.</exception>
       </Docs>
     </Member>
@@ -2573,8 +2573,8 @@ The size specified is greater than the maximum allowed buffer size.</exception>
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.InvalidOperationException">The <paramref name="requestUri" /> must be an absolute URI or <see cref="P:System.Net.Http.HttpClient.BaseAddress" /> must be set.</exception>
-        <exception cref="T:System.Net.Http.HttpRequestException">The request failed due to an issue getting a valid HTTP response such as network connectivity failure, DNS failure, server certificate validation error or invalid server response. On .NET 8+ the reason is indicated by <see cref="P:System.Net.Http.HttpRequestException.HttpRequestError" /></exception>
+        <exception cref="T:System.InvalidOperationException">The <paramref name="requestUri" /> is not an absolute URI and <see cref="P:System.Net.Http.HttpClient.BaseAddress" /> isn't set.</exception>
+        <exception cref="T:System.Net.Http.HttpRequestException">The request failed due to an issue getting a valid HTTP response, such as network connectivity failure, DNS failure, server certificate validation error, or invalid server response. On .NET 8+, the reason is indicated by <see cref="P:System.Net.Http.HttpRequestException.HttpRequestError" />.</exception>
         <exception cref="T:System.OperationCanceledException">The request failed due to timeout.</exception>
         <exception cref="T:System.UriFormatException">The provided request URI is not valid relative or absolute URI.</exception>
       </Docs>

xml/System.Net.Http/HttpResponseMessage.xml

@@ -351,9 +351,9 @@ When the `disposing` parameter is `true`, this method releases all resources hel
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode%2A> method throws an <xref:System.Net.Http.HttpRequestException> if <xref:System.Net.Http.HttpResponseMessage.StatusCode> is outside of the range the range 200-299 (the range of status codes indicating success according to the standard).
- In some scenarios you may need stronger control defining which status codes are considered to be succesful; for example an API may be expected to always return `200 OK`. In such cases we recommend to manually check if <xref:System.Net.Http.HttpResponseMessage.StatusCode> matches the expected value(s).
- In .NET Framework and .NET Core 2.2 and earlier versions, if the <xref:System.Net.Http.HttpResponseMessage.Content%2A> is not `null`, this method will also call <xref:System.Net.Http.HttpResponseMessage.Dispose%2A> to free managed and unmanaged resources. Starting with .NET Core 3.0, the content will not be disposed. 
+ The <xref:System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode%2A> method throws an <xref:System.Net.Http.HttpRequestException> if <xref:System.Net.Http.HttpResponseMessage.StatusCode> is outside of the range 200-299 (the range of status codes indicating success according to the standard).
+ In some scenarios, you might need more control over which status codes are considered to be successful; for example, an API might be expected to always return `200 OK`. In such cases, we recommend to manually check if <xref:System.Net.Http.HttpResponseMessage.StatusCode> matches the expected value.
+ In .NET Framework and .NET Core 2.2 and earlier versions, if the <xref:System.Net.Http.HttpResponseMessage.Content%2A> is not `null`, this method also calls <xref:System.Net.Http.HttpResponseMessage.Dispose%2A> to free managed and unmanaged resources. Starting with .NET Core 3.0, the content is not disposed. 
 
  ]]></format>
         </remarks>