bolt8

commit a1c088c138baf941d603c055ae660868522b7b79
parent c390306df8ac5eab77f9bf0713d437a25106fcbc
Author: Jared Tobin <jared@jtobin.io>
Date:   Sat, 10 Oct 2026 13:42:41 +0400

docs: avoid an ambiguous haddock reference

Diffstat:
M
lib/Lightning/Protocol/BOLT8.hs
 | 
10
+++++-----

1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/lib/Lightning/Protocol/BOLT8.hs b/lib/Lightning/Protocol/BOLT8.hs
@@ -61,11 +61,11 @@
 --
 -- = Security
 --
--- * __Use each state exactly once.__ Every function that takes a
---   state (t'Initiator', t'Responder', t'Sender', t'Receiver' or
---   t'Pending') returns the next one, and the caller must continue with
---   that. States are ordinary immutable values, so nothing stops an old
---   one from being used again, and doing so is catastrophic: encrypting
+-- * __Use each state exactly once.__ Every function that takes an
+--   t'Initiator', t'Responder', t'Sender', t'Receiver' or t'Pending'
+--   returns the next state, and the caller must continue with that.
+--   States are ordinary immutable values, so nothing stops an old one
+--   from being used again, and doing so is catastrophic: encrypting
 --   twice with the same t'Sender' reuses a nonce, which reveals the XOR
 --   of the two plaintexts and allows forgeries, and decrypting with an
 --   old t'Receiver' accepts replayed frames.