From 7fbd2490b7216a93ec2881b1ff8ecb47344d86a1 Mon Sep 17 00:00:00 2001
From: cmarco0 <146938645+cmarco0@users.noreply.github.com>
Date: Wed, 10 Jul 2024 11:03:00 +0200
Subject: [PATCH] better explaination that the example provided is
 non-normative

---
 draft-demarco-oauth-nonce-endpoint.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/draft-demarco-oauth-nonce-endpoint.md b/draft-demarco-oauth-nonce-endpoint.md
index 9bdfd6f..ab6dfd2 100644
--- a/draft-demarco-oauth-nonce-endpoint.md
+++ b/draft-demarco-oauth-nonce-endpoint.md
@@ -210,11 +210,13 @@ Below are provided some non-normative examples, describing how a decrypted and J
 
 Please note that the values represented in the previous examples are informative.
 
+**Note:** The example provided is non-normative and is provided for illustrative purposes only. The example is intended to demonstrate potential use cases and do not prescribe any specific implementation requirements.
+
 In any case, the payload MUST include some unique value (`"jti"` on the example above), typically generated using a pseudo-random number generator with sufficient entropy [RFC4086], to ensure that the encrypted digest (the actual Nonce) is also unique.
 
 # Nonce Payload Claims
 
-The body of Nonce Payload contains:
+In the table below, the claims in the non-normative example above are explained:
 
 | Claim             | Description                                                                                     | Reference                       |
 |-------------------|---------------------------------------------------------------------------------------------|---------------------------------|