Fix xml-lint warning in doc

1 files changed, 24 insertions, 18 deletions

diff --git a/system/doc/efficiency_guide/advanced.xml b/system/doc/efficiency_guide/advanced.xml
index e1760d0ded..896eda5f1c 100644
--- a/system/doc/efficiency_guide/advanced.xml
+++ b/system/doc/efficiency_guide/advanced.xml
@@ -255,30 +255,36 @@
         <cell><marker id="unique_references"/>Unique References on a Runtime System Instance</cell>
         <cell>Each scheduler thread has its own set of references, and all
         other threads have a shared set of references. Each set of references
-        consist of <c>2⁶⁴ - 1</c> unique references. That is the total
+        consist of <c>2⁶⁴ - 1</c> unique references. That is, the total
         amount of unique references that can be produced on a runtime
-        system instance is <c>(NoSchedulers + 1) * (2⁶⁴ - 1)</c>. If a
-        scheduler thread create a new reference each nano second,
+        system instance is <c>(NoSchedulers + 1) × (2⁶⁴ - 1)</c>.
+	<br/><br/>
+	If a scheduler thread create a new reference each nano second,
         references will at earliest be reused after more than 584 years.
 	That is, for the foreseeable future they are unique enough.</cell>
       </row>
       <row>
         <cell><marker id="unique_integers"/>Unique Integers on a Runtime System Instance</cell>
-        <cell>There are two types of unique integers both created using the
-        <seealso marker="erts:erlang#unique_integer/1">erlang:unique_integer()</seealso>
-        BIF. Unique integers created:
-         <taglist>
-	  <tag>with the <c>monotonic</c> modifier</tag>
-	  <item>consist of a set of <c>2⁶⁴ - 1</c> unique integers.</item>
-	  <tag>without the <c>monotonic</c> modifier</tag>
-	  <item>consist of a set of <c>2⁶⁴ - 1</c> unique integers per scheduler
-	  thread and a set of <c>2⁶⁴ - 1</c> unique integers shared by
-	  other threads. That is the total amount of unique integers without
-	  the <c>monotonic</c> modifier is <c>(NoSchedulers + 1) * (2⁶⁴ - 1)</c></item>
-        </taglist>
-      If a unique integer is created each nano second, unique integers
-      will at earliest be reused after more than 584 years. That is, for
-	the foreseeable future they are unique enough.</cell>
+        <cell>
+	    There are two types of unique integers both created using the
+            <seealso marker="erts:erlang#unique_integer/1">erlang:unique_integer()</seealso>
+            BIF:
+	    <br/><br/>
+	    <em>1.</em> Unique integers created <em>with</em> the
+	    <c>monotonic</c> modifier consist of a set of <c>2⁶⁴ - 1</c>
+	    unique integers.
+	    <br/><br/>
+	    <em>2.</em> Unique integers created <em>without</em> the
+	    <c>monotonic</c> modifier consist of a set of <c>2⁶⁴ - 1</c>
+	    unique integers per scheduler thread and a set of <c>2⁶⁴ - 1</c>
+	    unique integers shared by other threads. That is, the total
+	    amount of unique integers without the <c>monotonic</c> modifier
+	    is <c>(NoSchedulers + 1) × (2⁶⁴ - 1)</c>.
+	    <br/><br/>
+	    If a unique integer is created each nano second, unique integers
+	    will at earliest be reused after more than 584 years. That is, for
+	    the foreseeable future they are unique enough.
+	</cell>
       </row>	
       <tcaption>System Limits</tcaption>
     </table>