Revised 3.5

report.lyx

@@ -5846,24 +5846,12 @@ Techniques for ensuring reliability
 
 \begin_layout Standard
 One of the main goals of the project is to achieve high reliability.
- The term 
-\begin_inset Quotes eld
-\end_inset
-
-reliable system
-\begin_inset Quotes erd
-\end_inset
-
- is defined by the IEEE as a system with 
-\begin_inset Quotes eld
-\end_inset
-
-the ability of a system or component to perform its required functions under
- stated conditions for a specified period of time
-\begin_inset Quotes erd
-\end_inset
-
+ The term 'reliable system' is defined by the IEEE as 
+\end_layout
 
+\begin_layout Quotation
+A system with the ability of a system or component to perform its required
+ functions under stated conditions for a specified period of time 
 \begin_inset CommandInset citation
 LatexCommand citet
 key "ieee_90"
@@ -5871,10 +5859,13 @@ key "ieee_90"
 \end_inset
 
 .
- There are some tools for creating reliable applications built in to Erlang.
+\end_layout
+
+\begin_layout Standard
+There are some tools for creating reliable applications built in to Erlang:
  
 \begin_inset ERT
-status open
+status collapsed
 
 \begin_layout Plain Layout
 
@@ -5902,14 +5893,22 @@ E"}
 \end_layout
 
 \begin_layout Itemize
-Links between processes.
+
+\series bold
+Links between processes
+\series default
+.
  When a process spawns a new child process, and the child process later
  exits, the parent process is notified of the exit.
  
 \end_layout
 
 \begin_layout Itemize
-Transparent distribution over a network of processors.
+
+\series bold
+Transparent distribution over a network of processors
+\series default
+.
  When several nodes participate in a network, it does not matter on which
  of these machines a process is run.
  Communication between processes does not depend on the node in which each
@@ -5918,7 +5917,11 @@ Transparent distribution over a network of processors.
 \end_layout
 
 \begin_layout Itemize
-Hot code replacements.
+
+\series bold
+Hot code replacements
+\series default
+.
  Two versions of the same module can reside in the memory of Erlang at any
  time.
  This means that a simple swap between these versions can take place very