From a26f738afe6d693bd4fafb3ff831613012b4cd52 Mon Sep 17 00:00:00 2001 From: Simon Warta <2603011+webmaster128@users.noreply.github.com> Date: Mon, 19 Sep 2022 13:53:38 +0200 Subject: [PATCH] Update docs/MESSAGE_TYPES.md Co-authored-by: Tomasz Kurcz --- docs/MESSAGE_TYPES.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/MESSAGE_TYPES.md b/docs/MESSAGE_TYPES.md index cbcd9a0395..6a12bf75ad 100644 --- a/docs/MESSAGE_TYPES.md +++ b/docs/MESSAGE_TYPES.md @@ -1,13 +1,13 @@ ## CosmWasm message types -CosmWasm uses JSON for sending data from the host the Wasm contract and results +CosmWasm uses JSON for sending data from the host to the Wasm contract and results out of the Wasm contract. Such JSON messages are created in the client, -typically some JavaScript-based application. There the usage of JSON is feels -very natural for developers. However, JSON has signigicant limitations such as +typically some JavaScript-based application. There the usage of JSON feels +very natural for developers. However, JSON has significant limitations such as the lack of a native binary type and inconsistent support for integers > 53 bit. -For this reason, the CosmWasm standard limrary `cosmwasm-std` shipts types that -ensure good user experience in JSON. The following table shows both stadard Rust -types as well as cosmwasm_std types and how they are encoded in JSON. +For this reason, the CosmWasm standard library `cosmwasm-std` ships types that +ensure good user experience in JSON. The following table shows both standard Rust +types as well as `cosmwasm_std` types and how they are encoded in JSON. | Rust type | JSON type[^1] | Example | Note | | ------------------- | -------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------- |