diff --git a/guides/guide-to-server-hosting.html b/guides/guide-to-server-hosting.html
index 0e6bb65..ffb5fac 100644
--- a/guides/guide-to-server-hosting.html
+++ b/guides/guide-to-server-hosting.html
@@ -52,7 +52,7 @@
 					<li><a href="/guides/setup-kvm-bridge.html">Setup a bridged adapter</a></li>
 					<li>TODO:<a href="/guides/install-kvm-virtual-machine.html">Install a virtual machine</a></li>
 					<li>TODO:<a href="/guides/virsh-cheatsheet.html">Virsh cheatsheet</a></li>
-					<li>TODO:<a href="/guides/vm-seperation-of-concerns">Example of Separation of Concerns (SoC)</a></li>
+					<li><a href="/guides/vm-seperation-of-concerns">Example of Separation of Concerns (SoC)</a></li>
 				</ul>
 
 				<h2>Nginx Webserver</h2>
diff --git a/guides/vm-seperation-of-concerns.html b/guides/vm-seperation-of-concerns.html
index f9ddef1..e210c46 100644
--- a/guides/vm-seperation-of-concerns.html
+++ b/guides/vm-seperation-of-concerns.html
@@ -79,7 +79,6 @@
 
 				<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>
-				<p>Virtual Machines are wonderful, as they allow you to make use of more powerful/high spec machines while minimising the wasted usage...</p>
 			</section>
 		</main>