From 2de8f98a62d04c068e1b4113e7545969c9ae9e01 Mon Sep 17 00:00:00 2001
From: Andrew Stanton-Nurse <andrew@andrewnurse.net>
Date: Tue, 8 Nov 2016 09:15:58 -0800
Subject: [PATCH] update doc comments on WebSocketConnection

---
 .../WebSocketConnection.cs                                   | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/src/Microsoft.Extensions.WebSockets.Internal/WebSocketConnection.cs b/src/Microsoft.Extensions.WebSockets.Internal/WebSocketConnection.cs
index b775d59db2..5e7a96a5f8 100644
--- a/src/Microsoft.Extensions.WebSockets.Internal/WebSocketConnection.cs
+++ b/src/Microsoft.Extensions.WebSockets.Internal/WebSocketConnection.cs
@@ -17,9 +17,8 @@ namespace Microsoft.Extensions.WebSockets.Internal
     /// </summary>
     /// <remarks>
     /// <para>
-    /// This type is thread-safe under the following condition: No two threads attempt to call either
-    /// <see cref="ExecuteAsync"/> or <see cref="SendAsync"/> simultaneously. Different threads may call each method, but the same method
-    /// cannot be re-entered while it is being run in a different thread.
+    /// This type is thread-safe, as long as only one thread ever calls <see cref="ExecuteAsync"/>. Multiple threads may call <see cref="SendAsync"/> simultaneously
+    /// and the sends will block until ongoing send operations complete.
     /// </para>
     /// <para>
     /// The general pattern of having a single thread running <see cref="ExecuteAsync"/> and a separate thread running <see cref="SendAsync"/> will