gnunet-svn
[Top][All Lists]
Advanced

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

[taler-docs] 03/03: hopefully uncontroversial style nit: s/organisations


From: gnunet
Subject: [taler-docs] 03/03: hopefully uncontroversial style nit: s/organisations/organizations/
Date: Sat, 28 Nov 2020 03:11:34 +0100

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

ttn pushed a commit to branch master
in repository docs.

commit 37cb14044906cb5cff65b0c462e9e4311e708b8d
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Fri Nov 27 21:09:36 2020 -0500

    hopefully uncontroversial style nit: s/organisations/organizations/
    
    I saw elsewhere there is "honor", so assume we lean to American English.
    However, i also note that "i.e." and "e.g." are often not followed by comma,
    which is more British English.  Probably we need to choose one or the other.
---
 libeufin/iso20022.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libeufin/iso20022.rst b/libeufin/iso20022.rst
index 7fc0c4d..e45222a 100644
--- a/libeufin/iso20022.rst
+++ b/libeufin/iso20022.rst
@@ -36,7 +36,7 @@ Reasons for not using ISO 20022 directly are:
    to JSON, they are difficult to use due to their verbosity.
 3. Underspecification.  Messages like camt.05x leave many "degrees of freedom"
    when translating the underlying data into a message.
-4. No interoperability.  As a result of underspecification, different 
countries/organisations
+4. No interoperability.  As a result of underspecification, different 
countries/organizations
    define their own subset and interpretation rules for ISO 20022 messages.  
This can
    lead to even contradictory usage rules.  An example for this is how the 
Swiss and EPC
    interpretations handle transaction amounts in the presence of multiple 
currencies.

-- 
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]