From ceedeb512e6486bcecd98b291410d85f17b0f6e7 Mon Sep 17 00:00:00 2001 From: Elias Rad <146735585+nnsW3@users.noreply.github.com> Date: Fri, 24 Jan 2025 17:17:28 +0200 Subject: [PATCH 1/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d0a84ad6..2bfe2015 100644 --- a/README.md +++ b/README.md @@ -60,7 +60,7 @@ We give up the node layer (including networking, block production etc.), but we In other words, we keep bare blockchain state in-memory, and we can interact with it directly however we want. This way, we gain full control over the runtime, sacrificing real simulation of the blockchain environment. -However, usually, this is higly beneficial for the development process, as it allows for a much faster feedback loop, assisted with better insights into execution externalities. +However, usually, this is highly beneficial for the development process, as it allows for a much faster feedback loop, assisted with better insights into execution externalities. --- From 428c2836438faa76487b2a03fba7586bfe15efb5 Mon Sep 17 00:00:00 2001 From: Elias Rad <146735585+nnsW3@users.noreply.github.com> Date: Fri, 24 Jan 2025 17:20:06 +0200 Subject: [PATCH 2/3] Update README.md --- examples/contract-events/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/contract-events/README.md b/examples/contract-events/README.md index d9d84af5..a256571a 100644 --- a/examples/contract-events/README.md +++ b/examples/contract-events/README.md @@ -25,7 +25,7 @@ let last_call_value = record.last_call_return_decoded::(); as well as the events that have been emitted by contracts: ```rust -// `last_event_batch` returns the batch of runtime events that have been emitted during last contract interaction. +// `last_event_batch` returns the batch of runtime events that have been emitted during the last contract interaction. let last_event_batch = record.last_event_batch(); // We can filter out raw events emitted by contracts with `contract_events` method. let contract_events_data = last_event_batch.contract_events(); From 87fd3a12e017b468a049cee6e73a7c3017dbd81d Mon Sep 17 00:00:00 2001 From: Elias Rad <146735585+nnsW3@users.noreply.github.com> Date: Fri, 24 Jan 2025 17:20:25 +0200 Subject: [PATCH 3/3] Update README.md --- examples/cross-contract-call-tracing/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/examples/cross-contract-call-tracing/README.md b/examples/cross-contract-call-tracing/README.md index 403fad18..e919c714 100644 --- a/examples/cross-contract-call-tracing/README.md +++ b/examples/cross-contract-call-tracing/README.md @@ -1,6 +1,6 @@ -# Cross contract call tracing +# Cross-contract call tracing -This example shows how you can trace and debug cross contract calls. +This example shows how you can trace and debug cross-contract calls. ## Scenario @@ -57,4 +57,4 @@ and returned: successes: tests::test -``` \ No newline at end of file +```