follow list rewording

A suggesting to make readability better.

02.md

@@ -6,9 +6,13 @@ Follow List
 
 `final` `optional`
 
-A special event with kind `3`, meaning "follow list" is defined as having a list of `p` tags, one for each of the followed/known profiles one is following.
+A special event with kind `3`, meaning "follow list", is defined as having a list of `p` tags, one for each of the profiles to be followed.
 
-Each tag entry should contain the key for the profile, a relay URL where events from that key can be found (can be set to an empty string if not needed), and a local name (or "petname") for that profile (can also be set to an empty string or not provided), i.e., `["p", <32-bytes hex key>, <main relay URL>, <petname>]`.
+Each "p" tag entry should be populated as follows: 
+- The first element is "p"
+- The second element contains the pubkey string
+- The third element is either an empty string, or a relay URL where events from that key can be found
+- The fourth and final element is either an empty string or a string with a local name for that profile (or "petname")
 
 The `.content` is not used.
 
@@ -27,7 +31,7 @@ For example:
 }
 ```
 
-Every new following list that gets published overwrites the past ones, so it should contain all entries. Relays and clients SHOULD delete past following lists as soon as they receive a new one.
+Every new following list that gets published overwrites all previous ones, so it should contain all entries. Relays and clients SHOULD delete past following lists as soon as they receive a new one.
 
 Whenever new follows are added to an existing list, clients SHOULD append them to the end of the list, so they are stored in chronological order.