gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: simplify; swap out old FIXME for new


From: gnunet
Subject: [taler-docs] branch master updated: simplify; swap out old FIXME for new FIXME
Date: Wed, 11 Aug 2021 11:37:19 +0200

This is an automated email from the git hooks/post-receive script.

ttn pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 2789962  simplify; swap out old FIXME for new FIXME
2789962 is described below

commit 27899628e73e315685a9c34fea0e223144f84d3d
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Wed Aug 11 05:33:13 2021 -0400

    simplify; swap out old FIXME for new FIXME
---
 taler-merchant-manual.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index a4e3310..d5e3a25 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

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]