Fix language issues in data and packaging layer

Signed-off-by: Pierre R. Mai <pmai@pmsf.de>

Author: pmai

doc/architecture/data_layer.adoc

@@ -3,9 +3,9 @@
 The data layer of OSI resides in the message specifications given using the ProtoBuf IDL.
 It defines the data that can be transmitted using OSI, including the structure and semantics of the data.
 
-As a second part it also specifies the encoding(s) to be used when transmitting OSI data.
-Currently this is the ProtoBuf encoding, but other encodings can be supported from the same IDL, with FlatBuffer encoding a currently experimental feature.
+Additionally, it also specifies the encoding(s) to be used when transmitting OSI data.
+Currently, this is the ProtoBuf encoding, but other encodings can be supported from the same IDL, with FlatBuffer encoding a currently experimental feature.
 
-The data layer does not directly define components and transmission routes, which are relegated to the packaging layer of OSI.
-There can be many packaging layer implementations using the common data layer definitions.
-This also enables easy bridging of information between components using different packaging layer implementations, since the data being exchanged remains compatible.
+The data layer does not directly define components and transmission routes, which are defined in the packaging layer of OSI.
+There can be many packaging layer implementations using the shared data layer definitions.
+The flexibility this gives enables easy bridging of information between components using different packaging layer implementations since the data that is exchanged remains compatible.

doc/architecture/packaging_layer.adoc

@@ -1,10 +1,10 @@
 = Packaging layer
 
-The packaging layer of OSI specifies the way that components (e.g. models) employing the OSI data layer can be packaged in order to achieve easy interoperability.
+The packaging layer of OSI specifies how components (like sensor models) using the OSI data layer are packaged for exchange.
 
-It specifies model types (e.g. sensor model, traffic participant model), together with mandatory and optional OSI inputs, outputs, parameter interfaces.
-It also specifies specific component technology standards to allow encapsulation of those model types in easily exchangeable component packages, that allow use across platforms and implementations.
+It specifies model types (like sensor model, traffic participant model) and their mandatory and optional OSI inputs, outputs, and parameter interfaces.
+It also specifies specific component technology standards to allow encapsulation of those model types in easily exchangeable component packages that enable use across platforms and implementations.
 
-Multiple packaging layer implementations are possible within the OSI framework, with the common data layer ensuring ease of bridging between multiple implementations.
+Multiple packaging layer implementations are possible within the OSI framework, with the shared data layer ensuring ease of bridging between different implementations.
 The current centrally defined packaging layer is the OSI Sensor Model Packaging (OSMP) specification.
 It is defined based on FMI 2.0 and certain additional conventions to allow packaging of OSI using models as FMUs.