From: Petter Reinholdtsen <pere@hungry.com>
Date: Fri, 11 Oct 2013 12:23:44 +0000 (+0000)
Subject: Typo.
X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/51803e002fb89f76df7365ed4d97d79ac2f022fa?ds=sidebyside

Typo.
---

diff --git a/blog/data/2013-10-11-mesh-network-oslo.txt b/blog/data/2013-10-11-mesh-network-oslo.txt
index 81572467ef..da402aff8a 100644
--- a/blog/data/2013-10-11-mesh-network-oslo.txt
+++ b/blog/data/2013-10-11-mesh-network-oslo.txt
@@ -75,7 +75,7 @@ packets across mesh networks, and OLSR, B.A.T.M.A.N. and
 B.A.T.M.A.N. advanced are protocols used by several free software
 based community mesh networks.</p>
 
-</p>The batman-adv protocol is a bit special, as it provide layer 2
+<p>The batman-adv protocol is a bit special, as it provide layer 2
 (as in ethernet ) routing, allowing ipv4 and ipv6 to work on the same
 network.  One way to think about it is that it provide a mesh based
 vlan you can bridge to or handle like any other vlan connected to your
@@ -85,13 +85,13 @@ least since Debian Wheezy, and it is fairly easy to set up.  A
 introduction</a> is available from the Open Mesh project.  These are
 the key settings needed to join the Oslo meshfx network:</p>
 
-<table>
+<p><table>
 <tr><th>Setting</th><th>Value</th></tr>
 <tr><td>Protocol / kernel module</td><td>batman-adv</td></tr>
 <tr><td>ESSID</td><td>meshfx@hackeriet</td></tr>
 <td>Channel / Frequency</td><td>11 / 2462</td></tr>
 <td>Cell ID</td><td>02:BA:00:00:00:01</td>
-</table>
+</table></p>
 
 <p>The reason for setting ad-hoc wifi Cell ID is to work around bugs
 in firmware used in wifi card and wifi drivers.  (See a nice post from