Typo.

diff --git a/blog/data/2013-10-27-vmdebootstrap-rpi.txt b/blog/data/2013-10-27-vmdebootstrap-rpi.txt
index a335940a6dfc1f227835ae174f34fa3d035c6b5a..726a4ed6d86d6aa55cd9d74cb8ab3be453475782 100644 (file)
--- 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
 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
 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