Fixed formatting.

Author: DariuszDepta

docs/multi-test/getting-started/counter/implementation.md

@@ -141,7 +141,7 @@ The `lib.rs` file in a Rust project serves as the main entry point for defining
 library. In the context of our example **counter** smart contract, the `lib.rs` file is defining and
 organizing the modules that make up the contract. Recall the **counter** project file structure:
 
-```text {4,6} title="counter directory content"
+```text {4,6} title="counter directory"
 .
 ├── Cargo.toml
 └── src
@@ -390,7 +390,7 @@ value that can be incremented, decremented, queried, or reset by the smart contr
 about the [Item](../../../storage-plus/containers/item.md) type can be found in
 [StoragePlus](../../../storage-plus/introduction.md) documentation.
 
-### _instantiate_ entrypoint
+### `instantiate` entrypoint
 
 The `instantiate` function (entry-point) is called during the instantiation of the smart
 contract. Depending on the value of the message passed in `msg` argument, the counter will be
@@ -417,7 +417,7 @@ pub fn instantiate(
 }
 ```
 
-### _execute_ entrypoint
+### `execute` entrypoint
 
 The `execute` function (entry-point) is called whenever the user wants to interact with the
 contract, especially when the value of the counter should be incremented, decremented or reset.
@@ -446,7 +446,7 @@ pub fn execute(
 }
 ```
 
-### _query_ entrypoint
+### `query` entrypoint
 
 The `query` function (entry-point) is called whenever the user asks the counter smart
 contract for the current value. The counter value is retrieved from the contract's persistent

docs/multi-test/getting-started/counter/introduction.md

@@ -36,31 +36,31 @@ library named **counter**.
 
 Change the working directory to your home directory:
 
-```shell
+```shell title="terminal"
 cd ~
 ```
 
 Create a dedicated directory to store your example smart contract:
 
-```shell
+```shell title="terminal"
 mkdir my-contracts
 ```
 
 Change the working directory to `my-contracts`:
 
-```shell
+```shell title="terminal"
 cd my-contracts
 ```
 
 Create a new Rust library named **counter**:
 
-```shell
+```shell title="terminal"
 cargo init --lib counter
 ```
 
 Change the working directory to `counter`:
 
-```shell
+```shell title="terminal"
 cd counter
 ```
 
@@ -80,13 +80,13 @@ should be stored in `src` directory.
 
 Let's create an empty **contract.rs** file...
 
-```shell
+```shell title="terminal"
 touch src/contract.rs
 ```
 
 ...and empty **msg.rs** file:
 
-```shell
+```shell title="terminal"
 touch src/msg.rs
 ```
 
@@ -103,6 +103,6 @@ The final structure of the smart contract project placed in the `counter` direct
 
 ## Filling the content
 
-In the previous section you have created a project structure for **counter** smart contract,
+In this section you have created a project structure for **counter** smart contract,
 but the source files are still empty. In the following chapter, we provide an example
 [**implementation**](./implementation.md) of the **counter** smart contract.

docs/multi-test/getting-started/writing-tests/introduction.md

@@ -2,7 +2,7 @@
 
 Having the **counter** smart contract set up, let's first check if the project compiles:
 
-```shell
+```shell title="terminal"
 cargo build
 ```
 
@@ -23,7 +23,7 @@ been built successfully.
 It is a very good habit to run [Rust linter](https://doc.rust-lang.org/clippy) after each code
 change, so let's run it before we move forward.
 
-```shell
+```shell title="terminal"
 cargo clippy
 ```
 
@@ -72,13 +72,13 @@ Note, that both directories **`src`** and **`tests`** are placed at the root of
 
 Let's begin by creating the `tests` directory:
 
-```shell
+```shell title="terminal"
 mkdir tests
 ```
 
 Then create an empty `mod.rs` file inside the `tests` directory:
 
-```shell
+```shell title="terminal"
 touch tests/mod.rs
 ```
 
@@ -91,13 +91,13 @@ mod multitest;
 By convention, we place all **MultiTest** test cases under the `multitest` directory, so let's
 create it:
 
-```shell
+```shell title="terminal"
 mkdir tests/multitest
 ```
 
 Inside the `tests/multitest` directory we should also create an empty file named `mod.rs`:
 
-```shell
+```shell title="terminal"
 touch tests/multitest/mod.rs
 ```
 
@@ -109,7 +109,7 @@ mod test_counter;
 
 Finally, inside the `tests/multitest` directory, we create a file named `test_counter.rs`:
 
-```shell
+```shell title="terminal"
 touch tests/multitest/test_counter.rs
 ```
 
@@ -121,7 +121,7 @@ Now that the directory structure for tests is ready, it's time to run all tests.
 
 Once the directories and files are set up for tests, let's execute them:
 
-```shell
+```shell title="terminal"
 cargo test
 ```
 
@@ -155,7 +155,7 @@ integration tests (**line 12**) and **0** for documentation tests (**line 16**).
 
 Similarly, to execute all tests using [cargo-nextest](https://nexte.st), type:
 
-```shell copy filename="TERMINAL"
+```shell title="terminal"
 cargo nextest run
 ```
 
@@ -180,7 +180,7 @@ quite tedious, so let's prepare a short script to automate this task.
 
 Create an empty file named `coverage.sh` in the `counter` directory:
 
-```shell
+```shell title="terminal"
 touch coverage.sh
 ```
 
@@ -198,7 +198,7 @@ echo "Report: file://$(pwd)/target/coverage-report/tarpaulin-report.html"
 
 Finally, make this file executable:
 
-```shell
+```shell title="terminal"
 chmod +x coverage.sh
 ```
 
@@ -227,7 +227,7 @@ should now look like this:
 
 With the code coverage script at hand, measuring code coverage is now as simple as typing:
 
-```shell
+```shell title="terminal"
 ./coverage.sh
 ```
 
@@ -308,4 +308,6 @@ pub fn query(deps: Deps, _env: Env, msg: CounterQueryMsg) -> Result<Binary, StdE
 
 ## Writing tests for smart contracts
 
-Now it is time to start implementing tests for the **counter** smart contract.
+Now it is time to start implementing tests for the **[counter]** smart contract.
+
+[counter]: ../counter/introduction.md

docs/multi-test/installation.md

@@ -19,8 +19,12 @@ cw-multi-test = "3"
 
 **MultiTest** is a **TESTING** library and should **ALWAYS** be added to your project
 as a **DEVELOPMENT DEPENDENCY** in section **`[dev-dependencies]`** of the **Cargo.toml** file.
+
+:::
 
-**MultiTest** <u>**IS NOT**</u> designed to be used in production code on a real-life blockchain.
+:::warning
+
+**MultiTest** <span style={{color:'red'}}>**IS NOT**</span> designed to be used in production code on a real-life blockchain.
 
 :::
 

docs/multi-test/introduction.md

@@ -37,5 +37,5 @@ To successfully follow the upcoming chapters, a basic knowledge of [Rust and Car
 
 :::
 
-[Rust and Cargo]: https://www.rust-lang.org/tools/install
+[Rust and Cargo]: https://rust-lang.org/learn
 [file an issue]: https://github.com/CosmWasm/cw-multi-test/issues