From 0241ccd8b047dad46530d5533d24cf9267159205 Mon Sep 17 00:00:00 2001 From: bruno Date: Wed, 7 Feb 2018 12:44:33 +0100 Subject: [PATCH] Docs: Michelson: fix typos --- docs/whitedoc/michelson.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/whitedoc/michelson.rst b/docs/whitedoc/michelson.rst index dda9b3f9a..0311c6d9d 100644 --- a/docs/whitedoc/michelson.rst +++ b/docs/whitedoc/michelson.rst @@ -393,7 +393,7 @@ III - Core data types and notations of type ``(t)`` that we note ``{ Elt key value ; ... }``, with keys sorted. - ``big_map (k) (t)``: Lazily deserialized maps from keys of type - ``(k)`` of values of type ``(t)`` that we note ``{ Elt key value ... }``, + ``(k)`` of values of type ``(t)`` that we note ``{ Elt key value ; ... }``, with keys sorted. These maps should be used if you intend to store large amounts of data in a map. They have higher gas costs than standard maps as data is lazily deserialized. You are limited to a @@ -1055,28 +1055,28 @@ Operations on maps where SIZE / { } : S => s : S -Operations on big_maps -~~~~~~~~~~~~~~~~~~~~~~ +Operations on ``big_maps`` +~~~~~~~~~~~~~~~~~~~~~~~~~~ The behaviour of these operations is the same as if they were normal maps, except that under the hood, the elements are loaded and deserialized on demand. -- ``GET``: Access an element in a big_map, returns an optional value to be +- ``GET``: Access an element in a ``big_map``, returns an optional value to be checked with ``IF_SOME``. :: :: 'key : big_map 'key 'val : 'S -> option 'val : 'S -- ``MEM``: Check for the presence of an element in a big_map. +- ``MEM``: Check for the presence of an element in a ``big_map``. :: :: 'key : big_map 'key 'val : 'S -> bool : 'S -- ``UPDATE``: Assign or remove an element in a map. +- ``UPDATE``: Assign or remove an element in a ``big_map``. ::