From 3f5cd0123935b6245fb6077ffe5311e7fb29a8c9 Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Wed, 8 May 2024 17:19:03 -0300 Subject: rename "parameterized replaceable event" to "tagged-replaceable event". --- 75.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to '75.md') diff --git a/75.md b/75.md index c16436a..cfc29f9 100644 --- a/75.md +++ b/75.md @@ -53,11 +53,11 @@ The following tags are OPTIONAL. } ``` -The goal MAY include an `r` or `a` tag linking to a URL or parameterized replaceable event. +The goal MAY include an `r` or `a` tag linking to a URL or tagged-replaceable event. The goal MAY include multiple beneficiary pubkeys by specifying [`zap` tags](57.md#appendix-g-zap-tag-on-other-events). -Parameterized replaceable events can link to a goal by using a `goal` tag specifying the event id and an optional relay hint. +Tagged-replaceable events can link to a goal by using a `goal` tag specifying the event id and an optional relay hint. ```json { @@ -77,7 +77,7 @@ Clients MAY display funding goals on user profiles. When zapping a goal event, clients MUST include the relays in the `relays` tag of the goal event in the zap request `relays` tag. -When zapping a parameterized replaceable event with a `goal` tag, clients SHOULD tag the goal event id in the `e` tag of the zap request. +When zapping a tagged-replaceable event with a `goal` tag, clients SHOULD tag the goal event id in the `e` tag of the zap request. ## Use cases -- cgit v1.2.3