[releng] Commit of misc. formatting and 'cleanup' of non-Java files.
diff --git a/bundles/org.eclipse.test.performance.ui/.classpath b/bundles/org.eclipse.test.performance.ui/.classpath
index 098194c..f2561d6 100644
--- a/bundles/org.eclipse.test.performance.ui/.classpath
+++ b/bundles/org.eclipse.test.performance.ui/.classpath
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <classpath>
-	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.7"/>
-	<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
-	<classpathentry kind="src" path="src"/>
-	<classpathentry kind="output" path="bin"/>
+    <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.7"/>
+    <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
+    <classpathentry kind="src" path="src"/>
+    <classpathentry kind="output" path="bin"/>
 </classpath>
diff --git a/bundles/org.eclipse.test.performance.ui/.project b/bundles/org.eclipse.test.performance.ui/.project
index b608c59..857c94e 100644
--- a/bundles/org.eclipse.test.performance.ui/.project
+++ b/bundles/org.eclipse.test.performance.ui/.project
@@ -1,33 +1,33 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <projectDescription>
-	<name>org.eclipse.test.performance.ui</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.jdt.core.javabuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.pde.ManifestBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.pde.SchemaBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.wst.validation.validationbuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.pde.PluginNature</nature>
-		<nature>org.eclipse.jdt.core.javanature</nature>
-	</natures>
+    <name>org.eclipse.test.performance.ui</name>
+    <comment></comment>
+    <projects>
+    </projects>
+    <buildSpec>
+        <buildCommand>
+            <name>org.eclipse.jdt.core.javabuilder</name>
+            <arguments>
+            </arguments>
+        </buildCommand>
+        <buildCommand>
+            <name>org.eclipse.pde.ManifestBuilder</name>
+            <arguments>
+            </arguments>
+        </buildCommand>
+        <buildCommand>
+            <name>org.eclipse.pde.SchemaBuilder</name>
+            <arguments>
+            </arguments>
+        </buildCommand>
+        <buildCommand>
+            <name>org.eclipse.wst.validation.validationbuilder</name>
+            <arguments>
+            </arguments>
+        </buildCommand>
+    </buildSpec>
+    <natures>
+        <nature>org.eclipse.pde.PluginNature</nature>
+        <nature>org.eclipse.jdt.core.javanature</nature>
+    </natures>
 </projectDescription>
diff --git a/bundles/org.eclipse.test.performance.ui/about.html b/bundles/org.eclipse.test.performance.ui/about.html
index e336131..8caed82 100644
--- a/bundles/org.eclipse.test.performance.ui/about.html
+++ b/bundles/org.eclipse.test.performance.ui/about.html
@@ -8,7 +8,7 @@
 <body lang="EN-US">
 <h2>About This Content</h2>
  
-<p>February 24, 2005</p>	
+<p>February 24, 2005</p>    
 <h3>License</h3>
 
 <p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
diff --git a/bundles/org.eclipse.test.performance.ui/doc/help.html b/bundles/org.eclipse.test.performance.ui/doc/help.html
index 74a75e6..54f914c 100644
--- a/bundles/org.eclipse.test.performance.ui/doc/help.html
+++ b/bundles/org.eclipse.test.performance.ui/doc/help.html
@@ -1,108 +1,173 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">p, table, td, th {  font-family: arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: arial,helvetica,geneva; font-size: 10px}
-h3 {  font-family: arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: arial, helvetica, geneva; font-size: 28px; font-weight: bold}
-body {  font-family: arial, helvetica, geneva; font-size: 10pt; clip:   rect(   ); margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large;; font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small;; font-family: Arial, Helvetica, sans-serif; color: #8080FF}
+<html>
+<head>
+<meta
+  http-equiv="Content-Type"
+  content="text/html; charset=iso-8859-1">
+<style type="text/css">
+p, table, td, th {
+     font-family: arial, helvetica, geneva;
+     font-size: 10pt
+}
+
+pre {
+     font-family: "Courier New", Courier, mono;
+     font-size: 10pt
+}
+
+h2 {
+     font-family: arial, helvetica, geneva;
+     font-size: 18pt;
+     font-weight: bold;
+     line-height: 14px
+}
+
+code {
+     font-family: "Courier New", Courier, mono;
+     font-size: 10pt
+}
+
+sup {
+     font-family: arial, helvetica, geneva;
+     font-size: 10px
+}
+
+h3 {
+     font-family: arial, helvetica, geneva;
+     font-size: 14pt;
+     font-weight: bold
+}
+
+li {
+     font-family: arial, helvetica, geneva;
+     font-size: 10pt
+}
+
+h1 {
+     font-family: arial, helvetica, geneva;
+     font-size: 28px;
+     font-weight: bold
+}
+
+body {
+     font-family: arial, helvetica, geneva;
+     font-size: 10pt;
+     clip: rect();
+     margin-top: 5mm;
+     margin-left: 3mm
+}
+
+.indextop {
+     font-size: x-large;;
+     font-family: Verdana, Arial, Helvetica, sans-serif;
+     font-weight: bold
+}
+
+.indexsub {
+     font-size: xx-small;;
+     font-family: Arial, Helvetica, sans-serif;
+     color: #8080FF
+}
 </style>
 <body>
-<p>
-<h1>Table of contents</h1>
-<ul>
-<li><a href="#scales">Scales</a>
-<ul>
-<li><a href="#percent">Percentage</a></li>
-<li><a href="#time">Time linear</a></li>
-<li><a href="#time">Time logarithmic</a></li>
-</ul>
-</li>
-<li><a href="#tips">Tips for time scales</a></li>
-</ul>
-</p>
-<h1><a name="scales">Scales</h1>
-Since 3.5, it's possible to see results in fingerprints with three different
-kinds of scale.
-<h3><a name="percent">Percentage scale</h3>
-<p>The X axis represents percentage of the variation vs. the given baseline</p>
-<p>This is the way fingerprints were displayed since the beginning:
-<p><img src="images/percentage.png">
-<ul>
-<li>Red bar means a regression, even if it's less than the 10% threshold.</li>
-<li>Green bar means an improvement</li>
-<li>Gray bar means an 'explained' regression.</li>
-</ul>
-</p>
-<h3><a name="time">Linear and logarithmic time scales</h3>
-<p>For these scales, the X axis represents the duration time of the test.<br>
-The colors meanings are the same than for the percentage scale.<br>
-These kind of graphs give a better idea of time duration for each test.</p>
-<p>Typically use linear scale if you want to see the tests relativeness for all the component tests:</p>
-<p><img src="images/linear.png">
-<p>But the logarithmic scale is more appropriate when there are a strong duration differences between tests, hence makes short duration tests easier to survey:</p>
-<p><img src="images/log.png">
-<p>Each test have two bars: the former is white and shows the baseline result, the latter is colored (red, green or gray) and shows the current build result.<br>
-The variation between the baseline and the build is displayed as a percentage on top of both bars.</p>
-<h1><a name="tips">Tips for time scales</h1>
-<p>Tips are almost the same for linear and logarithmic scales:</p>
-<table border="0">
-  <tr>
-    <td valign="top"><img src="../images/light.gif"></td>
-    <td><b>Flying over a bar displays its time value<b>:</td></tr>
-  </tr>
-  <tr>
-    <td></td>
-    <td><img src="images/help_time_baseline.png"></td>
-  </tr>
-  <tr>
-    <td></td>
-    <td><img src="images/help_time_current.png"></td>
-  </tr>
-  <tr><td><br></td></tr>
-  <tr>
-    <td valign="top"><img src="../images/light.gif"></td>
-    <td><b>For <u>linear scale only</u>, when the error on the time result is noticeable,
-		then the measurement uncertainty is shown in yellow at the end of the bar<b>:</td></tr>
-  </tr>
-  <tr>
-    <td></td>
-    <td><img src="images/help_time_error.png"></td>
-  </tr>
-  <tr><td><br></td></tr>
-  <tr>
-    <td valign="top"><img src="../images/light.gif"></td>
-    <td><b>A performance regression may sometimes have a known good reason</b>.<br>
-    In this case, the current build bar is grayed and flying over it also shows the given explanation:</td></tr>
-  </tr>
-  <tr>
-    <td></td>
-    <td><img src="images/help_explained_regression.png"></td>
-  </tr>
-  <tr><td><br></td></tr>
-  <tr>
-    <td valign="top"><img src="../images/light.gif"></td>
-    <td><b>Test result may have big error which can make the test result not fully reliable</b>.<br>
-  In this case, a warning icon is shown after the variation value and flying over it gives the offending error value:</td></tr>
-  </tr>
-  <tr>
-    <td></td>
-    <td><img src="images/help_error_warning.png"></td>
-  </tr>
-  <tr><td><br></td></tr>
-  <tr>
-    <td valign="top"><img src="../images/light.gif"></td>
-    <td><b>Test may have no result for the used baseline, hence the first available build is used as a reference</b>.<br>
-  In this case, a warning icon is shown after the scenario title and flying over it gives the build ID used to compute the variation:</td></tr>
-  </tr>
-  <tr>
-    <td></td>
-    <td><img src="images/help_no_baseline.png"></td>
-  </tr>
-</table>
+
+  <h1>Table of contents</h1>
+  <ul>
+    <li><a href="#scales">Scales</a>
+      <ul>
+        <li><a href="#percent">Percentage</a></li>
+        <li><a href="#time">Time linear</a></li>
+        <li><a href="#time">Time logarithmic</a></li>
+      </ul></li>
+    <li><a href="#tips">Tips for time scales</a></li>
+  </ul>
+  <h1 id="scales">Scales></h1>
+  Since 3.5, it's possible to see results in fingerprints with three different kinds of scale.
+  <h3 id="percent">Percentage scale</h3>
+  <p>The X axis represents percentage of the variation vs. the given baseline</p>
+  <p>
+    This is the way fingerprints were displayed since the beginning: <img src="images/percentage.png">
+  </p>
+  <ul>
+    <li>Red bar means a regression, even if it's less than the 10% threshold.</li>
+    <li>Green bar means an improvement</li>
+    <li>Gray bar means an 'explained' regression.</li>
+  </ul>
+  <h3 id="time">Linear and logarithmic time scales</h3>
+  <p>
+    For these scales, the X axis represents the duration time of the test.<br> The colors meanings are the same than for the percentage scale.<br> These kind of graphs give a better idea of
+    time duration for each test.
+  </p>
+  <p>Typically use linear scale if you want to see the tests relativeness for all the component tests:</p>
+  <p>
+    <img src="images/linear.png">
+  <p>But the logarithmic scale is more appropriate when there are a strong duration differences between tests, hence makes short duration tests easier to survey:</p>
+  <p>
+    <img src="images/log.png">
+  <p>
+    Each test have two bars: the former is white and shows the baseline result, the latter is colored (red, green or gray) and shows the current build result.<br> The variation between the
+    baseline and the build is displayed as a percentage on top of both bars.
+  </p>
+  <h1 id="tips">Tips for time scales</h1>
+  <p>Tips are almost the same for linear and logarithmic scales:</p>
+  <table style="border: 0" >
+    <tr>
+      <td valign="top"><img src="../images/light.gif"></td>
+      <td><b>Flying over a bar displays its time value</b>:</td>
+    </tr>
+    <tr>
+      <td></td>
+      <td><img src="images/help_time_baseline.png"></td>
+    </tr>
+    <tr>
+      <td></td>
+      <td><img src="images/help_time_current.png"></td>
+    </tr>
+    <tr>
+      <td><br></td>
+    </tr>
+    <tr>
+      <td valign="top"><img src="../images/light.gif"></td>
+      <td><b>For linear scale only, when the error on the time result is noticeable, then the measurement uncertainty is shown in yellow at the end of the bar</b>:</td>
+    </tr>
+    <tr>
+      <td></td>
+      <td><img src="images/help_time_error.png"></td>
+    </tr>
+    <tr>
+      <td><br></td>
+    </tr>
+    <tr>
+      <td valign="top"><img src="../images/light.gif"></td>
+      <td><b>A performance regression may sometimes have a known good reason</b>.<br> In this case, the current build bar is grayed and flying over it also shows the given explanation:</td>
+    </tr>
+    <tr>
+      <td></td>
+      <td><img src="images/help_explained_regression.png"></td>
+    </tr>
+    <tr>
+      <td><br></td>
+    </tr>
+    <tr>
+      <td valign="top"><img src="../images/light.gif"></td>
+      <td><b>Test result may have big error which can make the test result not fully reliable</b>.<br> In this case, a warning icon is shown after the variation value and flying over it
+        gives the offending error value:</td>
+    </tr>
+    <tr>
+      <td></td>
+      <td><img src="images/help_error_warning.png"></td>
+    </tr>
+    <tr>
+      <td><br></td>
+    </tr>
+    <tr>
+      <td valign="top"><img src="../images/light.gif"></td>
+      <td><b>Test may have no result for the used baseline, hence the first available build is used as a reference</b>.<br> In this case, a warning icon is shown after the scenario title and
+        flying over it gives the build ID used to compute the variation:</td>
+    </tr>
+    <tr>
+      <td></td>
+      <td><img src="images/help_no_baseline.png"></td>
+    </tr>
+  </table>
 </body>
 </html>
diff --git a/bundles/org.eclipse.test.performance.ui/html/builds-comparison.html b/bundles/org.eclipse.test.performance.ui/html/builds-comparison.html
index 3bded21..68770bd 100644
--- a/bundles/org.eclipse.test.performance.ui/html/builds-comparison.html
+++ b/bundles/org.eclipse.test.performance.ui/html/builds-comparison.html
@@ -2,8 +2,8 @@
 
 <html>
 <head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Builds Comparison view</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+    <title>Builds Comparison view</title>
 </head>
 
 <body>
diff --git a/bundles/org.eclipse.test.performance.ui/html/builds.html b/bundles/org.eclipse.test.performance.ui/html/builds.html
index 8e71a63..d9dc071 100644
--- a/bundles/org.eclipse.test.performance.ui/html/builds.html
+++ b/bundles/org.eclipse.test.performance.ui/html/builds.html
@@ -2,8 +2,8 @@
 
 <html>
 <head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Builds view</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+    <title>Builds view</title>
 </head>
 
 <body>
@@ -32,7 +32,7 @@
 <p><img src="images/builds-nolocaldata.png" alt="Builds view with no local data"/></p>
 </li>
 <li>
-<font color="#888888">gray</font></i>: the local data files were read but contain
+<i><font color="#888888">gray</font></i>: the local data files were read but contain
 no information about this build (typically new performance tests ran but the local
 data files were not copied since then):
 <p><img src="images/builds-missinglocaldata.png" alt="Builds view with missing local data"/></p>
@@ -64,7 +64,7 @@
 eclipsebuildserv or fullmoon...</i>
 </p>
 
-<h2><a name="writecomparison">Write comparison</h2>
+<h2><a name="writecomparison">Write comparison</a></h2>
 <p>
 From this view, it is also possible to write the comparison between two 
 selected builds using the <b>Write comparison</b> item of the View menu:
diff --git a/bundles/org.eclipse.test.performance.ui/html/components.html b/bundles/org.eclipse.test.performance.ui/html/components.html
index 6c9b714..d33ce78 100644
--- a/bundles/org.eclipse.test.performance.ui/html/components.html
+++ b/bundles/org.eclipse.test.performance.ui/html/components.html
@@ -2,8 +2,8 @@
 
 <html>
 <head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Components view</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+    <title>Components view</title>
 </head>
 
 <body>
@@ -48,7 +48,7 @@
 the last build with a failure (i.e. a regression over 10%).
 </p><p>
 The warning icon means that some warnings occur for some results.
-The current possible warning are:
+The current possible warning are:</p>
 <ul>
 <li>error over the 3% threshold on test(s)</li>
 <li>unreliable test(s): the deviation through the test(s) history is over 20%</li>
@@ -56,13 +56,13 @@
 <li>no baseline for test(s)</li>
 <li>only one run on test(s)</li>
 </ul>
-</p><p>
-The information icon gives some other interesting information:
+<p>
+The information icon gives some other interesting information:</p>
 <ul>
 <li>the Student T-test fails on test(s)</li>
 <li>the test(s) value or its delta is less than 100ms</li>
 </ul>
-</p><p>
+<p>
 Note that for component and scenario level, the status is the aggregation of
 the children status. That means that as soon as one scenario is in error then
 the component is also flagged in error. And of course the higher severity is
@@ -86,11 +86,11 @@
 </ul>
 <p>
 As baselines results are not really useful for the survey, the filter is activated
-by default in this view. Currently the survey only concerns the fingerprints
+by default in this view. Currently the survey only concerns the fingerprint
 scenario, hence the corresponding filter is also activated by default.
 </p>
 
-<h2><a name="writestatus">Write status</h2>
+<h2><a name="writestatus">Write status</a></h2>
 <p>
 From this view, it is also possible to write the status file for the last
 active build (see <a href="preferences.html#lastbuild">Last build</a>) by
diff --git a/bundles/org.eclipse.test.performance.ui/html/local_data.html b/bundles/org.eclipse.test.performance.ui/html/local_data.html
index 1d55a69..c2aa4e2 100644
--- a/bundles/org.eclipse.test.performance.ui/html/local_data.html
+++ b/bundles/org.eclipse.test.performance.ui/html/local_data.html
@@ -2,8 +2,8 @@
 
 <html>
 <head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Local data</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+    <title>Local data</title>
 </head>
 
 <body>
@@ -16,26 +16,27 @@
 The performance results tool then can read these files to avoid long distance
 access to data information. Of course, it's first necessary to copy these files
 on a location easily accessible from the machine where the tool is launched.
-</p><p>
-<i>Notes
+</p>
+<div style="font-style: italic;">
+<p>Notes</p>
 <ul>
 <li>these files are accessible for some authorized users onto
 <b>ottcvs1.ottawa.ibm.com</b> at <b>/home/users/ecperf</b> directory</li>
 <li>SFTP is necessary to copy these files from that location</li>
 </ul>
-</i>
-</p><p>
+</div>
+<p>
 To read the local files, select the <b>Local data -> Read...</b> menu item and
 chose the directory where the files have been copied.
-</p><p>
-<i>Notes
+</p>
+<div style="font-style: italic;">
+<p>Notes</p>
 <ul>
 <li>this manual read action only has to be done once, as it will be automatically
 done at the next start of the tool</li>
 <li>no verification is currently done that the local files matches
 the connected DB (if any). Mixing them should give unpredictable results!</li>
 </ul>
-</i>
-</p>
+</div>
 </body>
 </html>
\ No newline at end of file
diff --git a/bundles/org.eclipse.test.performance.ui/html/overview.html b/bundles/org.eclipse.test.performance.ui/html/overview.html
index 5b22fea..17d173a 100644
--- a/bundles/org.eclipse.test.performance.ui/html/overview.html
+++ b/bundles/org.eclipse.test.performance.ui/html/overview.html
@@ -2,8 +2,8 @@
 
 <html>
 <head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Overview</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+    <title>Overview</title>
 </head>
 
 <body>
@@ -13,7 +13,7 @@
 <b>Performance Results</b> perspective:
 <p><img src="images/perspective.png" alt="Performance Results perspective"/></p>
 <p>
-There are 4 views in this perspective:
+There are 4 views in this perspective:</p>
 <ul>
 <li><a href="components.html">Components view</a>: This is the view to see
 the results in details for each components</li>
@@ -24,7 +24,7 @@
 <li><a href="properties.html">Properties view</a>: Display element properties
 (typically results numbers and other database information)</li>
 </ul>
-</p><p>
+<p>
 The goal of this tool is both to look at performance results database numbers
 and to verify whether a build result have scenarios showing performance regression.
 </p><p>
diff --git a/bundles/org.eclipse.test.performance.ui/html/preferences.html b/bundles/org.eclipse.test.performance.ui/html/preferences.html
index 000be5d..41b2643 100644
--- a/bundles/org.eclipse.test.performance.ui/html/preferences.html
+++ b/bundles/org.eclipse.test.performance.ui/html/preferences.html
@@ -2,8 +2,8 @@
 
 <html>
 <head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Preferences</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+    <title>Preferences</title>
 </head>
 
 <body>
@@ -11,17 +11,17 @@
 <p>
 The tool have some preferences which may be configured by advanced users.
 This must be done carefully otherwise, either no data could be read by the tool
-and/or generatead results could be puzzled.
+and/or generated results could be puzzled.
 </p><p>
 
-<h3><a name="eclipse_version">Eclipse version</h3>
+<h3><a name="eclipse_version">Eclipse version</a></h3>
 <p><img src="images/preferences-eclipse-versions.png" alt="Preferences Eclipse versions"/></p>
 <p>
 The Eclipse version on which the performance results belongs to. There are
 only two possible choice: the maintenance and the current versions.
 </p>
 
-<h3><a name="database">Database</h3>
+<h3><a name="database">Database</a></h3>
 <p><img src="images/preferences-database.png" alt="Preferences Database"/></p>
 <p>
 By default the tool does not connect to any performance results database as common
@@ -34,7 +34,7 @@
 <code>perfDb3x</code> folder otherwise you'll get an error message.
 </p>
 
-<h3><a name="status">Status</h3>
+<h3><a name="status">Status</a></h3>
 <p><img src="images/preferences-status.png" alt="Preferences Status"/></p>
 <p>
 The status preferences can be set to exclude some tests while written
@@ -44,6 +44,7 @@
 preference value
 </p><p>
 Here are the detailed explanation of these status preferences:
+</p>
 <ul>
 <li><b>Values</b>: Check-box to include the values of the failing tests in the
 status file. Note that is not recommended to do so when status want to be
@@ -85,9 +86,8 @@
 a test result in the status file...
 </li>
 </ul>
-</p>
 
-<h3><a name="milestones">Milestones</h3>
+<h3><a name="milestones">Milestones</a></h3>
 <p><img src="images/preferences-milestones.png" alt="Preferences Milestones"/></p>
 <p>
 These are the list of the version milestones. Each milestone is a date string
@@ -96,7 +96,7 @@
 list and emphasize it...
 </p>
 
-<h3><a name="lastbuild">Last build</h3>
+<h3><a name="lastbuild">Last build</a></h3>
 <p><img src="images/preferences-lastbuild.png" alt="Preferences Last build"/></p>
 <p>
 The last build on which verifications and/or generation want to be done. When
@@ -108,7 +108,7 @@
 the local data which will be read again.
 </p>
 
-<h2><a name="defaultdim">Default dimension</h2>
+<h2><a name="defaultdim">Default dimension</a></h2>
 <p><img src="images/preferences-default-dim.png" alt="Preferences Default dimension"/></p>
 <p>
 This is the dimension used to compute delta and make the verification. Currently
@@ -119,7 +119,7 @@
 added to the list...</i>
 </p>
 
-<h2><a name="resultsdim">Results dimensions</h2>
+<h2><a name="resultsdim">Results dimensions</a></h2>
 <p><img src="images/preferences-results-dim.png" alt="Preferences Results dimension"/></p>
 <p>
 These are dimensions displayed in the scenario data HTML pages. Currently there
diff --git a/bundles/org.eclipse.test.performance.ui/html/properties.html b/bundles/org.eclipse.test.performance.ui/html/properties.html
index 6470322..c1a5f53 100644
--- a/bundles/org.eclipse.test.performance.ui/html/properties.html
+++ b/bundles/org.eclipse.test.performance.ui/html/properties.html
@@ -2,8 +2,8 @@
 
 <html>
 <head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Properties view</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+    <title>Properties view</title>
 </head>
 
 <body>
@@ -12,9 +12,9 @@
 Properties view contents is different for each select element of the component hierarchy.
 But they all have three sections:
 <ul>
-<li>Results:	Performances results information</li>
-<li>Status:	Various severity messages</li>
-<li>Survey:	Comment added while surveying</li>
+<li>Results:    Performances results information</li>
+<li>Status:    Various severity messages</li>
+<li>Survey:    Comment added while surveying</li>
 </ul>
 <p>
 Note that the status may have multiple warning messages. So, this property is
diff --git a/bundles/org.eclipse.test.performance.ui/html/results.html b/bundles/org.eclipse.test.performance.ui/html/results.html
index fd9e98e..1b5ff50 100644
--- a/bundles/org.eclipse.test.performance.ui/html/results.html
+++ b/bundles/org.eclipse.test.performance.ui/html/results.html
@@ -2,8 +2,8 @@
 
 <html>
 <head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Components Results view</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+    <title>Components Results view</title>
 </head>
 
 <body>
diff --git a/bundles/org.eclipse.test.performance.ui/html/verification.html b/bundles/org.eclipse.test.performance.ui/html/verification.html
index 70f2c0b..ce750b3 100644
--- a/bundles/org.eclipse.test.performance.ui/html/verification.html
+++ b/bundles/org.eclipse.test.performance.ui/html/verification.html
@@ -2,8 +2,8 @@
 
 <html>
 <head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Verification</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+    <title>Verification</title>
 </head>
 
 <body>
@@ -11,9 +11,9 @@
 <p>
 While verifying a build results, the first thing to do is to look for failures.
 The tool helps to know rapidly which components have failure showing a red-cross
-icon in the <a href="components.html">Components view</a>:
+icon in the <a href="components.html">Components view</a>:</p>
 <p><img src="images/verification-components.png" alt="Verification: failing components"/></p>
-</p><p>
+<p>
 When clicking on one of the component having error(s), the tool automatically
 selects the first configuration (i.e. test machine) which has an error in its
 last build results. Then, flying over the failures may give a first indication
diff --git a/bundles/org.eclipse.test.performance.ui/images/descriptions.html b/bundles/org.eclipse.test.performance.ui/images/descriptions.html
index dc9db05..d2fed86 100644
--- a/bundles/org.eclipse.test.performance.ui/images/descriptions.html
+++ b/bundles/org.eclipse.test.performance.ui/images/descriptions.html
@@ -1,9 +1,9 @@
 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 <html>
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Descriptions</title>
-	</head>
+    <head>
+        <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+        <title>Descriptions</title>
+    </head>
 
 <body bgcolor="#FFFFFF" text="#000000">
 <p><a name="fp"></a><font size="+2"><b>Fingerprint Example</b></font></p>
diff --git a/bundles/org.eclipse.test.performance.ui/readme.html b/bundles/org.eclipse.test.performance.ui/readme.html
index 1a2fc86..393e745 100644
--- a/bundles/org.eclipse.test.performance.ui/readme.html
+++ b/bundles/org.eclipse.test.performance.ui/readme.html
@@ -1,9 +1,9 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html lang="en">
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>org.eclipse.test.performance.ui readme</title>
-	</head>
+    <head>
+        <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+        <title>org.eclipse.test.performance.ui readme</title>
+    </head>
 
 <p><b><font size="+2">README</font></b><br> </p><p>Last updated: October 26, 2005<br> 
 </p><p><b>Introduction</b><br> <br> This readme describes how to create performance 
diff --git a/bundles/org.eclipse.test.performance.ui/scripts/Fingerprints.js b/bundles/org.eclipse.test.performance.ui/scripts/Fingerprints.js
index d1914e9..c004d19 100644
--- a/bundles/org.eclipse.test.performance.ui/scripts/Fingerprints.js
+++ b/bundles/org.eclipse.test.performance.ui/scripts/Fingerprints.js
@@ -1,32 +1,32 @@
 function toggleFingerprints() {
-	var formSelect=document.forms[0].elements[0];
-	var type=formSelect.selectedIndex;
-	var idx=document.URL.indexOf("php?");
-	if (idx==-1) {
-		window.open(document.URL+"?fp_type="+type, "_self");
-	} else {
-		window.open(document.URL.substring(0,idx)+"php?fp_type="+type, "_self");
-	}
+    var formSelect=document.forms[0].elements[0];
+    var type=formSelect.selectedIndex;
+    var idx=document.URL.indexOf("php?");
+    if (idx==-1) {
+        window.open(document.URL+"?fp_type="+type, "_self");
+    } else {
+        window.open(document.URL.substring(0,idx)+"php?fp_type="+type, "_self");
+    }
 }
 
 function setFingerprintsType() {
-	var idx=document.URL.indexOf("?");
-	var type=0;
-	if (idx != -1) {
-		var typeStr=document.URL.substring(idx+1, document.URL.length);
-		idx=typeStr.indexOf("=");
-		if (idx != -1) {
-			var ch=typeStr.substring(idx+1, idx+2)
-			switch (ch) {
-				case '1':
-					type=1;
-					break;
-				case '2':
-					type=2;
-					break;
-			}
-		}
-	}
-	var formSelect=document.forms[0].elements[0];
-	formSelect.selectedIndex=type;
+    var idx=document.URL.indexOf("?");
+    var type=0;
+    if (idx != -1) {
+        var typeStr=document.URL.substring(idx+1, document.URL.length);
+        idx=typeStr.indexOf("=");
+        if (idx != -1) {
+            var ch=typeStr.substring(idx+1, idx+2)
+            switch (ch) {
+                case '1':
+                    type=1;
+                    break;
+                case '2':
+                    type=2;
+                    break;
+            }
+        }
+    }
+    var formSelect=document.forms[0].elements[0];
+    formSelect.selectedIndex=type;
 }
diff --git a/bundles/org.eclipse.test.performance.ui/scripts/ToolTip.css b/bundles/org.eclipse.test.performance.ui/scripts/ToolTip.css
index d9114d2..165d564 100644
--- a/bundles/org.eclipse.test.performance.ui/scripts/ToolTip.css
+++ b/bundles/org.eclipse.test.performance.ui/scripts/ToolTip.css
@@ -1,26 +1,26 @@
 
 .hidden_tooltip {
-	display:none;
+    display:none;
 }
 
 span.visible_tooltip {
-	display:block;
-	position:absolute;
-	top:10px;
-	left:21px;
-	width:300px;
-	font-size:9px;;
-	padding-left:5px;
-	padding-right:5px;
-	border:1px solid black;
-	background-color:#FFFFCC;
-	text-decoration:none;
-	color:#000000;
-	z-index:10;
+    display:block;
+    position:absolute;
+    top:10px;
+    left:21px;
+    width:300px;
+    font-size:9px;;
+    padding-left:5px;
+    padding-right:5px;
+    border:1px solid black;
+    background-color:#FFFFCC;
+    text-decoration:none;
+    color:#000000;
+    z-index:10;
 } 
 
 a{  
-	text-decoration:none;
+    text-decoration:none;
 }
 span {
 z-index=100;
@@ -30,5 +30,5 @@
 }
 
 .tooltipSource {
-	position:relative;
+    position:relative;
 }
\ No newline at end of file
diff --git a/bundles/org.eclipse.test.performance.ui/scripts/ToolTip.js b/bundles/org.eclipse.test.performance.ui/scripts/ToolTip.js
index 98008cc..639b9fc 100644
--- a/bundles/org.eclipse.test.performance.ui/scripts/ToolTip.js
+++ b/bundles/org.eclipse.test.performance.ui/scripts/ToolTip.js
@@ -1,23 +1,23 @@
 // General purpose functions. 
 
 function hide_element(elementId) {
-	element = document.getElementById(elementId);
-	if(element != null) {
-		currentClass = element.className;
-		if(currentClass =='visible_tooltip') {
-			element.className = 'hidden_tooltip';
-		}
-	}
+    element = document.getElementById(elementId);
+    if(element != null) {
+        currentClass = element.className;
+        if(currentClass =='visible_tooltip') {
+            element.className = 'hidden_tooltip';
+        }
+    }
 }
 
 function show_element(elementId) {
-	element = document.getElementById(elementId);
-	if(element != null) {
-		currentClass = element.className;
-		if(currentClass == 'hidden_tooltip') {
-			element.className = 'visible_tooltip';
-		}
-	}
+    element = document.getElementById(elementId);
+    if(element != null) {
+        currentClass = element.className;
+        if(currentClass == 'hidden_tooltip') {
+            element.className = 'visible_tooltip';
+        }
+    }
 }
 
 
diff --git a/bundles/org.eclipse.test.performance.ui/toc.xml b/bundles/org.eclipse.test.performance.ui/toc.xml
index 32d0d3f..e6becb2 100644
--- a/bundles/org.eclipse.test.performance.ui/toc.xml
+++ b/bundles/org.eclipse.test.performance.ui/toc.xml
@@ -2,16 +2,16 @@
 <?NLS TYPE="org.eclipse.help.toc"?>
 
 <toc label="Performance Results Guide">
-	<topic label="Overview"  href="html/overview.html"> 
-		<topic label="Preferences" href="html/preferences.html"/> 
-		<topic label="Local data" href="html/local_data.html"/> 
-	</topic>
-	<topic label="Views">
-		<topic label="Components" href="html/components.html"/> 
-		<topic label="Properties" href="html/properties.html"/> 
-		<topic label="Builds" href="html/builds.html"/> 
-		<topic label="Results" href="html/results.html"/>
-		<topic href="html/builds-comparison.html" label="Builds Comparison"/>
-	</topic>
-	<topic label="Verification" href="html/verification.html"/> 
+    <topic label="Overview"  href="html/overview.html"> 
+        <topic label="Preferences" href="html/preferences.html"/> 
+        <topic label="Local data" href="html/local_data.html"/> 
+    </topic>
+    <topic label="Views">
+        <topic label="Components" href="html/components.html"/> 
+        <topic label="Properties" href="html/properties.html"/> 
+        <topic label="Builds" href="html/builds.html"/> 
+        <topic label="Results" href="html/results.html"/>
+        <topic href="html/builds-comparison.html" label="Builds Comparison"/>
+    </topic>
+    <topic label="Verification" href="html/verification.html"/> 
 </toc>