Editorial revisions

karthikeyad-pnnl · Mar 26, 2020 · 4dd58b5 · 4dd58b5
1 parent 114ebc3
commit 4dd58b5
Show file tree

Hide file tree

Showing 4 changed files with 11 additions and 6 deletions.
diff --git a/specification/source/codeGeneration.rst b/specification/source/codeGeneration.rst
@@ -6,8 +6,8 @@ Code Generation
 Introduction
 ^^^^^^^^^^^^
 
-This section describes the translation
-from CDL to a building automation system.
+This section describes the translation of control sequences expressed
+in CDL to a building automation system.
 
 Translating the *CDL library* to a building automation system to make it
 available as part of a product line needs to be done only when
@@ -16,7 +16,7 @@ to perform this step.
 However, translation of a *CDL-conforming control sequence* that has been developed
 for a specific building will need to be done for each building project.
 
-While translation from CDL to C code or to a Functional Mockup Unit is
+While translation from CDL to C code or to a :term:`Functional Mockup Unit` is
 support by Modelica simulation environments, translation to
 legacy building automation product lines is more difficult
 as they typically do not allow executing custom C code. Moreover,
@@ -30,7 +30,7 @@ in a verification test module, consists of the following steps:
 
 1. Implementation of the control sequence using CDL.
 
-2. Export of the Modelica model as a :term:`Functional Mockup Unit` for Model Exchange (FMU-ME)
+2. Export of the Modelica model as a Functional Mockup Unit for Model Exchange (FMU-ME)
    or as a JSON specification.
 
 3. Import of the FMU-ME in the runtime environment, or translation of the

diff --git a/specification/source/example.rst b/specification/source/example.rst
@@ -3,6 +3,9 @@
 Example Application
 -------------------
 
+Introduction
+^^^^^^^^^^^^
+
 In this section, we compare the performance of two different
 control sequences, applied to a floor of a prototypical office building.
 The objectives are

diff --git a/specification/source/preample.rst b/specification/source/preample.rst
@@ -16,5 +16,4 @@ use cases and requirements, as well as a case study that illustrates the use of
 performance comparison of a control sequence during design.
 
 The document is a working document that is used as a discussion basis
-and will evolve as the development progresses. The proposed design
-should not be considered finalized.
+and will evolve as the development progresses.
diff --git a/specification/source/verification.rst b/specification/source/verification.rst
@@ -3,6 +3,9 @@
 Verification
 ------------
 
+Introduction
+^^^^^^^^^^^^
+
 This section describes how to formally verify whether
 the control sequence is implemented according to specification.
 This process would be done as part