diff --git a/src/libraries/Microsoft.Extensions.Http/src/Logging/IHttpClientAsyncLogger.cs b/src/libraries/Microsoft.Extensions.Http/src/Logging/IHttpClientAsyncLogger.cs
index 307078a00754a..e23abe8db815b 100644
--- a/src/libraries/Microsoft.Extensions.Http/src/Logging/IHttpClientAsyncLogger.cs
+++ b/src/libraries/Microsoft.Extensions.Http/src/Logging/IHttpClientAsyncLogger.cs
@@ -19,7 +19,7 @@ namespace Microsoft.Extensions.Http.Logging
     /// would be called from the corresponding sync code paths.
     /// </para>
     /// <para>
-    /// It is up to the user implementing the interface to decide where (to <see cref="Microsoft.Extensions.Logging.ILogger"/>, or anything else) and what exactly to log.
+    /// It is up to the user implementing the interface to decide whether to use <see cref="Microsoft.Extensions.Logging.ILogger"/>, or anything else, and what exactly to log.
     /// However, the implementation should be mindful about potential adverse side effects of accessing some of the <see cref="HttpRequestMessage"/> or
     /// <see cref="HttpResponseMessage"/> properties, such as reading from a content stream; if possible, such behavior should be avoided.
     /// </para>
diff --git a/src/libraries/Microsoft.Extensions.Http/src/Logging/IHttpClientLogger.cs b/src/libraries/Microsoft.Extensions.Http/src/Logging/IHttpClientLogger.cs
index e9c61ae312959..a0a473ce1cdc1 100644
--- a/src/libraries/Microsoft.Extensions.Http/src/Logging/IHttpClientLogger.cs
+++ b/src/libraries/Microsoft.Extensions.Http/src/Logging/IHttpClientLogger.cs
@@ -11,7 +11,7 @@ namespace Microsoft.Extensions.Http.Logging
     /// </summary>
     /// <remarks>
     /// <para>
-    /// It is up to the user implementing the interface to decide where (to <see cref="Microsoft.Extensions.Logging.ILogger"/>, or anything else) and what exactly to log.
+    /// It is up to the user implementing the interface to decide whether to use <see cref="Microsoft.Extensions.Logging.ILogger"/>, or anything else, and what exactly to log.
     /// However, the implementation should be mindful about potential adverse side effects of accessing some of the <see cref="HttpRequestMessage"/> or
     /// <see cref="HttpResponseMessage"/> properties, such as reading from a content stream; if possible, such behavior should be avoided.
     /// </para>