Index: DamOverall/trunk/doc/DAM - Architecture Overall/DAM - Architecture Overall.tex
===================================================================
diff -u -r2589 -r2669
--- DamOverall/trunk/doc/DAM - Architecture Overall/DAM - Architecture Overall.tex	(.../DAM - Architecture Overall.tex)	(revision 2589)
+++ DamOverall/trunk/doc/DAM - Architecture Overall/DAM - Architecture Overall.tex	(.../DAM - Architecture Overall.tex)	(revision 2669)
@@ -373,8 +373,8 @@
 	\item Deltares.DamEngine.Io: this map contains classes performing Input/Output to and from the engine.
 	\item Deltares.DamEngine.Version: this map contains a class to configure the version number for all classes.
 \end{itemize}
-Each project will have a corresponding test 0y99o9ogh==igiii99i9ki9999999999og9iioiiioiiiii=ction{\ProgramName repository Failure Mechanisms} \label{sec:RepositoryDamFailureMechanisms}
-
+Each project will have a corresponding test project.
+\section{\ProgramName repository Failure Mechanisms} \label{sec:RepositoryDamFailureMechanisms}
 The original \ProgramName implementation had its own failure mechanisms implemented. In the current architecture, the failure mechanisms are not part of the \ProgramName engine itself. They will be implemented as independent kernels. 
 In \autoref{fig-SVNDamEngineLayout} the layout of the \ProgramName Failure Mechanisms map is shown.
 
@@ -417,8 +417,10 @@
 \chapter{Releasing a product}  \label{ProductRelease}
 
 This is a description of the steps needed to create a \ProgramName release. An external release is normally a release of a \ProgramName client (\ProgramName UI or \ProgramName Live).
-The order of releasing the several modules of the \ProgramName system is important because of the dependencies between the several modules. So keep the order of releasing as is specified in this chapter. \newline
-It is not always necessary to release all modules, but a module needs to be released, when a dependent module has been released. 
+The order of releasing the several modules of the \ProgramName system is important because of the dependencies between the several modules. So keep the order of releasing as specified in this chapter. \newline
+It is not always necessary to release all modules, but a module needs to be released, when a dependent module has been released.  \newline
+\Note{In the following description only the dependencies of the modules belonging to this project are listed. Each module can have dependencies to other external libraries. You should check if these external libraries are still up-to-date. } \newline
+\Note{Special attention should be paid to the DSL (Delta Shell Light) library. This library is also a Deltares product and has its own release document.}
 \section{Dam Failure Mechanisms} \label{ReleaseDamFailureMechanisms}
 This chapter describes the failure mechanisms which are specifically developed for Dam.
 \subsection{DamMacroStability} \label{ReleaseDamMacroStability}
