diff --git a/index.php b/index.php
index 5d70765..c9a894a 100755
--- a/index.php
+++ b/index.php
@@ -48,7 +48,8 @@
 </ul>
 The most interesting bit about TCF is its <b>modularity to support maximum code re-use</b>. 
 You can adopt TCF only for auto-discovery and launching, but keep gdb for debugging by using the
-TCF gdb remote launch. See the <a href="http://wiki.eclipse.org/TCF">TCF Wiki</a> for details.</p> 
+TCF gdb remote launch.<br/>
+See the <a href="http://wiki.eclipse.org/TCF">TCF Wiki</a> for details.</p> 
 
 <img class="displayed" src="/tcf/images/te_on_pi.png" alt="TCF Target Explorer on Raspberry Pi" border="0" width="609px" height="413px" />
 
@@ -64,7 +65,8 @@
 </div>
 
 <div class="sideitem">
-<h3>News: TCF Debug supports ARM</h3>
+<h3>News:<br/>
+TCF Debug supports ARM</h3>
 <p><i>March 25, 2013 -</i>Initial <a href="http://tmober.blogspot.com/2013/03/eclipsecon-2013-tcf-arm-debugging-and.html">
 ARM debugging support</a> has been added to TCF. Look at the <a href="http://wiki.eclipse.org/TCF/Raspberry_Pi">Raspberry Pi HOWTO</a>.
 </div>
@@ -75,7 +77,7 @@
 By replacing a gdb based debugger with TCF, Xilinx has increased the performance
 of basic debugger commands up to 50 times, while providing a much more stable product.<br/>
 The modular and asynchronous approach of TCF is so compelling that we are moving
-over our JTAG tools to use the same framework.</i></p><p>
+over our JTAG tools to use the same framework.</i><br/><br/>
 &mdash; Tomas Evensen, Chief Scientist Embedded Software, Xilinx</p>
 </div>