Some more editorials

TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md

@@ -132,7 +132,7 @@ For the purposes of the present document, the following abbreviations apply:
 
 
 `AE    Application Entity`  
-`APT    Abstract Protocol Tester`
+`APT    Abstract Protocol Tester`  
 `ASP    Abstract Service Primitives`  
 `ATM    Abstract Test Method`  
 `ATS    Abstract Test Suite`  
@@ -142,9 +142,9 @@ For the purposes of the present document, the following abbreviations apply:
 `IP    Internet Protocol`  
 `IUT    Implementation Under Test`  
 `IXIT    Implementation eXtra Information for Test`  
-`JSON    JavaScript Object Notation`
-`M2M     Machine to machine`
-`MN     Middle Node`
+`JSON    JavaScript Object Notation`  
+`M2M     Machine to machine`  
+`MN     Middle Node`  
 `MQTT    Message Queuing Telemetry Transport`  
 `MTC    Main Test Component`  
 `PA    Platform Adaptor`  
@@ -206,10 +206,11 @@ Following this recommendation the oneM2M tester architecture comprises a non-pla
 
 
 ![Figure 5.3-1: High level oneM2M Test Architecture](media/image7.png)
-> NOTE:    However, it can be implemented in a semi-independent manner, which will minimize the dependency to those elements.
 
 **Figure 5.3-1: High level oneM2M Test Architecture**
 
+> NOTE:    However, it can be implemented in a semi-independent manner, which will minimize the dependency to those elements.
+
 
 - **oneM2M** **TTCN** **-3** **Abstract** **Test Suite:**  the test suite is platform independent, and it is the cornerstone of the architecture. It allows a complete decoupling between the test suite and the rest of the test system. The test suite is composed of a complete set of test cases covering oneM2M requirements specified by oneM2M TS0001 <a href="#_ref_1">[1]</a> and oneM2M TS-0004 <a href="#_ref_2">[2]</a>.
 - **oneM2M System Adaptor** **:**  this is the platform dependent part that includes adaptors and codecs (out of the scope of the present document). This part of the architecture definition depends on the specific platform (e.g. Windows&reg; or Linux&reg;) and test tool on which the tester is going to run.
@@ -484,6 +485,7 @@ Table 5.4.4.2.2-1 defines UtTrigger and UtTriggerAck primitives including oneM2M
 
 
 
+
 The rules for defining UtTrigger and UtTriggerAck primitives are:
 
 1. UtTrigger primitive is represented in requestPrimitive serialized in JSON format. 
@@ -939,7 +941,7 @@ This test suite has been compiled error-free using two different commercial TTCN
 
 The TTCN-3 library modules, which form parts of the present document, are contained in the following gitLab tag:
 
-[https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v3\_5\_1](https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v3\_5\_1) <br />
+[https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v3\_5\_2](https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v3\_5\_2) <br />
 
 
 # Annex B (informative): Bibliography