From 2145ff24bbde0185938c6abfacc7ecef18301a61 Mon Sep 17 00:00:00 2001
From: zadevhub <138465437+zadevhub@users.noreply.github.com>
Date: Thu, 29 Jan 2026 09:37:25 +0000
Subject: [PATCH] Update oauth2-jwt.md

The word emit is difficult to follow. I had to look it up in this context. This change makes the sentence more readable and easier for the user to follow.
---
 docs/en/docs/tutorial/security/oauth2-jwt.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/docs/tutorial/security/oauth2-jwt.md b/docs/en/docs/tutorial/security/oauth2-jwt.md
index 95baf871c1..316a464a97 100644
--- a/docs/en/docs/tutorial/security/oauth2-jwt.md
+++ b/docs/en/docs/tutorial/security/oauth2-jwt.md
@@ -18,7 +18,7 @@ eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4
 
 It is not encrypted, so, anyone could recover the information from the contents.
 
-But it's signed. So, when you receive a token that you emitted, you can verify that you actually emitted it.
+But it's signed. So, when you receive a token that you originally issued, you can verify that it actually came from you and has not been tampered with in-transit.
 
 That way, you can create a token with an expiration of, let's say, 1 week. And then when the user comes back the next day with the token, you know that user is still logged in to your system.