diff --git a/xml/System.Threading.Tasks/Task.xml b/xml/System.Threading.Tasks/Task.xml
index cd654e48442..c02a3a08d0e 100644
--- a/xml/System.Threading.Tasks/Task.xml
+++ b/xml/System.Threading.Tasks/Task.xml
@@ -7092,7 +7092,7 @@ An exception was thrown during
 
 ## Remarks
 
-The returned task will complete when any of the supplied tasks has completed.  The returned task will always end in the `RanToCompletion` state with its `Result` set to the first task to complete.  The result value is `true` even if the first task to complete ended in the `Canceled` or `Faulted` state.
+The returned task will complete when any of the supplied tasks has completed.  The returned task will always end in the `RanToCompletion` state with its `Result` set to the first task to complete.  This is true even if the first task to complete ended in the `Canceled` or `Faulted` state.
 
           ]]></format>
         </remarks>
@@ -7359,7 +7359,7 @@ The returned task will complete when any of the supplied tasks has completed.  T
 
 ## Remarks
 
-The returned task will complete when any of the supplied tasks has completed.  The returned task will always end in the `RanToCompletion` state with its `Result` set to the first task to complete.  The result value is `true` even if the first task to complete ended in the `Canceled` or `Faulted` state.
+The returned task will complete when any of the supplied tasks has completed.  The returned task will always end in the `RanToCompletion` state with its `Result` set to the first task to complete.  This is true even if the first task to complete ended in the `Canceled` or `Faulted` state.
 
 > [!TIP]
 > In every overload of Task.WhenAny(), when the method returns the first completed task, the other tasks will continue running until completion, even if any of them completed in the `Canceled` or `Faulted` state. If that behavior is undesirable, you can cancel all the remaining tasks once the first task completes.