From 903f2775c17842d1b92f15b94860fbf67fecf3eb Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Tue, 26 Nov 2024 08:07:21 +0100 Subject: [PATCH 1/5] fix typo --- SEMANTICS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SEMANTICS.md b/SEMANTICS.md index 017735f1e8..df0990e7c2 100644 --- a/SEMANTICS.md +++ b/SEMANTICS.md @@ -344,7 +344,7 @@ It just ends up returning `Err` to contract-A's `reply` function. Note that errors are not handled with `ReplyOn::Success`, meaning, in such a case, an error will be treated just like a normal `message` returning an error. -This diagram may help explain. Imagine a contract returned two submesssages - +This diagram may help explain. Imagine a contract returned two submessages - (a) with `ReplyOn::Success` and (b) with `ReplyOn::Error`: | processing a) | processing b) | reply called | may overwrite result from reply | note | From 1087ee7c4c28016d4e899326c18cacf80ed69f56 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Tue, 26 Nov 2024 08:10:12 +0100 Subject: [PATCH 2/5] fix typo --- docs/CAPABILITIES.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/CAPABILITIES.md b/docs/CAPABILITIES.md index 8ae2f0e397..057dad4ac7 100644 --- a/docs/CAPABILITIES.md +++ b/docs/CAPABILITIES.md @@ -96,7 +96,7 @@ contract checks the availability early on. When functionality is always present in the VM (such as a new import implemented directly in the VM, see [#1299]), we should not use capability. They just create -fragmentation in the CosmWasm ecosystem and increase the barrier for adoption. +fragmentation in the CosmWasm ecosystem and increase the barrier to adoption. Instead the `check_wasm_imports` check is used to validate this when the contract is stored. From a0805f7775c4543d81e61b6fd7d77c60ff738a7f Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Tue, 26 Nov 2024 08:12:39 +0100 Subject: [PATCH 3/5] fix typo --- contracts/burner/src/msg.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contracts/burner/src/msg.rs b/contracts/burner/src/msg.rs index f8d7f4558d..9eb8dfae7d 100644 --- a/contracts/burner/src/msg.rs +++ b/contracts/burner/src/msg.rs @@ -18,7 +18,7 @@ pub struct InstantiateMsg {} #[cw_serde] pub enum ExecuteMsg { /// Cleans up the given number of state elements. - /// Call this multiple times to increamentally clean up state. + /// Call this multiple times to incrementally clean up state. Cleanup { /// The number of state elements to delete. /// From 9f18a88e0b70ffaaee10cc0e078f0e30548008db Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Tue, 26 Nov 2024 08:14:22 +0100 Subject: [PATCH 4/5] fix typos --- contracts/crypto-verify/src/ethereum.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contracts/crypto-verify/src/ethereum.rs b/contracts/crypto-verify/src/ethereum.rs index f6958a0230..3fedc2a992 100644 --- a/contracts/crypto-verify/src/ethereum.rs +++ b/contracts/crypto-verify/src/ethereum.rs @@ -63,7 +63,7 @@ fn serialize_unsigned_transaction( /// Get the recovery param from the value `v` when no chain ID for replay protection is used. /// -/// This is needed for chain-agnostig aignatures like signed text. +/// This is needed for chain-agnostic signatures like signed text. /// /// See [EIP-155] for how `v` is composed. /// @@ -78,7 +78,7 @@ pub fn get_recovery_param(v: u8) -> StdResult { /// Get the recovery param from the value `v` when a chain ID for replay protection is used. /// -/// This is needed for chain-agnostig aignatures like signed text. +/// This is needed for chain-agnostic signatures like signed text. /// /// See [EIP-155] for how `v` is composed. /// From 350f88e8025a25c7fc7676fcf2e04d5a8c467f2d Mon Sep 17 00:00:00 2001 From: "autofix-ci[bot]" <114827586+autofix-ci[bot]@users.noreply.github.com> Date: Tue, 26 Nov 2024 07:24:19 +0000 Subject: [PATCH 5/5] [autofix.ci] apply automated fixes --- SEMANTICS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SEMANTICS.md b/SEMANTICS.md index df0990e7c2..ea00133024 100644 --- a/SEMANTICS.md +++ b/SEMANTICS.md @@ -344,8 +344,8 @@ It just ends up returning `Err` to contract-A's `reply` function. Note that errors are not handled with `ReplyOn::Success`, meaning, in such a case, an error will be treated just like a normal `message` returning an error. -This diagram may help explain. Imagine a contract returned two submessages - -(a) with `ReplyOn::Success` and (b) with `ReplyOn::Error`: +This diagram may help explain. Imagine a contract returned two submessages - (a) +with `ReplyOn::Success` and (b) with `ReplyOn::Error`: | processing a) | processing b) | reply called | may overwrite result from reply | note | | ------------- | ------------- | ------------ | ------------------------------- | ------------------------------------------------- |