From 07e962a1dad3dadb568d3e2cda8c3c28bd3d4747 Mon Sep 17 00:00:00 2001
From: compudj <compudj@04897980-b3bd-0310-b5e0-8ef037075253>
Date: Thu, 22 Jan 2009 00:32:53 +0000
Subject: [PATCH] update features

git-svn-id: http://ltt.polymtl.ca/svn@3279 04897980-b3bd-0310-b5e0-8ef037075253
---
 trunk/lttv/QUICKSTART.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/trunk/lttv/QUICKSTART.html b/trunk/lttv/QUICKSTART.html
index 220ce051..137b3f8c 100644
--- a/trunk/lttv/QUICKSTART.html
+++ b/trunk/lttv/QUICKSTART.html
@@ -570,11 +570,11 @@ A few examples of successful LTTng users :
   and to help them solve hard to reproduce problems. They have had
   success with such tracing approach to fix "rare disk delay" issues and
   VM-related issues presented in this article :
-
-  * "Linux Kernel Debugging on Google-sized clusters at Ottawa Linux
+<ul>
+  <li> "Linux Kernel Debugging on Google-sized clusters at Ottawa Linux
     Symposium 2007"
     http://ltt.polymtl.ca/papers/bligh-Reprint.pdf
-
+</ul>
 <li> IBM Research have had problems with Commercial Scale-out applications,
   which are being an increasing trend to split large server workloads.
   They used LTTng successfully to solve a distributed filesystem-related
-- 
2.34.1