summaryrefslogtreecommitdiff
path: root/developers.html
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2014-11-18 14:49:36 +0100
committerChristian Grothoff <christian@grothoff.org>2014-11-18 14:49:36 +0100
commit89b04b3ac984b2fb7c2cee20005dd33847dc2a43 (patch)
tree98abc35b46bcd5312deb55cc2524e1c35dfe891e /developers.html
parentdd13f3b77ab4b513728b61cd0794fdd72889322c (diff)
downloadwww-89b04b3ac984b2fb7c2cee20005dd33847dc2a43.tar.gz
www-89b04b3ac984b2fb7c2cee20005dd33847dc2a43.tar.bz2
www-89b04b3ac984b2fb7c2cee20005dd33847dc2a43.zip
about
Diffstat (limited to 'developers.html')
-rw-r--r--developers.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/developers.html b/developers.html
index f2fddc46..d6eec334 100644
--- a/developers.html
+++ b/developers.html
@@ -30,7 +30,7 @@
<p>Taler is designed to work on the Internet. To ensure that Taler payments can work with restrictive network setups, Taler uses a RESTful protocol over
HTTP or HTTPS. Taler's security does not depend upon the use of HTTPS, but obviously merchants may choose to offer HTTPS for consistency and because
it generally is better for privacy compared to HTTP. Taler uses JSON to encode structure data, making it easy to integrate Taler with existing Web
- applications. Taler's protocol is documented in detail <a href="http://api.taler.net/">here</a></p>
+ applications. Taler's protocol is documented in detail <a href="http://api.taler.net/">here</a>.</p>
</div>
</div>
<div class="row">