1 files changed, 1 insertions, 1 deletions
diff --git a/99.md b/99.md
index e2ffc3b..724ce5f 100644
--- a/99.md
+++ b/99.md
@@ -26,7 +26,7 @@ The `.pubkey` field of these events are treated as the party creating the listin
 ### Metadata
- For "tags"/"hashtags" (i.e. categories or keywords of relevance for the listing) the `"t"` event tag should be used, as per [NIP-12](12.md).
+- For "tags"/"hashtags" (i.e. categories or keywords of relevance for the listing) the `"t"` event tag should be used.
 - For images, whether included in the markdown content or not, clients SHOULD use `image` tags as described in [NIP-58](58.md). This allows clients to display images in carousel format more easily.
 The following tags, used for structured metadata, are standardized and SHOULD be included. Other tags may be added as necessary.

diff --git a/99.md b/99.md index e2ffc3b..724ce5f 100644 --- a/99.md +++ b/99.md
@@ -26,7 +26,7 @@ The `.pubkey` field of these events are treated as the party creating the listin
26		26
27	### Metadata	27	### Metadata
28		28
29	- For "tags"/"hashtags" (i.e. categories or keywords of relevance for the listing) the `"t"` event tag should be used, as per [NIP-12](12.md).	29	- For "tags"/"hashtags" (i.e. categories or keywords of relevance for the listing) the `"t"` event tag should be used.
30	- For images, whether included in the markdown content or not, clients SHOULD use `image` tags as described in [NIP-58](58.md). This allows clients to display images in carousel format more easily.	30	- For images, whether included in the markdown content or not, clients SHOULD use `image` tags as described in [NIP-58](58.md). This allows clients to display images in carousel format more easily.
31		31
32	The following tags, used for structured metadata, are standardized and SHOULD be included. Other tags may be added as necessary.	32	The following tags, used for structured metadata, are standardized and SHOULD be included. Other tags may be added as necessary.