Improve documentation comment

asmcomp/dataflow.mli

@@ -44,8 +44,8 @@ module Backward(D: DOMAIN) : sig
      The [transfer] function is called as [transfer i at_next at_raise].
      - [i] is a sub-instruction of [instr].
      - [at_next] is the abstract state "after" the instruction for
-       to normal control flow, falling through the successor(s) of [i].
-     - [at_next] is the abstract state "after" the instruction for
+       normal control flow, falling through the successor(s) of [i].
+     - [at_raise] is the abstract state "after" the instruction for
        exceptional control flow, branching to the nearest exception handler
        or exiting the function with an unhandled exception.
 
@@ -85,9 +85,10 @@ module Backward(D: DOMAIN) : sig
      The optional [constant_transfer] argument can speed up the analysis
      in a few use cases.  This argument is a predicate over Mach operations.
      It flags cases where the transfer function returns the same result
-     regardless of the [at_next] and [at_raise] results.  In this case,
-     the [at_next] abstract state is not computed, and the transfer function
-     is called with [D.bot] for the [at_next] argument.
+     regardless of the [at_next] and [at_raise] results.  If
+     [constant_transfer] returns [true], the [at_next] abstract state
+     is not computed, and the transfer function is called with [D.bot]
+     for the [at_next] argument.
      A consequence of this optimization is that some reachable parts
      of the Mach code are not analyzed at all.  For this reason, the
      second part of the result (the function [int -> D.t] associating