Specify how "authors" metadata field should be used (#138)

Reviewed-on: https://codeberg.org/fediverse/fep/pulls/138

fep-xxxx-template.md

@@ -1,6 +1,6 @@
 ---
 slug: "xxxx"
-authors: Alyssa P. Hacker <alyssa.p.hacker@social.example>, Chatty Ben <ben@chatty.example>
+authors: Alyssa P. Hacker <alyssa.p.hacker@email.example>, Chatty Ben <@ben@fediverse.example>
 status: DRAFT
 dateReceived: 1970-01-01
 ---
@@ -15,11 +15,11 @@ dateReceived: 1970-01-01
 ## References
 
 - [ActivityPub] Christine Lemmer Webber, Jessica Tallon, [ActivityPub](https://www.w3.org/TR/activitypub/), 2018
-- [ABC] Alyssa P. Hacker, [An example proposal](http://example.org/abc.html), 2020
+- [ABC] Alyssa P. Hacker, [An example proposal](http://abc.example/abc.html), 2020
 
 
 ## Copyright
 
-CC0 1.0 Universal (CC0 1.0) Public Domain Dedication 
+CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
 
 To the extent possible under law, the authors of this Fediverse Enhancement Proposal have waived all copyright and related or neighboring rights to this work.

fep/a4ed/fep-a4ed.md

@@ -56,7 +56,7 @@ Proposal metadata is placed at the top of the document as key-value pairs betwee
 
 Following metadata key-value pairs may be placed at the top of a proposal:
 
-- `authors`: A comma separated list of authors of the proposal.
+- `authors`: A comma separated list of authors of the proposal. Each item of the list should contain an author's name followed by a contact address in angle brackets (e.g. `Alyssa P. Hacker <alyssa.p.hacker@email.example>`, `Alyssa P. Hacker <@alyssa.p.hacker@fediverse.example>`).
 - `status`: Indicates the proposal status. Can be either `DRAFT`, `WITHDRAWN` or `FINAL`.
 - `dateReceived`: Date of when the proposal was added to the repository (when status is set to `DRAFT`).
 - `dateWithdrawn`: Date of when the proposal status was set to `WITHDRAWN` (only for proposals with status `WITHDRAWN`).