From 899ca769be0aae6c5f977bf37173543eea5eba3e Mon Sep 17 00:00:00 2001 From: trbouma Date: Wed, 24 Apr 2024 16:12:38 -0400 Subject: [PATCH] typos --- 05-signed-metadata.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/05-signed-metadata.md b/05-signed-metadata.md index db5089ce..ae55d90d 100644 --- a/05-signed-metadata.md +++ b/05-signed-metadata.md @@ -8,11 +8,11 @@ Adding Signed Metadata to DNS-based internet identifiers ## Proposal -This NIP proposes the addtion of ```"metadata``` to the nip-05 response to provide optionally signed metadata about the identifier. +This NIP proposes the addtion of ```"metadata"``` to the nip-05 response to provide optionally signed metadata about the identifier. ## Rationale -The value of this NIP is that it extends the capability of a NIP-05 identifier to present unsigned or signed (verifiable) credential about itself, or about the controller of the identifier. For example, a NIP-05 identifier such as ```bob@example.com``` can express a signed statement that Bob is indeed a professional engineer. This capability enables a NIP-05 identifier express trusted (signed) statements that can be presented as such in a client, where indication is required. +The value of this NIP is that it extends the capability of a NIP-05 identifier to present unsigned or signed (verifiable) credentials about itself, or about the controller of the identifier. For example, a NIP-05 identifier such as ```bob@example.com``` can express a signed statement that Bob is indeed a professional engineer. This capability enables a NIP-05 identifier express trusted (signed) statements that can be presented as such in a client, where indication is required. ## Theory and Approach