Use code block for bitcoin: URI example

diff --git a/index.html b/index.html
index 176a5839a645b038676f50b2e9261cad146df8ec..86739cdda77c3949697df8d03dc188f469dc1646 100644 (file)
--- a/index.html
+++ b/index.html
@@ -276,7 +276,7 @@
                </div>
                <div class="footer">
                        <h2>How It Works</h2>
-                       <p class="small-print">BIP 353 resolves DNS TXT records into bitcoin: URIs. Any standard (reusable) bitcoin: URI should work, for example a URI with a BOLT 12 offer (starting with lno), a Silent Payments Address (starting with sp), and an on-chain address may look like <span class="small-print mono">bitcoin:1OnChain?lno=lno1lightningoffer&amp;sp=sp1qsilentpayment</span></p>
+                       <p class="small-print">BIP 353 resolves DNS TXT records into <span class="mono">bitcoin:</span> URIs. Any standard (reusable) <span class="mono">bitcoin:</span> URI should work, for example a URI with a BOLT 12 offer (starting with lno), a Silent Payments Address (starting with sp), and an on-chain address may look like <code class="mono">bitcoin:1OnChain?lno=lno1lightningoffer&amp;sp=sp1qsilentpayment</code></p>
                        <p class="small-print">Note that most BIP 353 names rely on <a href="https://bolt12.org">BOLT 12</a> or <a href="https://silentpayments.xyz">Silent Payments</a> and as both are relatively new, wallet support isn't yet universal.</p>
                        <p class="small-print">While you're absolutely trusting this site to not provide you with backdoored code, names are fully validated locally on your machine using DNSSEC. Thus, no matter what server you use to resolve the name, the worst they can do is log who you're paying or tell you they're not payable. They can never give you the wrong address!</p>
                        <p class="small-print">Trust someone else to host a name for you? Check out <a href="https://twelve.cash">twelve.cash</a></p>