Update TR-0073-Developer_Guide_Deploying_Semantics.md

TR-0073-Developer_Guide_Deploying_Semantics.md

@@ -178,31 +178,24 @@ The messages shown in Figure 4 are further described here:
 - **Generate notification** for clothes washing machine. When the client application sends a oneM2M primitive to a resource that controls the clothes washing machine, a notification is generated (assuming notifications were created). In our scenario, since the clothes washing machine and the IPE are behind a firewall and therefore not reachable, the notification for the IPE are stored in the CSE and made available to the IPE via the long polling process.
 - **Poll for notifications**. Because the IPE cannot receive notifications directly, it must use the long polling procedure to retrieve its notifications from the CSE. The IPE processes notifications by sending commands to the clothes washing machine using the API of the clothes washing machine.
 
-## Custom Model
+## Device models using a Custom Model
 
 Using oneM2M to represent devices allows for unlimited flexibility. A device model can be customized to support the needs of the manufacturer or system architecture. The resource tree structure shown here represents a custom model that has a single container for reading the status of the washing machine and a separate container to set or command the washing machine.
 
 <p align="center">
-    <strong>Figure 4: TEXT</strong>
+    <strong>Figure 4: Custom washing machine model</strong>
     <br>
     <img src="media/image6.png" alt="__CAPTION__">
 </p>
 
 
 <p align="center">
-    <strong>Figure 5: Custom washing machine model</strong>
+    <strong>Figure 5: Custom Model oneM2M Call Flows</strong>
     <br>
     <img src="media/image7.png" alt="Custom washing machine model">
 </p>
 
 
-<p align="center">
-    <strong>Figure 6: Custom Model oneM2M Call Flows</strong>
-    <br>
-    <img src="media/image8.png" alt="__CAPTION__">
-</p>
-
-
 
 Only the messages highlighted in light blue are described here as the rest of the messages are the same as in the general call flow described in clause 6.1.
 
@@ -231,7 +224,7 @@ Only the messages highlighted in light blue are described here as the rest of th
 
 
 
-## Semantic Modelling
+## Device models using Semantic Modelling
 A SAREF description of the washing machine is mapped to the resource structure shown in Figure 6 using the rules described in TS-0030 and TS-0012. A complete derivation of this example is shown in [ref to TS-0012] Annex B.1.3.3.
 
 The description of our (simplified) washing machine using SAREF ontology is expanded upon here:
@@ -286,7 +279,7 @@ sn:WASH_XYZ-StartStopFunction                 a       saref:ActuatingFunction ;
 
 
 <p align="center">
-    <strong>Figure 7: SAREF Washing Machine Model</strong>
+    <strong>Figure 6: SAREF Washing Machine Model</strong>
     <br>
     <img src="media/image8.png" alt="__CAPTION__">
 </p>
@@ -340,7 +333,7 @@ TS-0023 defines a framework for developing common standardized models of devices
 
 
 <p align="center">
-    <strong>Figure 9: SDT washing machine model</strong>
+    <strong>Figure 7: SDT washing machine model</strong>
     <br>
     <img src="media/image10.png" alt="__CAPTION__">
 </p>