summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2019-09-13 09:05:22 +0200
committerChristian Grothoff <christian@grothoff.org>2019-09-13 09:05:22 +0200
commitf08974cc349b3bf1c4fe4631a1b69fe43917bac6 (patch)
tree22f506c6aa00542010e0963d264f50bcf06c609b
parent23d2571a045fe29054698d0511af1715ef6dcfca (diff)
downloaddocs-f08974cc349b3bf1c4fe4631a1b69fe43917bac6.tar.gz
docs-f08974cc349b3bf1c4fe4631a1b69fe43917bac6.tar.bz2
docs-f08974cc349b3bf1c4fe4631a1b69fe43917bac6.zip
typo
-rw-r--r--taler-nfc-guide.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/taler-nfc-guide.rst b/taler-nfc-guide.rst
index 4fdbd3aa..e9a1296d 100644
--- a/taler-nfc-guide.rst
+++ b/taler-nfc-guide.rst
@@ -139,7 +139,7 @@ are used:
- Accept the UTF-8 encoded JSON object in the remainder of the command data as a request tunneling response.
-The ``GET DATA (=0xCA)`` instruction (again with the instruction parameters ``0x0100`` is used to request
+The ``GET DATA (=0xCA)`` instruction (again with the instruction parameters ``0x0100``) is used to request
a command from the wallet. The APDU with this instruction must be sent with a ``0x0000`` trailer to indicate
that up to 65536 bytes of data are expected in the response from the wallet. Note that the wallet itself cannot
initiate communication, and thus the reader must "poll" the wallet for commands.