From 3e0e6ca2d65eca76fbe929859d5f359f3ed6bfcf Mon Sep 17 00:00:00 2001
From: Leo Wandersleb <leo@leowandersleb.de>
Date: Fri, 2 Sep 2022 16:07:50 -0400
Subject: [PATCH] separate array elements with ,

---
 10.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/10.md b/10.md
index 8b7bd573..7f697e97 100644
--- a/10.md
+++ b/10.md
@@ -13,7 +13,7 @@ This NIP describes how to use "e" and "p" tags in text events, especially those
 ## Positional "e" tags (DEPRECATED)
 >This scheme is in common use; but should be considered deprecated.
 
-`["e", <event-id> <relay-url>]`  as per NIP-01.
+`["e", <event-id>, <relay-url>]`  as per NIP-01.
 
 Where:
 
@@ -26,19 +26,19 @@ Where:
  This event is not a reply to, nor does it refer to, any other event.
 
  * One "e" tag: <br>
- `["e",<id>]`: The id of the event to which this event is a reply.
+ `["e", <id>]`: The id of the event to which this event is a reply.
 
- * Two "e" tags:  `["e",<root-id>]`, `["e",<reply-id>]` <br>
+ * Two "e" tags:  `["e", <root-id>]`, `["e", <reply-id>]` <br>
  `<root-id>` is the id of the event at the root of the reply chain.  `<reply-id>` is the id of the article to which this event is a reply.  
 
- * Many "e" tags: `["e",<root-id>]` `["e",<mention-id>]`, ..., `["e",<reply-id>]`<br>
+ * Many "e" tags: `["e", <root-id>]` `["e", <mention-id>]`, ..., `["e", <reply-id>]`<br>
 There may be any number of `<mention-ids>`.  These are the ids of events which may, or may not be in the reply chain.  
 They are citings from this event.  `root-id` and `reply-id` are as above.
 
 >This scheme is deprecated because it creates ambiguities that are difficult, or impossible to resolve when an event references another but is not a reply.
 
 ## Marked "e" tags (PREFERRED)
-`["e", <event-id> <relay-url> <marker>]`  
+`["e", <event-id>, <relay-url>, <marker>]`  
 	
 Where:
 
@@ -54,7 +54,7 @@ Where:
 ## The "p" tag
 Used in a text event contains a list of pubkeys used to record who is involved in a reply thread.
 
-When replying to a text event E the reply event's "p" tags should contain all of E's "p" tags as well as the `"pubkey"` of the of the event being replied to.  
+When replying to a text event E the reply event's "p" tags should contain all of E's "p" tags as well as the `"pubkey"` of the event being replied to.  
 
 Example:  Given a text event authored by `a1` with "p" tags [`p1`, `p2`, `p3`] then the "p" tags of the reply should be [`a1`, `p1`, `p2`, `p3`] 
 in no particular order.