6.3.2.2

TS-0041-oneM2M-SensorThings_interworking.md

@@ -194,7 +194,7 @@ The IPE needs to perform configuration steps on the hosting CSE.
 
 #### 6.3.2.1 Communication direction oneM2M CSE towards IPE
 
-In Figure 6.3.2.1-1 a oneM2M AE, triggert by a sensor, sends data to the CSE by creating a `<contentInstance>` in a `<container>` at the CSE. 
+In Figure 6.3.2.1-1 a oneM2M AE, triggered by a sensor, sends data to the CSE by creating a `<contentInstance>` in a `<container>` at the CSE. 
 The IPE subscribes to the `<container>`by creating a `<subscription>` and receives a `<notification>` message along with the `<contentInstance>` when new data arrives.
 
 ![Figure 6.3.2.1-1: Message flow from AE to CSE to IPE](media/config_cse1.png)
@@ -227,8 +227,8 @@ If the `<container>` does not exist, and if necessary, a related `<AE>` shall be
 **Figure 6.3.2.2-2: Configuration message flow for IPE to CSE direction** 
 
 The detailed configuration steps are shown in Figure 6.3.2.2-2:
-1)	The IPE requests to create an `<AE>` resource on the hosting CSE.
-2)	The hosting CSE evaluates the request, performs the appropriate checks, and creates the `<AE>` resource.
+1)	The IPE requests to register an `<AE>` resource on the hosting CSE.
+2)	The hosting CSE evaluates the request, performs the appropriate checks, and registers the `<AE>` resource.
 3)	The hosting CSE responds with a successful result message upon successful creation of the `<AE>` resource; otherwise, it responds with an error.
 4)	The IPE requests to create a `<container>` under the `<AE>`.
 5)	The hosting CSE evaluates the requests, performs the appropriate checks, and creates the `<container>` resource.