From 0faf47cf88ba1a09efa3237508730399a8c30e9a Mon Sep 17 00:00:00 2001
From: Florian Dold <florian.dold@gmail.com>
Date: Wed, 24 Aug 2016 14:25:29 +0200
Subject: fix duplicate label

---
 articles/ui/ui.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'articles/ui/ui.tex')

diff --git a/articles/ui/ui.tex b/articles/ui/ui.tex
index 0f0d66882..07be16254 100644
--- a/articles/ui/ui.tex
+++ b/articles/ui/ui.tex
@@ -792,7 +792,7 @@ a Taler wallet is installed (as it is in Figure~\ref{fig:shopping}).
 }
 \end{lstlisting}
   \caption{Minimal Taler contract over a digital article with a value of \EUR{0.10}}
-  \label{listing:contract}
+  \label{listing:json-contract}
 \end{figure*}
 
 \begin{figure*}[h!]
@@ -816,7 +816,7 @@ X-Taler-Contract-Url: https://myshop/generate-contract?product=42
 \end{figure*}
 
 The offer URL of the Web shop can then initiate payments by sending a
-\emph{contract proposal} (Figure~\ref{listing:contract}) to the wallet, either via the HTTP status
+\emph{contract proposal} (Figure~\ref{listing:json-contract}) to the wallet, either via the HTTP status
 code {\tt 402 Payment Required} (Figure~\ref{listing:http-contract}), or via Taler's JavaScript API
 (Figure~\ref{listing:contract}).  The wallet then presents the
 contract to the user.  The format of the contract is in an extensible
-- 
cgit v1.2.3

