@@ -3,7 +3,7 @@ module type Trigger = sig
33 type exn_bt
44
55 (* * Schedulers may handle the {!Await} effect to customize the behavior of
6- [ await] .
6+ {! await} .
77
88 In case the fiber permits propagation of cancelation, the trigger should
99 be attached to the computation of the fiber for the duration of suspending
@@ -25,7 +25,7 @@ module type Computation = sig
2525 type exn_bt
2626
2727 (* * Schedulers may handle the {!Cancel_after} effect to customize the behavior
28- of [ cancel_after] .
28+ of {! cancel_after} .
2929
3030 The scheduler should typically attach a trigger to the computation passed
3131 with the effect and arrange the operation to be canceled upon signal.
@@ -84,7 +84,7 @@ module type Fiber = sig
8484 ]} *)
8585
8686 (* * Schedulers may handle the {!Current} effect to customize the behavior of
87- [ current] .
87+ {! current} .
8888
8989 ⚠️ A handler should eventually resume the fiber without propagating
9090 cancelation. A scheduler may, of course, decide to reschedule the current
@@ -95,7 +95,7 @@ module type Fiber = sig
9595 type _ Effect.t + = private Current : t Effect .t
9696
9797 (* * Schedulers may handle the {!Yield} effect to customize the behavior of
98- [ yield] .
98+ {! yield} .
9999
100100 Just like with {!Current}, a handler should either continue or discontinue
101101 the fiber, but, unlike with {!Current}, the scheduler should give priority
@@ -104,7 +104,7 @@ module type Fiber = sig
104104 type _ Effect.t + = private Yield : unit Effect .t
105105
106106 (* * Schedulers may handle the {!Spawn} effect to customize the behavior of
107- [ spawn] .
107+ {! spawn} .
108108
109109 The scheduler is free to run the newly created fibers on any domain and
110110 decide which fiber to give priority to. *)
0 commit comments