Order of implementation changed

6-2-multidevice_build_structure.tex → 6-1-multidevice_build_structure.tex

@@ -4,7 +4,7 @@
 
 \subsubsection{Framework integration}
 
-The framework has been changed to keep control over the application life-cycle.
+The framework is build to keep control over the application life-cycle.
 It ensures that the device unspecific code is executed at the right time and provides an API for device specific functionality.
 
 The framework specifies a simple interface, which must be implemented by each device.

6-implementation.tex

@@ -2,11 +2,10 @@
 
 Implementing \textit{OTA} updates under the given requirements involves three different components, which interact closely.
 
-The first component implements the update mechanism in the firmware running on the embedded device.
-It is responsible for checking and downloading the updates and installing them.
-Second, the build system is in charge of building the firmware from source and publishing the built binary images.
-Finally, the deployment provides infrastructure for downloading the binary firmware images and triggering the update on all devices.
+The first component is the build system which is in charge of building the firmware from source and publishing the built binary images.
+Second, the deployment provides infrastructure for downloading the binary firmware images and triggering the update on all devices.
+Finally, the implementation of the update mechanism as part of the firmware running on the embedded device which is responsible for downloading and checking the updates and installing them.
 
-\input{6-1-update_mechanism}
-\input{6-2-multidevice_build_structure}
-\input{6-3-automatic-deployment}
+\input{6-1-multidevice_build_structure}
+\input{6-2-automatic-deployment}
+\input{6-3-update_mechanism}