diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md
index b41286a3901d3b7689d5199223477593c0703f06..40efddc6ff45bf7294551ced23147278ea5bdbd1 100644
--- a/TS-0041-oneM2M-SensorThings_interworking.md
+++ b/TS-0041-oneM2M-SensorThings_interworking.md
@@ -180,7 +180,7 @@ According to oneM2M TS-0033 <a href="#_ref_2">[2]</a> a representation of a non-
 - sensor (IoT-data); and 
 - administrative data (like historic locations or historic products IDs).
 
-The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'content' attribute of a oneM2M `<contentInstance>`;, and vice versa as shown in Figure 6.1-1. The data type of the 'result' field of an "Observation" is acording to SensorThings API <a href="#_ref_i.1">[i.1]</a> 'any' and depends on the 'observationType' defined in the associated "Datastream". The 'content' attribute of an oneM2M instance may be opaque data <a href="#_ref_3">[3]</a> understandable with the help of the 'contentInfo' attribute. The 'contentInfo' attribute on the oneM2M side may be added by the IPE. The original timestamps, present in the "Observation" as 'phenomenonTime' and in the &lt;contentInstance&gt; as "creationTime," shall be discarded. These timestamps are to be reset by the OGC /STA server and the CSE, respectively. They may be transmitted for informational purposes as part of the 'result' or the 'content' fields.
+The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'content' attribute of a oneM2M `<contentInstan2ce>`;, and vice versa as shown in Figure 6.1-1. The data type of the 'result' field of an "Observation" is acording to SensorThings API <a href="#_ref_i.1">[i.1]</a> 'any' and depends on the 'observationType' defined in the associated "Datastream". The 'content' attribute of an oneM2M instance may be opaque data <a href="#_ref_3">[3]</a> understandable with the help of the 'contentInfo' attribute. The 'contentInfo' attribute on the oneM2M side may be added by the IPE. The original timestamps, present in the "Observation" as 'phenomenonTime' and in the &lt;contentInstance&gt; as "creationTime," shall be discarded. These timestamps are to be reset by the OGC /STA server and the CSE, respectively. They may be transmitted for informational purposes as part of the 'result' or the 'content' fields.
 
 ![Figure 6.1-1: OGC / STA-to-oneM2M data model mapping](media/data_mapping.svg)