[taler-www] branch master updated: Rectifing the titles of two papers

[gnunet]

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

skuegel pushed a commit to branch master
in repository www.

The following commit(s) were added to refs/heads/master by this push:
     new ac29f3e  Rectifing the titles of two papers
ac29f3e is described below

commit ac29f3ed89ad2384d4d20bcfcd5d1d4fc7d71b13
Author: Stefan Kügel <skuegel@web.de>
AuthorDate: Sat Oct 21 20:30:00 2023 +0200

    Rectifing the titles of two papers
    
    Signed-off-by: Stefan Kügel <skuegel@web.de>
---
 www.yml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/www.yml b/www.yml
index 440c161..38986cb 100644
--- a/www.yml
+++ b/www.yml
@@ -88,7 +88,7 @@ newsposts:
     title: Comment émettre une monnaie numérique de banque centrale
   - page: 2021-06.html
     date: 2021-06-17
-    title: How to issue a privacy-preserving central bank digital currency
+    title: How to issue a Privacy-preserving Central Bank Digital Currency
   - page: 2021-03.html
     date: 2021-03-29
     title: Why a Digital Euro should be Online-first and Bearer-based
@@ -240,7 +240,7 @@ paperslist:
     authors:
       - Christian Grothoff
       - Thomas Moser
-    name: "How to issue a privacy-preserving centrally banked digital currency"
+    name: "How to Issue a Privacy-preserving Central Bank Digital Currency"
     kind: Article
     url: 
https://www.suerf.org/suer-policy-brief/27227/how-to-issue-a-privacy-preserving-central-bank-digital-currency
     url_html: 
https://www.suerf.org/suer-policy-brief/27227/how-to-issue-a-privacy-preserving-central-bank-digital-currency
@@ -261,7 +261,7 @@ paperslist:
       - David Chaum
       - Christian Grothoff
       - Thomas Moser
-    name: "How to Issue a Centrally Banked Digital Currency"
+    name: "How to Issue a Central Bank Digital Currency"
     kind: Article
     url: https://www.snb.ch/en/mmr/papers/id/working_paper_2021_03
     url_html:

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