diff --git a/guides/vm-seperation-of-concerns.html b/guides/vm-seperation-of-concerns.html
index 2e4cb29..f9ddef1 100644
--- a/guides/vm-seperation-of-concerns.html
+++ b/guides/vm-seperation-of-concerns.html
@@ -40,6 +40,7 @@
 				<h2>How to seperate concerns</h2>
 				<p>Some people will seperate each service into their own VM, however I don't believe this to be efficient (in all cases).</p>
 				<p>What I recommend is to take your server needs, and break them down into logical blocks, adding each of these blocks to their own VMs. This will keep certain things contained alone, as you want them seperated as much as possible (NAS, etc).</p>
+				<div class="tblcon">
 				<table>
 					<thead><tr><th colspan="2">Concern/VM</th><th colspan="5">Services</th></tr></thead>
 					<tbody>
@@ -74,6 +75,7 @@
 						</tr>
 					</tbody>
 				</table>
+				</div>
 
 				<h2>Why not use a dedicated server for each concern?</h2>
 				<p>You can! No-one's going to stop you, but unless each concern <em>requires</em> (i.e. needs the dedicated hardware/isolation) its own dedicated server, it's hugely redundant. Again NAS as an example, would be good for a dedicated machine, as it'll be safer if there's no additional chance it goes down due to failure of an unrelated service.</p>