From 38c983dc4290f7fca4dfe53acaf338fa15786560 Mon Sep 17 00:00:00 2001
From: Tomas Bezouska <bezysoftware@outlook.com>
Date: Sat, 30 Nov 2024 09:21:18 +0100
Subject: [PATCH] NIPs are no longer numbers

---
 11.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/11.md b/11.md
index 8af4f31..c339514 100644
--- a/11.md
+++ b/11.md
@@ -18,7 +18,7 @@ When a relay receives an HTTP(s) request with an `Accept` header of `application
   "icon": <a link to an icon (e.g. in .jpg, or .png format>,
   "pubkey": <administrative contact pubkey>,
   "contact": <administrative alternate contact>,
-  "supported_nips": <a list of NIP numbers supported by the relay>,
+  "supported_nips": <a list of NIPs supported by the relay>,
   "software": <string identifying relay software URL>,
   "version": <string version identifier>
 }
@@ -64,7 +64,7 @@ An alternative contact may be listed under the `contact` field as well, with the
 
 ### Supported NIPs
 
-As the Nostr protocol evolves, some functionality may only be available by relays that implement a specific `NIP`.  This field is an array of the integer identifiers of `NIP`s that are implemented in the relay.  Examples would include `1`, for `"NIP-01"` and `9`, for `"NIP-09"`.  Client-side `NIPs` SHOULD NOT be advertised, and can be ignored by clients.
+As the Nostr protocol evolves, some functionality may only be available by relays that implement a specific `NIP`.  This field is an array of the string identifiers of `NIP`s that are implemented in the relay.  Examples would include `1`, for `"NIP-01"` and `9`, for `"NIP-09"`.  Client-side `NIPs` SHOULD NOT be advertised, and can be ignored by clients.
 
 ### Software