Edited 09_channel_operation.asciidoc with Atlas code editor

09_channel_operation.asciidoc

@@ -1,5 +1,5 @@
 [[channel_operation]]
-== Channel Operation and Payment Forwarding
+== Channel Operation and pass:[<span class="keep-together">Payment Forwarding</span>]
 
 ((("payment channel","operation", id="ix_09_channel_operation-asciidoc0", range="startofrange")))In this chapter we will bring together payment channels and hash time-locked contracts (HTLCs). In <<payment_channels>> we explained the way Alice and Bob construct a payment channel between their two nodes. We also looked at the commitment and penalty mechanisms that secure the payment channel. In <<routing>> we looked at hash time-locked contracts (HTLCs) and how these can be used to route a payment across a path made of multiple payment channels. In this chapter we bring the two concepts together by looking at how HTLCs are managed on each payment channel, how the HTLCs are committed to the channel state, and how they are settled to update the channel balances.
 
@@ -34,6 +34,7 @@ We will focus on the payment channel between Alice and Bob and review the messag
 .The message flow for HTLC commitment between channel partners
 image::images/mtln_0903.png["The message flow for HTLC commitment between channel partners"]
 
+[role="pagebreak-before"]
 We've already seen the +commitment_signed+ and +revoke_and_ack+ in <<payment_channels>>. Now we will see how HTLCs fit into the commitment scheme. The two new messages are +update_add_htlc+, which Alice uses to ask Bob to add an HTLC, and +update_fulfill_htlc+, which Bob uses to redeem the HTLC once he has received the payment secret (Dina's secret).(((range="endofrange", startref="ix_09_channel_operation-asciidoc3")))(((range="endofrange", startref="ix_09_channel_operation-asciidoc2")))(((range="endofrange", startref="ix_09_channel_operation-asciidoc1")))
 
 === Forwarding Payments with HTLCs