refactor code (#264)

Author: DariuszDepta

src/pages/cw-multi-test/getting-started.mdx

@@ -11,7 +11,7 @@ smart contracts using **`MultiTest`**. It provides a practical example and best
 a smooth start with using **`MultiTest`** for testing smart contracts. In the following chapters,
 you will be:
 
-- designing example [**counter**](getting-started/counter.mdx) smart contract,
+- designing an example [**counter**](getting-started/counter.mdx) smart contract,
 - [**writing tests**](getting-started/writing-tests.mdx) for the counter smart contract.
 
 The example **counter** smart contract and all test cases are provided in two versions: one using

src/pages/sylvia/basics/contract-structure.mdx

@@ -186,7 +186,7 @@ queries should never mutate the state. This is not the case for the [`ExecCtx`](
 and `InstantiateCtx` which exposes the
 [`DepsMut`](https://docs.rs/cosmwasm-std/latest/cosmwasm_std/struct.DepsMut.html).
 
-Feel free expanding the macro now and seeing what Sylvia generates. It might be overwhelming, as
+Feel free to expanding the macro now and seeing what Sylvia generates. It might be overwhelming, as
 there will be a lot of things generated that seem not relevant to our code, so for the bare minimum,
 check the [`InstantiateMsg`](../macros/generated-types/message-types#contract-messages) and its
 `impl` block.

src/pages/sylvia/macros/attributes/payload.mdx

@@ -81,4 +81,4 @@ impl Contract {
 ```
 
 Sylvia uses the [`from_json`](https://docs.rs/cosmwasm-std/latest/cosmwasm_std/fn.from_json.html) to
-deserialize the `payload` field, so it has to be serialized do JSON.
+deserialize the `payload` field, so it has to be serialized to JSON.

src/pages/sylvia/macros/entry-points.mdx

@@ -6,7 +6,7 @@ import { Callout } from "nextra/components";
 
 # Entry_points
 
-Use the `entry_points` macro to generate entry points of your contract.
+Use the `entry_points` macro to generate entry points for your contract.
 
 <Callout>
     Use `entry_points` macro on top of `contract` macro. The `contract` macro erases all the Sylvia attributes, which may cause

src/pages/tutorial/cw-contract/event.mdx

@@ -170,7 +170,7 @@ call. Additionally, there is a possibility to add attributes directly to the res
 sugar. By default, every execution emits a standard "wasm" event. Adding attributes to the result
 adds them to the default event.
 
-We can check if events are properly emitted by contract. It is not always done, as it is much of
+We can check if events are properly emitted by the contract. It is not always done, as it is much of
 boilerplate in test, but events are, generally, more like logs - not necessarily considered main
 contract logic. Let's now write single test checking if execution emits events: