From 8bf87116e4935810671fac2c6d5e4b8348992e22 Mon Sep 17 00:00:00 2001 From: Dave Jones Date: Tue, 25 Apr 2023 16:58:01 -0500 Subject: [PATCH] tweak --- value/value.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/value/value.md b/value/value.md index d74efe6..b252513 100644 --- a/value/value.md +++ b/value/value.md @@ -506,11 +506,11 @@ the `customKey` and `customValue` attributes. There are currently 3 payment "actions" that are defined in the BLIP-10 TLV extension that is embedded in the payment payload: "stream", "boost" and "auto". -* "stream" - This means the payment is a timed interval payment (i.e. - every minute) that is sent or queued while the +* `stream` - This means the payment is a timed interval payment (i.e. - every minute) that is sent or queued while the user is engaged in active listening/viewing of the content. -* "boost" - This means the payment is a user generated one-time payment that happens in response to a user initiated +* `boost` - This means the payment is a user generated one-time payment that happens in response to a user initiated action like a "Boost" button push, or some other clearly labeled payment initiation function. These types of payments can contain textual messages (i.e. - a boostagram). -* "auto" - This means the payment was an app initiated payment that recurs at a specific long-form interval such as +* `auto` - This means the payment was an app initiated payment that recurs at a specific long-form interval such as weekly, monthly, yearly, etc. The user configures an interval and payment amount in the app and the app then sends that amount at the specified time when each interval passes. \ No newline at end of file