NIP-54 double mention 'merge requests'

[bquast]

NIP-54 lists MERGE REQUESTS twice:

1. Section # 5
2. Appendix # 1 (ought to be enumerated A)

Section # 5 content:

Event kind:818 represents a request to merge from a forked article into the source. It is directed to a pubkey and references the original article and the modified event.

[INSERT EVENT EXAMPLE]

Appendix 1 content:

Users can request other users to get their entries merged into someone else's entry by creating a kind:818 event.

{
"content": "I added information about how to make hot ice-creams",
"kind": 818,
"tags": [
[ "a", "30818::hot-ice-creams", "" ],
[ "e", "", "" ],
[ "p", "" ],
[ "e", "", "", "source" ]
]
}
.content: an optional explanation detailing why this merge is being requested. a tag: tag of the article which should be modified (i.e. the target of this merge request). e tag: optional version of the article in which this modifications is based e tag with source marker: the ID of the event that should be merged. This event id MUST be of a kind:30818 as defined in this NIP.

The destination-pubkey is the pubkey being requested to merge something into their article can create [[NIP-25]] reactions that tag the kind:818 event with + or -

P.S. Appendices should be 'enumerated' using letters, instead of numbers. Even if sections are not enumerated, certain clients might do that (e.g. LaTeX would), then you get a Section 2 and an Appendix 2 (but without the prefixes 'Section' and 'Appendix', so they look the same).

This is a well established convention.