SDS-2025-0016R02-ogc_ipe_configuration_aspects

Coversheet	Value
Meeting ID	TP#68
Work-item	WI-0100
Reason	rewordings & more precise descriptions

TS-0041-oneM2M-SensorThings_interworking.md

@@ -204,7 +204,7 @@ Both directions of the data flow between the OGC/STA server and the IPE require
 
 #### 6.3.1.1 Communication direction OGC/STA Server towards IPE
 
-In Figure 6.3.1.1-1, an OGC/STA client is connected to an OGC/STA server, and its data is forwarded to the IPE. he OGC/STA client publishes data to the OGC/STA server via an HTTP-POST message. The 'result' attribute of an "Observation" contains the sensor data.
+In Figure 6.3.1.1-1, an OGC/STA client is connected to an OGC/STA server, and its data is forwarded to the IPE. The OGC/STA client publishes data to the OGC/STA server via an HTTP-POST message. The 'result' attribute of an "Observation" contains the sensor data.
 An "Observation" according to STA Sensing Entities Data Model <a href="#_ref_i.1">[i.1]</a> belongs to a "Datastream" (see Figure 5-2). 
 
 The IPE shall subscribe to the relevant "Datastream" at the MQTT-Broker of the OGC/STA Server using its specific URL or topic like e.g. {"sta-example-server-address.com/v1.0/Datastreams(8715)"}. After subscribing, the IPE receives every "Observation" that is pushed to that "Datastream".