corrected affiliation

examples/technical_report/Isabelle_DOF-Manual/01_Introduction.thy

@@ -62,20 +62,20 @@ might find complementary information in  @{cite "brucker.wolff19:isadof-design-i
 declare_reference*[bgrnd::text_section]
 declare_reference*[isadof::text_section]
 declare_reference*[casestudies::text_section]
-declare_reference*[ontopide::text_section]
+declare_reference*[latex::text_section]
 declare_reference*[conclusion::text_section]
 (*>*)
 text*[plan::introduction]\<open> The plan of the paper is follows: we start by introducing  the underlying 
 Isabelle system (@{docitem_ref (unchecked) \<open>bgrnd\<close>}) followed guided tour or tutorial
 adressing the needs of the first intended user group. 
-It follows the chapter @{docitem_ref (unchecked) \<open>isadof\<close>} for the second user group 
-with essentials of  \isadof and its ontology language (@{docitem_ref (unchecked) \<open>isadof\<close>}). 
+It follows the chapter @{docitem_ref (unchecked) \<open>isadof\<close>} for the 
+first user group needing a more systematic introduction as well as the
+second user group with essentials of  \isadof and its ontology language 
+(@{docitem_ref (unchecked) \<open>isadof\<close>}). 
 
-XXX
-
-It follows @{docitem_ref (unchecked) \<open>casestudies\<close>}, where we present three application
-scenarios from the point of view of the ontology modeling. In @{docitem_ref (unchecked) \<open>ontopide\<close>}
-we discuss the user-interaction generated from the ontological definitions.  Finally, we draw 
+It follows @{docitem_ref (unchecked) \<open>latex\<close>}, where we necessary bits on the LaTeX
+generation and ways to adapt it to particular purposes.
+ Finally, we draw 
 conclusions  and discuss related work in @{docitem_ref (unchecked) \<open>conclusion\<close>}. \<close>  
 
 (*<*) 

examples/technical_report/Isabelle_DOF-Manual/02_Background.thy

@@ -46,9 +46,9 @@ automated proof procedures as well as specific support for higher specification
 were built. \<close>
 
 
-text\<open> Of particular interest for \dof is documentation generation of the architecture,
-which is based on literate specification commands such as \inlineisar+section+ \ldots, 
-\inlineisar+subsection+ \ldots, \inlineisar+text+ \ldots, etc. Moreover, we assume that
+text\<open> Of particular interest for \dof is the  documentation generation component in 
+the architecture, which is based on literate specification commands such as \inlineisar+section+ 
+\ldots, \inlineisar+subsection+ \ldots, \inlineisar+text+ \ldots, etc. Moreover, we assume that
 \<^emph>\<open>inside\<close> text-elements, there are generic and extendible ways to add "semantic", i.e.
 machine-checked sub-elements.
 

examples/technical_report/Isabelle_DOF-Manual/document/preamble.tex

@@ -97,7 +97,7 @@
 
 \uppertitleback{
 Copyright \copyright{} 2018--2019 The University of Sheffield, UK\\
-Copyright \copyright{} 2018--2019 Universit\'e Paris-Sud, France\\
+Copyright \copyright{} 2018--2019 Universit\'e Paris-Saclay, France\\
 Copyright \copyright{} 2019\phantom{--2019} University of Exeter, UK\\
 All rights reserved.
 
@@ -127,7 +127,7 @@ SPDX-License-Identifier: BSD-2-Clause
 }
 
 \lowertitleback{\textbf{Note:}\\
-  This manual describes \isadof version XXX. 
+  This manual describes \isadof version 1.0/2019. 
 }
 
 
@@ -150,7 +150,7 @@ SPDX-License-Identifier: BSD-2-Clause
 &
   Laboratoire en Recherche\newline
   ~~~~en Informatique (LRI)\newline
-  Universit\'e Paris-Sud 11\newline
+  Universit\'e Paris-Saclay\newline
   91405 Orsay Cedex\newline
   France
 \end{tabular}