From 1ddc0c92951481e16cfc54e1bef6b0deb915ddf2 Mon Sep 17 00:00:00 2001
From: Miguel Angel Reina Ortega <miguelangel.reinaortega@etsi.org>
Date: Wed, 16 Oct 2024 10:45:13 +0000
Subject: [PATCH] Add conflict

---
 ...ct_Test_Suite_&_implementation_eXtra_Information_for_Test.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md b/TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md
index 20897edc..3b1448de 100644
--- a/TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md
+++ b/TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md
@@ -217,7 +217,7 @@ APTs used by the oneM2M test suite are described in figure 5.1-1. The test syste
 **Figure 5.1-1: Abstract protocol testers - oneM2M**
 
 
-As figure 5.1-1 illustrates, the corresponding ATS needs to use lower layers to establish a proper connection to the system under test (SUT) over a physical link (Lower layers link). Four different lower layers have been specified corresponding to the binding protocols considered in oneM2M: HTTP, CoAP, WebSocket and MQTT.
+As figure 5.1-1 illustrates, the corresponding ATS needs to use lower layers to establish a proper connection to the implementation under test (SUT) over a physical link (Lower layers link). Four different lower layers have been specified corresponding to the binding protocols considered in oneM2M: HTTP, CoAP, WebSocket and MQTT.
 
 
 ## 5.2 Test Configuration
-- 
GitLab