From c6618a5255b302f25ede133ffa0bad0ce28b2c2c Mon Sep 17 00:00:00 2001
From: yuroitaki <25913766+yuroitaki@users.noreply.github.com>
Date: Mon, 26 May 2025 17:13:16 +0800
Subject: [PATCH] Modify intro.

---
 docs/protocol/custom_extension.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/protocol/custom_extension.md b/docs/protocol/custom_extension.md
index 0fc3354..59df8b0 100644
--- a/docs/protocol/custom_extension.md
+++ b/docs/protocol/custom_extension.md
@@ -4,7 +4,9 @@ sidebar_position: 5
 
 # Custom Extensions
 
-Notary attestations can be extended with custom fields defined by the `Prover`. This allows applications to attach additional data to attestations in a verifiable way. For now, the `Notary` simply includes these fields in the signed attestation without validation. In the future, a plugin system will allow developers to add custom logic to the `Notary` for verifying this data. Until then, such validation requires modifying the Notary code directly.
+Notary attestations can be extended with custom fields defined by the `Prover` or the `Notary`. This allows applications to attach additional data to attestations in a verifiable way.
+
+For now, the default notary server implementation only supports including custom data requested by the `Prover` in the attestation without any validation. In the future, a plugin system will allow developers to add custom logic to the notary server for adding or validating these data, without needing to modify the notary server code.
 
 ## Use Cases