Edited 10_onion_routing.asciidoc with Atlas code editor

10_onion_routing.asciidoc

@@ -342,6 +342,7 @@ because of associativity, we can move the parentheses
 </ul>
 ++++
 
+[role="pagebreak-before"]
 because _xy_ = _yx_ (the curve is an abelian group)
 
 ++++
@@ -707,14 +708,14 @@ In this case, Bob extracts the inner HMAC (he's already verified the integrity o
 
 Now Bob can remove his hop payload from the front of the onion and left-shift the remaining data. An amount of data equal to Bob's hop payload from the second-half 1,300 bytes of filler will now shift into the onion payload space. This is shown in <<bob_removes_shifts>>. 
 
-[[bob_removes_shifts]]
-.Bob removes the hop payload and left-shifts the rest, filling the gap with new filler
-image::images/mtln_1025.png["Bob removes the hop payload and left-shifts the rest, filling the gap with new filler"]
-
 Now Bob can keep the first half 1,300 bytes, and discard the extended (filler) 1,300 bytes.
 
 Bob now has a 1,300-byte onion packet to send to the next hop. It is almost identical to the onion payload that Alice had created for Chan, except that the last 65 or so bytes of filler was put there by Bob and will be different.
 
+[[bob_removes_shifts]]
+.Bob removes the hop payload and left-shifts the rest, filling the gap with new filler
+image::images/mtln_1025.png["Bob removes the hop payload and left-shifts the rest, filling the gap with new filler"]
+
 No one can tell the difference between filler put there by Alice and filler put there by Bob. Filler is filler! It's all random bytes anyway. Note that if Bob (or one of Bob's other aliases) is present in the route in two distinct locations, then they can tell the difference because the base protocol always uses the same payment hash across the entire route. Atomic multipath payments (AMPs) and Point Time-Locked Contracts (PTLCs) eliminate the correlation vector by randomizing the payment identifier across each route/hop.
 
 ==== Bob Constructs the New Onion Packet