Small tweaks

Author: Jon Staab

90.md

@@ -12,9 +12,9 @@ This NIP defines listings for service providers.
 
 A flow is an independently-defined specification for how users ineract with a given service. The flow may be identified using any one of the following:
 
-- A `SP-XX` number, referring to a specification contained in this document.
-- A url pointing to a web page containing a flow specification.
-- A nostr event address pointing to any event which contains a flow specification.
+- A `NSP-XX` number, referring to a specification contained in this document, e.g. `["n", "NSP-01"]`.
+- A url pointing to a web page containing a flow specification, e.g. `["n", "https://example.com/my-nsp"]`.
+- A nostr event address pointing to any event which contains a flow specification, e.g. `["n", "<kind>:<pubkey>:<d>"]`.
 
 Flow specifications MAY describe ANY flow, but SHOULD use nostr events as the primary means of communication between parties. Nostr events SHOULD specify the address of the `kind 31999` service announcement event when relevant, rather than the serivce provider's pubkey. Events SHOULD be posted to the recipient's inbox relays unless specified otherwise.
 
@@ -65,7 +65,7 @@ Service providers MAY publish kind `1999` heartbeat events to indicate service a
 
 ## Flow Specifications
 
-### SP-01 - Content Discovery
+### NSP-01 - Content Discovery
 
 User publishes a `kind 5300` request for recommended content, including the following tags: