taler-docs

commit 95afc65ab01fec2c22e8555af69ba386233c80b2
parent 9bbfbe38ab89d5c768fad70182041454ffc665a0
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Wed, 29 Jul 2015 13:01:19 +0200

typo fix

Diffstat:
M
api-mint.rst
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/api-mint.rst b/api-mint.rst
@@ -723,7 +723,7 @@ Binary Blob Specification
 
   .. note::
 
-     Due to the way of handling `big` numbers by some platforms (such as `JavaScript`, for exapmle), wherever the following specification mentions a 64-bit value, the actual implementations
+     Due to the way of handling `big` numbers by some platforms (such as `JavaScript`, for example), wherever the following specification mentions a 64-bit value, the actual implementations
      are strongly advised to rely on arithmetic up to 53 bits.
 
 This section specifies the binary representation of messages used in Taler's protocols. The message formats are given in a C-style pseudocode notation.  Padding is always specified explicitly, and numeric values are in network byte order (big endian).