Note that two-phase cyclic barriers are suitable for use in loops.
diff --git a/Doc/whatsnew/3.2.rst b/Doc/whatsnew/3.2.rst
index e342b87..bdcf588 100644
--- a/Doc/whatsnew/3.2.rst
+++ b/Doc/whatsnew/3.2.rst
@@ -834,8 +834,10 @@
of a `Rendezvous <http://en.wikipedia.org/wiki/Synchronous_rendezvous>`_ which
is defined for only two threads.
-The barrier is designed to be cyclic, making it reusable once all of the
-waiting threads are released.
+Implemented as a two-phase cyclic barrier, :class:`~threading.Barrier` objects
+are suitable for use in loops. The separate *filling* and *draining* phases
+assure that all threads get released (drained) before any one them can loop back
+and re-enter the barrier. The barrier fully resets after each cycle.
If any of the predecessor tasks can hang or be delayed, a barrier can be created
with an optional *timeout* parameter. Then if the timeout period elapses before