diff --git a/documentation/trunk/eiffelstudio/Tutorials/computing-project-metrics.wiki b/documentation/trunk/eiffelstudio/Tutorials/computing-project-metrics.wiki
index 2d7bfa56..5cb20342 100644
--- a/documentation/trunk/eiffelstudio/Tutorials/computing-project-metrics.wiki
+++ b/documentation/trunk/eiffelstudio/Tutorials/computing-project-metrics.wiki
@@ -6,7 +6,7 @@ In earlier sections we saw how EiffelStudio provides extensive documentation on
 * Define new metrics, through mathematical formulae or boolean selection, and apply them to your project.
 * Store measurement results, as well as metric definitions, into an XML archive that can be stored locally or made available on the Web for future reference.
 * Compare the measurements on a system to those on record locally or on a Web site. Eiffel Software has released on its own site an archive recording the metric properties of its basic libraries, available to any other project for comparison.
-<div> 
+
 ==Methodological observations==
 
 Although the field of software metrics is a rich one with an abundant literature, its methodological basis is sometimes subject to question. One should resist the tendency to believe numbers just because they are numbers ("lies, damn lies, and metrics").
@@ -14,7 +14,7 @@ Although the field of software metrics is a rich one with an abundant literature
 Software engineers and their managers expect, however, to reap at least some of the benefits that precise quantification has brought to other engineering fields. Such is the purpose of software metrics, defined as '''quantitative estimates of product and project properties'''. Object-oriented development, with the rich software structures that it induces, is a particularly amenable to metric analysis. Even when some of the measures do not seem to bring much by themselves, comparing them to those of other projects may reveal significant peculiarities of a system or of some of its parts. 
 
 The metrics capabilities of EiffelStudio were designed with these observations in mind. They result from a conservative approach, where no metric is provided without a credible assumption that it reflects some meaningful project or product attribute. For example, you will find a way to define a new metric as a <span>linear combination</span> of existing ones, but not a way to compute arbitrary arithmetic operations, since it isn't clear that -- say -- <span>multiplying</span> two metrics ever makes sense. 
-</div><div> 
+
 ==Metric terminology==
 
 The following terms are used in the presentation of EiffelStudio metric mechanisms.
@@ -32,7 +32,7 @@ The numbers yielded by measures are meaningless unless we describe what they ref
 EiffelStudio provides a set of predefined units. Some simply serve to count occurrences of certain construct specimens in the software; examples include <code>group</code>, <code lang=text>class</code>, <code lang=text>feature</code>, <code>line</code>, <span>...</span> The metric <code>ratio</code> describes metrics whose values are divisions, for example "average number of classes per cluster", obtained by dividing the number of classes by the number of classes. 
 
 A metric can be computed over a scope. This scope is defined using a '''domain'''. A domain is a set of program elements. You build up a domain by adding development objects to a list. These development objects are things like application targets, clusters, libraries, classes, and features.  
-</div>
+
 
 ==Metric tool interface==