Edited 07_payment_channels.asciidoc with Atlas code editor

07_payment_channels.asciidoc

@@ -489,7 +489,7 @@ In <<asymmetric_1>> we see that Alice holds a transaction that pays 60,000 satos
 
 Bob holds the mirror-image of that transaction, where the first output is 80,000 satoshis _to_self_ (can be spent by Bob's keys), and 60,000 satoshis _to_remote_ (can be spent by Alice's keys).
 
-==== Delayed (Timelocked) Spending To_Self
+==== Delayed (Timelocked) Spending to_self
 
 Using asymmetric transactions allows the protocol to easily ascribe _blame_ to the cheating party. An invariant that the _broadcasting_ party must always wait ensures that the "honest" party has time to refute the claim, and revoke their funds. This asymmetry is manifested in the form of differing outputs for each side: the _to_local_ output is always timelocked and can't be spent immediately, whereas the _to_remote_ output is not timelocked and can be spent immediately.
 
@@ -604,7 +604,7 @@ The use of HTLCs to commit updates will be explained in detail in <<htlcs>> and
 
 Alice's +commitment_signed+ message gives Bob the signature needed (Alice's part of the 2-of-2) for a new commitment transaction.
 
-==== The Revoke_And_Ack Message
+==== The revoke_and_ack Message
 
 Now that Bob has a new commitment transaction, he can revoke the previous commitment by giving Alice a revocation key, and construct the new commitment with Alice's signature.
 
@@ -718,7 +718,7 @@ Bob will respond with his own +shutdown+ message indicating that he agrees to co
 
 Now both Alice and Bob have each other's preferred wallet address, they can construct identical closing transactions to settle the channel balance.
 
-==== The Closing_Signed Message
+==== The closing_signed Message
 
 Assuming the channel has no outstanding commitments or updates and the channel partners have exchanged the +shutdown+ messages shown in the previous section, they can now finish this cooperative close.