correction of 6.3.1.2

TS-0041-oneM2M-SensorThings_interworking.md

@@ -215,12 +215,12 @@ An "Observation" according to STA Sensing Entities Data Model <a href="#_ref_i.1
 
 #### 6.3.1.2 Communication direction IPE towards OGC/STA Server
 
-The IPE requires a destination-"Datastream" in order to send an "Observation". If no associated "Datastream" exists on the OGC/STA server, it shall be created. This can be done beforehand or at the IPE's start-up time and is up to the implementation.
-When a "Datastream" is created on the OGC/STA server, a reference ID (e.g. {"@iot.id:3635353"}) is returned. This reference is needed by the IPE to relate an "Observation" to a "Datastream" and shall be available during IPE operation. Apart from the "Datastream," additional entities of the OGC data model, such as "Location" or "Sensor," may be created. 
+The IPE requires a destination-"Datastream" to send an "Observation" containing data from the oneM2M side. If no associated "Datastream" exists on the OGC/STA server, it shall be created. This can be done beforehand or at the IPE's start-up, depending on the implementation.
+When a "Datastream" is created on the OGC/STA server, a reference ID (e.g. {"@iot.id:3635353"}) is returned. This reference is required by the IPE to associate an "Observation" with a "Datastream" and shall be available during IPE operation. In addition to the "Datastream" other entities of the STA Sensing Entities Data Model <a href="#_ref_i.1">[i.1]</a>, such as "Location" or "Sensor," may be created. 
 
-The creation of entities like "Datastream" and "Thing" requires several mandatory properties that shall be known at configuration time (e.g., 'name' and 'description'). These property fields may automatically derived e.g. from the "Label" or "ResourceName" attributes of the regarded oneM2M `<AE>` or `<container>` during IPE configuration. The OGC/STA procedures for creating OGC entities are described in SensorThing API documentation <a href="#_ref_i.1">[i.1]</a>.
+The creation of entities like "Datastream" and "Thing" requires several mandatory properties that shall be known at configuration time (e.g., 'name' and 'description'). These property fields may automatically derived, for example, from the "Label" or "ResourceName" attributes of the corresponding oneM2M `<container>` or if existing, from the `<AE>` during IPE configuration. The OGC/STA procedures for creating OGC entities are described in SensorThing API documentation <a href="#_ref_i.1">[i.1]</a>.
 
-Once the "Thing" and "Datastream" entities are created, the IPE can send "Observations" to the OGC/STA server as HTTP POST messages. The interested OGC/STA client can then subscribe to the destination "Datastream" at the MQTT Broker of the OGC/STA server and receive every "Observation" forwarded from the IPE (see Figure 6.3.1.2-1). Alternatively, the OGC/STA client may use an HTTP-GET request to pull the data as needed.
+Once the "Thing" and "Datastream" entities are created, the IPE can send "Observations" to the OGC/STA server as HTTP POST messages. An interested OGC/STA client can subscribe to the destination "Datastream" at the MQTT Broker of the OGC/STA server to receive each "Observation" forwarded by the IPE (see Figure 6.3.1.2-1). Alternatively, the OGC/STA client may use an HTTP-GET request to retrieve the data as needed.
 
 ![Figure 6.3.1.2-1: Message flow from IPE to OGC/STA Server to OGC/STA Client](media/config_ogc2.png)