From 59c449588394dd73caa97b767ee7974dd83e93f1 Mon Sep 17 00:00:00 2001
From: Petter Reinholdtsen <pere@hungry.com>
Date: Sat, 19 Mar 2016 15:29:12 +0100
Subject: [PATCH 1/1] Better markup.

---
 blog/data/2016-03-19-qr-invoice.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/blog/data/2016-03-19-qr-invoice.txt b/blog/data/2016-03-19-qr-invoice.txt
index 333f73c804..6544787cc4 100644
--- a/blog/data/2016-03-19-qr-invoice.txt
+++ b/blog/data/2016-03-19-qr-invoice.txt
@@ -20,7 +20,7 @@ a QR code with the key information of the invoice in JSON format.
 This is the typical content of a QR code following the UsingQR
 specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I've reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:
+to read.  Normally this is all on one long line:</p>
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {
@@ -66,7 +66,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 <a href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
-chance of getting sued...</a>
+chance of getting sued...</a></p>
 
 <p>I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that
-- 
2.50.1