Edited 15_payment_requests.asciidoc with Atlas code editor

15_payment_requests.asciidoc

@@ -57,7 +57,7 @@ a mechanism that allows a sender to typically request a new payment request
 from the receiver, then an interactive protocol can be used to allow a
 degree of payment request reuse.
 
-=== BOLT 11: Lightning Payment Request Serialization & Interpretation
+=== BOLT #11: Lightning Payment Request Serialization & Interpretation
 
 In this section, we'll describe the mechanism used to encode the set of
 information required to complete a payment on the Lightning Network. As
@@ -91,10 +91,10 @@ its own human-readable prefix (see <<table1501>>). This allows client software a
 quickly determine if a payment request can be satisfied by their node or not.
 
 [[table1501]]
-.BOLT 11 network prefixes
+.BOLT #11 network prefixes
 [options="header"]
 |=============================
-|Network       |BOLT 11 prefix
+|Network       |BOLT #11 prefix
 |mainnet       |`lnbc`
 |testnet       |`lntb`
 |simnet/regtest|`lnbcrt`
@@ -114,7 +114,7 @@ of an invoice at a glance, take the base factor and multiply it by the
 A full list of the currently defined multipliers is given in <<table1502>>.
 
 [[table1502]]
-.BOLT 11 amount multipliers
+.BOLT #11 amount multipliers
 [options="header"]
 |==============================================
 |Multiplier|Bitcoin unit|Multiplication factor
@@ -144,7 +144,7 @@ timestamp allows the sender to gauge how old the invoice is, and as we'll see
 later, allows the receiver to force an invoice to only be valid for a period of
 time if they wish.
 
-Similar to the TLV format we learned about in <<tlv>>, the BOLT 11 invoice
+Similar to the TLV format we learned about in <<tlv>>, the BOLT #11 invoice
 format uses a series of extensible key-value pairs to encode information
 needed to satisfy a payment. Because key-value pairs are used, it's easy to add
 new values in the future if a new payment type or additional
@@ -177,7 +177,7 @@ A given tag field is comprised of three components:
 A full list of all the currently defined tagged fields is given in <<table1503>>.
 
 [[table1503]]
-.BOLT 11 tagged invoice fields
+.BOLT #11 tagged invoice fields
 [options="header"]
 |===
 |Field tag|Data length|Usage