summaryrefslogtreecommitdiff
path: root/taler-merchant-manual.rst
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2021-08-11 05:33:13 -0400
committerThien-Thi Nguyen <ttn@gnuvola.org>2021-08-11 05:33:13 -0400
commit27899628e73e315685a9c34fea0e223144f84d3d (patch)
tree637c5ad4a4f9b1467129a44a5a631ffd2451b0a4 /taler-merchant-manual.rst
parentf357f261c5369586ad67f8efa580fe737d6e2619 (diff)
downloaddocs-27899628e73e315685a9c34fea0e223144f84d3d.tar.gz
docs-27899628e73e315685a9c34fea0e223144f84d3d.tar.bz2
docs-27899628e73e315685a9c34fea0e223144f84d3d.zip
simplify; swap out old FIXME for new FIXME
Diffstat (limited to 'taler-merchant-manual.rst')
-rw-r--r--taler-merchant-manual.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index a4e33107..d5e3a250 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -197,9 +197,9 @@ to the wallet as part of the order URI.
Additionally, when stocks are limited, you can configure Taler to
set a *product lock* on items (say, while composing the shopping cart).
These locks, as well as the *order lock* (when the order is complete),
-can be configured to auto-unlock at a certain time or triggering event.
+can be configured to auto-unlock at certain times.
-.. FIXME: Is the "or event" correct? If so, what events are triggers?
+.. FIXME: Is "can be configured" correct? (Are there controls surfaced?)
A wallet may *pay* for a claimed order, at which point the order turns into
a (paid) contract. Orders have an expiration date after which the commercial