From 633d073fab66f71bf5ca92e31cb1b87a6506e2b7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
 <67875049+akoshunyadi@users.noreply.github.com>
Date: Wed, 30 Oct 2024 22:35:38 +0100
Subject: [PATCH] Update device-reachability-status.yaml

---
 code/API_definitions/device-reachability-status.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/code/API_definitions/device-reachability-status.yaml b/code/API_definitions/device-reachability-status.yaml
index d5b58ca..d7df64e 100644
--- a/code/API_definitions/device-reachability-status.yaml
+++ b/code/API_definitions/device-reachability-status.yaml
@@ -37,7 +37,7 @@ info:
     Which specific authorization flows are to be used will be determined during onboarding process, happening between the API Client and the Telco Operator exposing the API, taking into account the declared purpose for accessing the API, while also being subject to the prevailing legal framework dictated by local legislation.
 
     It is important to remark that in cases where personal user data is processed by the API, and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of 3-legged access tokens becomes mandatory. This measure ensures that the API remains in strict compliance with user privacy preferences and regulatory obligations, upholding the principles of transparency and user-centric data control.
-    
+
     # Identifying a device from the access token
 
     This specification defines the `device` object field as optional in API requests, specifically in cases where the API is accessed using a 3-legged access token, and the device can be uniquely identified by the token. This approach simplifies API usage for API consumers by relying on the device information associated with the access token used to invoke the API.