SDS-2024-0141R02-ogc_ipe_communication_schema

Coversheet	Value
Meeting ID	TP#68
Work-item	#WI0100#
Reason	#wording corrections#

TS-0041-oneM2M-SensorThings_interworking.md

@@ -195,7 +195,7 @@ The IPE constructs an "Observation" creation request and copies the 'content' at
 
 **Figure 6.2-1: Communication oneM2M-to-OGC/STA direction** 
 
-Figure 6.2-2 shows the OGC/STA-to-oneM2M direction. The IPE subscribes to the desired "Datastream" of the MQTT-Broker at the OGC/STA server. The OGC/STA server publishes a new "Observation" via the MQTT broker triggert by a OGC/STA sensor. The IPE creates a `<contentInstance>` in a container, to be created as detailed in Section 6.3.2 in the CSE and copies the 'result' attribute of the "Observation" to the 'content' attribute of the `<contentInstance>`. The oneM2M applcation gets the sensor data either by polling the CSE or subscribing to the desired `<container>` at the CSE.
+Figure 6.2-2 shows the OGC/STA-to-oneM2M direction. The IPE subscribes to the desired "Datastream" of the MQTT-Broker at the OGC/STA server. The OGC/STA server publishes a new "Observation" via the MQTT broker triggered by a OGC/STA sensor. The IPE creates a `<contentInstance>` in a container, to be created as detailed in Section 6.3.2 in the CSE and copies the 'result' attribute of the "Observation" to the 'content' attribute of the `<contentInstance>`. The oneM2M applcation gets the sensor data either by polling the CSE or subscribing to the desired `<container>` at the CSE.
 
 ![Figure 6.2-2: Communication OGC/STA-to-oneM2M direction](media/com_flow_2.png)