1 files changed, 1 insertions, 1 deletions
diff --git a/89.md b/89.md
index be3d075..097bdcb 100644
--- a/89.md
+++ b/89.md
@@ -65,7 +65,7 @@ The third value of the tag SHOULD be the platform where this recommendation migh
 * `content` is an optional `metadata`-like stringified JSON object, as described in NIP-01. This content is useful when the pubkey creating the `kind:31990` is not an application. If `content` is empty, the `kind:0` of the pubkey should be used to display application information (e.g. name, picture, web, LUD16, etc.)
 * `k` tags' value is the event kind that is supported by this `kind:31990`.
-Using a `k` tag(s) (instead of having the kind onf the NIP-33 `d` tag) provides:
+Using a `k` tag(s) (instead of having the kind of the `d` tag) provides:
    * Multiple `k` tags can exist in the same event if the application supports more than one event kind and their handler URLs are the same.
    * The same pubkey can have multiple events with different apps that handle the same event kind.
 * `bech32` in a URL MUST be replaced by clients with the NIP-19-encoded entity that should be loaded by the application.

diff --git a/89.md b/89.md index be3d075..097bdcb 100644 --- a/89.md +++ b/89.md
@@ -65,7 +65,7 @@ The third value of the tag SHOULD be the platform where this recommendation migh
65		65
66	* `content` is an optional `metadata`-like stringified JSON object, as described in NIP-01. This content is useful when the pubkey creating the `kind:31990` is not an application. If `content` is empty, the `kind:0` of the pubkey should be used to display application information (e.g. name, picture, web, LUD16, etc.)	66	* `content` is an optional `metadata`-like stringified JSON object, as described in NIP-01. This content is useful when the pubkey creating the `kind:31990` is not an application. If `content` is empty, the `kind:0` of the pubkey should be used to display application information (e.g. name, picture, web, LUD16, etc.)
67	* `k` tags' value is the event kind that is supported by this `kind:31990`.	67	* `k` tags' value is the event kind that is supported by this `kind:31990`.
68	Using a `k` tag(s) (instead of having the kind onf the NIP-33 `d` tag) provides:	68	Using a `k` tag(s) (instead of having the kind of the `d` tag) provides:
69	* Multiple `k` tags can exist in the same event if the application supports more than one event kind and their handler URLs are the same.	69	* Multiple `k` tags can exist in the same event if the application supports more than one event kind and their handler URLs are the same.
70	* The same pubkey can have multiple events with different apps that handle the same event kind.	70	* The same pubkey can have multiple events with different apps that handle the same event kind.
71	* `bech32` in a URL MUST be replaced by clients with the NIP-19-encoded entity that should be loaded by the application.	71	* `bech32` in a URL MUST be replaced by clients with the NIP-19-encoded entity that should be loaded by the application.