diff --git a/release/1.0.0/sections/description-en.html b/release/1.0.0/sections/description-en.html
index c9ff5ce..f789f36 100644
--- a/release/1.0.0/sections/description-en.html
+++ b/release/1.0.0/sections/description-en.html
@@ -1,13 +1,12 @@
 <h2 id="desc" class="list">The Emission Conversion Factor Ontology: Description <span class="backlink"> back to <a href="#toc">ToC</a></span></h2>
-<span class="markdown">
+<p>
   The next figure shows an overview of the ECFO ontology. ECFO considers Emission Conversion Factors as first class citizens, describing them with rich metadata and provenance.
-
+</p>
   <img src="https://tec-toolkit.github.io/ECFO/release/1.0.0/img/ecfo.png"/>
-
+<p>
   A conversion factor has an emission source (e.g., burning a gaseous fuel like Butane), which is measured with the ecfo:hasSourceUnit property. Similarly, the ecfo:hasEmissionTarget
   describes the chemical compund released by the emission (units are captured with ecfo:hasTargetUnit). Units are represented using the quedt ontology. ECFs also have applicable periods
   (e.g., year 2019), a scope (see scope definitions below) and an applicable location (e.g., the UK). We also annotate ECFs with the dc:publisher responsible for their publication, and
   the source of data used to obtain the value in the KG (prov:wasDerivedFrom). All ECFs have a value, captured through rdf:value. Finally the ecfo:Tags may be associated with categories
   aimed at helping finding the source of an emission factor.
-
-</span>
+</p>