Fix comment

Author: ansd

deps/rabbit/src/mc.erl

@@ -481,7 +481,7 @@ is_cycle_v2(TargetQueue, Deaths) ->
 %% queue name and there are no newer deaths with the 'rejected' reason then
 %% consider this a cycle."
 %% However, the correct death order cannot be reliably determined in v1.
-%% deaths_v2 fixes this bug.
+%% v2 fixes this bug.
 is_cycle_v1(_Queue, []) ->
     false;
 is_cycle_v1(_Queue, [{_Q, rejected} | _]) ->

deps/rabbit/test/message_containers_deaths_v2_SUITE.erl

@@ -67,10 +67,7 @@ enable_feature_flag(Config) ->
     amqp_channel:call(Ch,
                       #'basic.publish'{routing_key = Q1},
                       #amqp_msg{payload = P2}),
-
-    %% We now have 2 messages in Q2 with different mc annotations:
-    %% * deaths for v1 in the 1st msg
-    %% * deaths_v2 for v2 in the 2nd msg
+    %% We now have 2 messages in Q2 with different values for the mc deaths annotation for v1 and v2.
 
     reject(Ch, Q2, P1),
     reject(Ch, Q2, P2),