Fix the BQ interface comments pertaining to recovery data

1 files changed, 2 insertions, 4 deletions

diff --git a/src/rabbit_backing_queue.erl b/src/rabbit_backing_queue.erl
index f66327ace8..2b561900e6 100644
--- a/src/rabbit_backing_queue.erl
+++ b/src/rabbit_backing_queue.erl
@@ -57,10 +57,8 @@
 %% 1. the amqqueue record
 %% 2. a term indicating whether the queue is an existing queue that
 %%    should be recovered or not. When 'new' is given, no recovery is
-%%    taking place, otherwise a tuple containing the process id of a
-%%    "barrier process" (on which to wait for a {BarrierPid, 'go'}
-%%    notification) is passed as the first element, whilst the second
-%%    holds either a list of recovery terms or the atom 'non_clean_shutdown'.
+%%    taking place, otherwise a list of recovery terms is given, or
+%%    the atom 'non_clean_shutdown' if no recovery terms are available.
 %% 3. an asynchronous callback which accepts a function of type
 %%    backing-queue-state to backing-queue-state. This callback
 %%    function can be safely invoked from any process, which makes it