Edited 10_onion_routing.asciidoc with Atlas code editor

10_onion_routing.asciidoc

@@ -717,6 +717,7 @@ Bob now has a 1,300-byte onion packet to send to the next hop. It is almost iden
 .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"]
 
+[role="pagebreak-before"]
 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