From 83610c201813ff2c402ac4ef5e69bf08503b93c5 Mon Sep 17 00:00:00 2001
From: Roland Hechwartner <roland.hechwartner@magenta.at>
Date: Wed, 2 Apr 2025 08:51:29 +0000
Subject: [PATCH] editorial changes

---
 TS-0011-Common_Terminology.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/TS-0011-Common_Terminology.md b/TS-0011-Common_Terminology.md
index 7260845..d6c7c89 100644
--- a/TS-0011-Common_Terminology.md
+++ b/TS-0011-Common_Terminology.md
@@ -299,7 +299,7 @@ Void.
 
 **Implementation:** the instantiation of devices, gateways, platforms, cloud servers, modules, software packages, development kits or all other kinds of entities developed to comply to oneM2M specification
 
-**Indirect Dynamic Authorization: **procedure in which an Originator obtains Dynamic Authorization from a Dynamic Authorization System Server, and provides the Hosting CSE with a Token or Token-ID representing that Dynamic Authorization
+**Indirect Dynamic Authorization:** procedure in which an Originator obtains Dynamic Authorization from a Dynamic Authorization System Server, and provides the Hosting CSE with a Token or Token-ID representing that Dynamic Authorization
 
 **Information:** in the context of oneM2M "Information"signifies data that can be interpreted by the oneM2M System
 
@@ -315,7 +315,7 @@ Void.
 
 `EXAMPLE:    Physical mapping: an Infrastructure Node could reside in an M2M Service Infrastructure.`  
 
-**Inner Primitive: **oneM2M Primitive being secured by End-to-End Security for Primitives
+**Inner Primitive:** oneM2M Primitive being secured by End-to-End Security for Primitives
 
 **Integrity [i.3], [i.4]:** safeguarding the accuracy and completeness of information and processing methods
 
-- 
GitLab