From 6dc94a434306241d0666cba788d74990547954e4 Mon Sep 17 00:00:00 2001
From: Sergio Moya <1083296+smoya@users.noreply.github.com>
Date: Wed, 27 Apr 2022 16:14:24 +0200
Subject: [PATCH] add links to PR and Issue for Security at operation level

---
 pages/blog/release-notes-2.4.0.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pages/blog/release-notes-2.4.0.md b/pages/blog/release-notes-2.4.0.md
index 22fc2293c163..f153dff80842 100644
--- a/pages/blog/release-notes-2.4.0.md
+++ b/pages/blog/release-notes-2.4.0.md
@@ -80,7 +80,6 @@ This new feature was contributed by [Daniel Kocot](https://github.com/danielkoco
 ## Security can now be defined at Operation level
 
 Until today, Security requirements were defined at Server level. That restricted the security requirements to be the same for all channels linked with a Server, and for all operations of those channels.
-Thanks to [Sekharbans](https://github.com/sekharbans-ebay), is it possible to increase that granularity by defining a set of security requirements at Operation level. 
 In fact, when setting Security in both the Server and the Operation, both should be satisfied.
 
 For example:
@@ -109,6 +108,8 @@ channels:
           - auth:read  
 ```
 
+Thanks to [Sekharbans](https://github.com/sekharbans-ebay), is now possible to increase security granularity by defining a set of security requirements at Operation level. For more detail, see [Sekharban's `/spec #584` pull request](https://github.com/asyncapi/spec/pull/584) and the [Github issue where Sekharban's suggested feature was discussed](https://github.com/asyncapi/spec/issues/584).
+
 ## Reusability of Servers defined in Components is clarified in the specification
 
 Reusability of Servers was introduced in [AsyncAPI 2.3.0](https://www.asyncapi.com/blog/release-notes-2.3.0#servers-and-channels-can-now-be-defined-as-reusable-components). However, the change was not fully clarified in the specification, leading to confusion.