Edited 09_channel_operation.asciidoc with Atlas code editor

09_channel_operation.asciidoc

@@ -132,6 +132,7 @@ There are three ways to claim this output. Try to read the script and see if you
 .Bob's new commitment with an HTLC output
 image::images/mtln_0905.png["Bob's new commitment with an HTLC output"]
 
+[role="pagebreak-before less_space"]
 ==== Alice Commits
 
 Shortly after sending the +update_add_htlc+ message, she will commit to the new state of the channel, so that the HTLC can be safely added by Bob. Bob has the HTLC information and has constructed a new commitment but does not yet have this new commitment signed by Alice.
@@ -203,6 +204,7 @@ Next, the message flow for +commitment_signed+ and +revoke_and_ack+ is now repea
 
 For completeness sake, let's quickly review the commitment transactions as this round of commitment/revocation happens.
 
+[role="pagebreak-before less_space"]
 ==== Bob Commits
 
 Bob now sends a +commitment_signed+ back to Alice, with his signatures for Alice's new commitment transaction, including the HTLC output she has added.
@@ -297,6 +299,7 @@ They create new commitments (Commitment #4), as shown in <<htlc_fulfillment_comm
 .The HTLC is removed and balances are updated in new commitments
 image::images/mtln_0912.png[The HTLC is removed and balances are updated in new commitments]
 
+[role="pagebreak-before"]
 Next, they complete two rounds of commitment and revocation. First, Alice sends +commitment_signed+ to sign Bob's new commitment transaction. Bob responds with +revoke_and_ack+ to revoke his old commitment. Once Bob has moved the state of the channel forward, the commitments look like we see in <<htlc_fulfillment_commitments_bob_commit>>. 
 
 [[htlc_fulfillment_commitments_bob_commit]]