diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md
index 0e7b94c5da0e6b0d1ff1becb5f0afadae5be8aeb..36958ae83c58d1569b09619492e5720a08e619e4 100644
--- a/TS-0041-oneM2M-SensorThings_interworking.md
+++ b/TS-0041-oneM2M-SensorThings_interworking.md
@@ -55,21 +55,18 @@ References are either specific (identified by date of publication and/or edition
 
 
 ## 2.1 Normative references
-
-
-
  
 - <a name="_ref_1">[1]</a>    OGC SensorThings API "Part 1: Sensing Version 1.1" (http://www.opengis.net/doc/is/sensorthings/1.1)
 - <a name="_ref_2">[2]</a>    oneM2M TS-0033 (V3.0.0): "Interworking Framework"
 - <a name="_ref_3">[3]</a>    oneM2M TS-0001 (V4.23.0): "Functional Architecture"
 
+
 ## 2.2 Informative references
 
 <mark>Clause 2.2 shall only contain informative references which are cited in the document itself.</mark>
 
 The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.
 
-
 - Use the **EX** style, add the letter "i" (for informative) before the number (which shall be in square brackets) and separate this from the title with a tab (you may use sequence fields for automatically numbering references).
 
 - <a name="#_ref_i.1">[i.1]</a>    oneM2M Drafting Rules (http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf)
@@ -151,7 +148,7 @@ The data in the SensorThings server are organized as according to  **Sensing Ent
 
 **Figure 5-2 STA Sensing Entities Data Model** 
 
-In the Sensing Entities Data Model events or sensor data are called "observations". Before a sensor is able to push an "Observation" to the server it needs at least a "Thing" and a "Datastream" entity. This has to be created beforehand. One "Thing" might have different "Sensors", one "Location" or many "HistoricalLocations".
+In the Sensing Entities Data Model events or sensor data are called "Observation". Before a sensor is able to push an "Observation" to the server it needs at least a "Thing" and a "Datastream" entity. This has to be created beforehand. One "Thing" might have different "Sensors", one "Location" or many "HistoricalLocations".
 
 The Sensing Entities data model and the purpose of data within the data model discloses mainly two data characteristics, associated with a "Thing":
 -	Data observations originated by sensors or commands sent to interact with actuators may be seen as IoT data from oneM2M point of view.