Edited 15_payment_requests.asciidoc with Atlas code editor

15_payment_requests.asciidoc

@@ -125,11 +125,11 @@ A full list of the currently defined multipliers is given in <<table1502>>.
 |==============================================
 
 
-==== Bech32 & the Data Segment
+==== Bech32 and the Data Segment
 
 If the "unreadable" portion looks familiar, then that's because it uses the
 very same encoding scheme as SegWit compatible Bitcoin addresses use today,
-namely `bech32`. Describing the `bech32` encoding scheme is outside the scope
+namely bech32. Describing the bech32 encoding scheme is outside the scope
 of this chapter. In brief, it's a sophisticated way to encode short strings
 that has very good error correction as well as detection properties.
 
@@ -165,7 +165,7 @@ the invoice.
 The tagged invoice fields are encoded in the main body of the invoice. These
 fields represent different key-value pairs that express either additional
 information that may help complete the payment or information which is
-_required_ to complete the payment. Because a slight variant of `bech32` is
+_required_ to complete the payment. Because a slight variant of bech32 is
 utilized, each of these fields are actually in the "base 5" domain.
 
 A given tag field is comprised of three components: