From 6446f2af0a75e513a0c4bad0ddaad8d798bd5e2d Mon Sep 17 00:00:00 2001
From: Pieter Wuille <pieter@wuille.net>
Date: Fri, 29 Jan 2021 11:33:33 -0800
Subject: Update bip-0350.mediawiki

Co-authored-by: andrewtoth <andrewstoth@gmail.com>
---
 bip-0350.mediawiki | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'bip-0350.mediawiki')

diff --git a/bip-0350.mediawiki b/bip-0350.mediawiki
index d09ae6b..f34da56 100644
--- a/bip-0350.mediawiki
+++ b/bip-0350.mediawiki
@@ -121,7 +121,7 @@ def decode(hrp, addr):
 
 '''Error locating'''
 
-Bech32m, like Bech32m, does support locating<ref>'''What about error correction?''' As explained in BIP173, introducing error correction reduces the ability to detect errors. While it is technically possible to correct a small number of errors due to Bech32(m)'s nature as a BCH code, implementations should refrain from using this for more than indicating where an error may be present.</ref> the positions of a few substitution errors. To combine this functionality with
+Bech32m, like Bech32, does support locating<ref>'''What about error correction?''' As explained in BIP173, introducing error correction reduces the ability to detect errors. While it is technically possible to correct a small number of errors due to Bech32(m)'s nature as a BCH code, implementations should refrain from using this for more than indicating where an error may be present.</ref> the positions of a few substitution errors. To combine this functionality with
 the segregated witness addresses proposed by this document, simply try locating errors for both Bech32 and Bech32m. If only one finds error locations, report that one. If both do (which should be very rare),
 there are a number of options:
 * Report the one that needs fewer corrections (if they differ).
-- 
cgit v1.2.3

