From 3d4fc177923532cd4c19099412b73366cbcc83fd Mon Sep 17 00:00:00 2001
From: aloccid-iata <140411726+aloccid-iata@users.noreply.github.com>
Date: Wed, 15 Nov 2023 16:55:59 +0100
Subject: [PATCH] fix wrong link

---
 working_draft/API/docs/security/authn-application-layer.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/working_draft/API/docs/security/authn-application-layer.md b/working_draft/API/docs/security/authn-application-layer.md
index 00332cb5..06806900 100644
--- a/working_draft/API/docs/security/authn-application-layer.md
+++ b/working_draft/API/docs/security/authn-application-layer.md
@@ -64,7 +64,7 @@ In order to be compliant with ONE Record specification, the JWT token must conta
 ## Payload 
 The payload contains the claims, which are statements about the ONE Record client server or other data. The claims are divided into three types:
 
-- Registered claims: These are predefined claims that are not mandatory but recommended. They include information such as the issuer (iss), subject (sub), audience (aud) and expiration time (exp). Additional registered claims can be found in the (RFC7519 specification)[https://tools.ietf.org/html/rfc7519#section-4.1]
+- Registered claims: These are predefined claims that are not mandatory but recommended. They include information such as the issuer (iss), subject (sub), audience (aud) and expiration time (exp). Additional registered claims can be found in the [RFC7519 specification](https://tools.ietf.org/html/rfc7519#section-4.1)
 
 - Public claims: JWT users have the freedom to define public claims according to their requirements. However, to prevent conflicts, it is recommended to either register these public claims in the IANA JSON Web Token Registry or define them using a URI with a namespace that can withstand collisions.