Docs fix spelling issues

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.
 
 ---
 

examples/contract-events/README.md

@@ -25,7 +25,7 @@ let last_call_value = record.last_call_return_decoded::<CustomType>();
 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();

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
-```
+```