From aae4f6d167090e3ed7c8519363a291afb05e686d Mon Sep 17 00:00:00 2001
From: Petter Reinholdtsen <pere@hungry.com>
Date: Sun, 27 Oct 2013 18:29:08 +0000
Subject: [PATCH] Typo.

---
 blog/data/2013-10-27-vmdebootstrap-rpi.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/blog/data/2013-10-27-vmdebootstrap-rpi.txt b/blog/data/2013-10-27-vmdebootstrap-rpi.txt
index a335940a6d..726a4ed6d8 100644
--- a/blog/data/2013-10-27-vmdebootstrap-rpi.txt
+++ b/blog/data/2013-10-27-vmdebootstrap-rpi.txt
@@ -21,7 +21,7 @@ architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
 code and adjusted it to be able to build armel images on my amd64
 Debian laptop.  I ended up giving vmdebootstrap five new options,
 allowing me to replicate the image creation process I use to make
-<a href=http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html"">Debian
+<a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian
 Jessie based mesh node images for the Raspberry Pi</a>.  First, the
 <tt>--foreign /path/to/binfm_handler</tt> option tell vmdebootstrap to
 call debootstrap with --foreign and to copy the handler into the
-- 
2.47.2