[glib-networking/mcatanzaro/tls-thread: 23/26] progress

[Michael Catanzaro <mcatanzaro src gnome org>]

commit bc5f69ae9e16bccb5b7e78bad8777355ce7e86e3
Author: Michael Catanzaro <mcatanzaro gnome org>
Date:   Sat Dec 28 10:45:43 2019 -0600

    progress

 tls/base/gtlsoperationsthread-base.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/tls/base/gtlsoperationsthread-base.c b/tls/base/gtlsoperationsthread-base.c
index 0eecf58..a54c274 100644
--- a/tls/base/gtlsoperationsthread-base.c
+++ b/tls/base/gtlsoperationsthread-base.c
@@ -47,9 +47,9 @@
  *   from separate reader and writer threads simultaneously.
  *
  * While the TLS thread class is intended to simplify our code, it has one major
- * disadvantage: the TLS thread *must never block* because GIOStream users are
- * allowed to do a sync read and a sync write simultaneously in separate
- * threads. Consider a hypothetical scenario:
+ * disadvantage: the TLS thread *must never block* during read or write
+ * operations, because GIOStream users are allowed to do a sync read and a sync
+ * write simultaneously in separate threads. Consider a hypothetical scenario:
  *
  * (1) Application starts a read on thread A
  * (2) Application starts a write on thread B