Edited 15_payment_requests.asciidoc with Atlas code editor

15_payment_requests.asciidoc

@@ -128,7 +128,7 @@ A full list of the currently defined multipliers is given in <<table1502>>.
 ==== Bech32 and the Data Segment
 
 ((("bech32, Lightning invoices and")))((("Lightning invoices","bech32 and data segment")))If the "unreadable" portion looks familiar, then that's because it uses the
-savery same encoding scheme as SegWit compatible Bitcoin addresses use today,
+very same encoding scheme as SegWit compatible Bitcoin addresses use today,
 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.