Fixed chapter 06 (#11)

Author: DariuszDepta

docs/tutorial/platform/04-hello-world.md

@@ -707,7 +707,7 @@ Now you have your bytecode stored on-chain, but no smart contract has been deplo
 You can confirm this with:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query wasm list-contract-by-code $ns_code_id
         ```
@@ -742,7 +742,7 @@ To make it easy, you pick Alice as the minter.
 Get her address:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         alice=$(./build/wasmd keys show alice \
             --keyring-backend test \
@@ -787,7 +787,7 @@ Which should return something like:
 With the message ready, you can send the command to instantiate your first smart contract:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd tx wasm instantiate $ns_code_id "$ns_init_msg_1" \
             --label "name service" --no-admin \
@@ -825,7 +825,7 @@ ns_instantiate_txhash_1=9881879B2A7663638D6DA81D6F9ECC7DBF8AA12B105817B06A761749
 Now that the transaction has likely been confirmed, you can retrieve it:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query tx $ns_instantiate_txhash_1 \
             --output json | jq
@@ -852,7 +852,7 @@ The authoritative way to get this information is to get it from the events,
 more precisely at the event of type `"instantiate"`:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query tx $ns_instantiate_txhash_1 \
             --output json | jq '.events[] | select(.type == "store_code") .attributes[] | select(.key == "code_id") .value'
@@ -897,7 +897,7 @@ Your smart contract address is `wasm14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr
 which you can retrieve with:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ns_addr1=$(./build/wasmd query tx $ns_instantiate_txhash_1 \
             --output json | jq -r '.events[] | select(.type == "instantiate") .attributes[] | select(.key == "_contract_address") .value')
@@ -921,7 +921,7 @@ With the contract instantiated, you can query a few things about it.
 It is possible to get the same information by code id.
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query wasm list-contract-by-code $ns_code_id
         ```
@@ -953,7 +953,7 @@ so the correct method is to use the transaction's event proper.
 CosmWasm has kept some information about your new instance. At any time, you can retrieve it with:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query wasm contract $ns_addr1
         ```
@@ -990,7 +990,7 @@ contract_info:
 At a later stage, your contract instances may hold a token balance. At any time, you can fetch this information with:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query bank balances $ns_addr1
         ```
@@ -1022,7 +1022,7 @@ The instance keeps its state in storage. If you come from Ethereum, you are fami
 The equivalent command in CosmWasm is `query wasm contract-state`. Conveniently, it also has the `all` subcommand. So let's see what the instance has in storage with:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query wasm contract-state all $ns_addr1
         ```
@@ -1100,7 +1100,7 @@ Now that you know that:
 You can query the instance's state directly, without the `all` keyword. Either with the key in ASCII:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query wasm contract-state raw $ns_addr1 \
             name_minter --ascii \
@@ -1124,7 +1124,7 @@ You can query the instance's state directly, without the `all` keyword. Either w
 Or with the key in hex:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query wasm contract-state raw $ns_addr1 \
             6E616D655F6D696E746572 --hex \
@@ -1219,7 +1219,7 @@ Press _Encode_ and on the right you see `wasm14hj2tavq8fpesdwxxcu44rty3hh90vhujr
 Alternatively, you can do the same with wasmd:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd keys parse ade4a5f5803a439835c636395a8d648dee57b2fc90d98dc17fa887159b69638b
         ```
@@ -1243,7 +1243,7 @@ the aptly-named [`PredictableAddressGenerator`](https://github.com/CosmWasm/wasm
 If you want to pre-calculate a future address, you can use the command:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query wasm build-address --help
         ```
@@ -1312,7 +1312,7 @@ This smart contract does not need funds, but as a vehicle to demonstrate the con
 you attach funds of **100 stake** to the call:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd tx wasm execute $ns_addr1 "$ns_register_queen_to_alice" \
             --amount 100stake \
@@ -1347,7 +1347,7 @@ ns_register_queen_to_alice_txhash=7966EBDD3766243FFFFE70D0A360305DE11B0BE77A3054
 What happened? Let's look at the events that were emitted as part of this registration:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query tx $ns_register_queen_to_alice_txhash \
             --output json \
@@ -1397,7 +1397,7 @@ There comes a long list of events. Note this particular one:
 It is emitted by the bank module and is the trace that tells you that Alice paid the name service contract `100stake`. And indeed, you can confirm that now the smart contract instance holds tokens:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query bank balance $ns_addr1 stake
         ```
@@ -1428,7 +1428,7 @@ Better care next time...
 Now, if you look at how the transaction is built:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query tx $ns_register_queen_to_alice_txhash \
             --output json \
@@ -1487,7 +1487,7 @@ Although you see the word `funds` as a field of the message, it does not mean th
 You can use the same way you used earlier. Call up all storage:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query wasm contract-state all $ns_addr1
         ```
@@ -1569,7 +1569,7 @@ ns_resolve_queen='{"resolve_record":{"name":"queen-of-the-hill"}}'
 Then you pass it as a query to the smart contract:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         ./build/wasmd query wasm contract-state smart $ns_addr1 "$ns_resolve_queen"
         ```

docs/tutorial/platform/05-first-contract.md

@@ -25,7 +25,7 @@ It was built with Rust 1.80.1 for CosmWasm 2.1.3. It may work with other version
 Most likely, you will start your CosmWasm project as a Rust project. Use `cargo` to initialize a new one.
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         cargo new my-nameservice --lib --edition 2021
         ```
@@ -68,9 +68,9 @@ pub struct InstantiateMsg {}
 You use the attribute macro [`cw_serde`](https://docs.cosmwasm.com/core/entrypoints#defining-your-own-messages) in order to make your for-now-empty _instantiate_ message serializable. Make its content available to the Rust project by replacing the sample code in `src/lib.rs` with:
 
 ```rust title="src/lib.rs"
-//with-coverage
+//diff-add
 + pub mod msg;
-//no-coverage-start
+//diff-del-start
 - pub fn add(left: u64, right: u64) -> u64 {
 -     left + right
 - }
@@ -79,15 +79,15 @@ You use the attribute macro [`cw_serde`](https://docs.cosmwasm.com/core/entrypoi
 - mod tests {
 -     ...
 - }
-//no-coverage-end
+//diff-del-end
 ```
 
 Note that it says `pub` as the message needs to be known outside of the project, including tests.
 
 Back in `src/msg.rs` you will notice that `cosmwasm_schema` now appears as an `unresolved import`. You see the same message if you try to build:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         cargo build
         ```
@@ -115,7 +115,7 @@ error[E0432]: unresolved import `cosmwasm_schema`
 Indeed, you need to add the relevant dependency:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         cargo add cosmwasm-schema@2.1.3
         ```
@@ -181,7 +181,7 @@ The module is also marked as public because the CosmWasm system needs to be able
 Once again, there is a missing dependency: `cosmwasm_std`. Add it:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         cargo add cosmwasm-std@2.1.3
         ```
@@ -222,7 +222,7 @@ Again, add the following line to `src/lib.rs`.
 
 ```rust title="src/lib.rs"
 pub mod contract;
-//with-coverage
+//diff-add
 + mod error;
 pub mod msg;
 ```
@@ -232,7 +232,7 @@ Note that it is not `pub` as it only needs to be available within the Rust libra
 And don't forget to add the corresponding dependency:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         cargo add thiserror@1.0.63
         ```
@@ -250,23 +250,23 @@ And don't forget to add the corresponding dependency:
 Now that the new error type has been declared, you can use it in `src/contract.rs`:
 
 ```diff-rs title="src/contract.rs"
-//no-coverage-start
+//diff-del-start
 - use crate::msg::InstantiateMsg;
 - use cosmwasm_std::{entry_point, DepsMut, Env, MessageInfo, Response, StdError};
-//no-coverage-end
-//with-coverage-start
+//diff-del-end
+//diff-add-start
 + use crate::{error::ContractError, msg::InstantiateMsg};
 + use cosmwasm_std::{entry_point, DepsMut, Env, MessageInfo, Response};
 + 
 + type ContractResult = Result<Response, ContractError>;
-//with-coverage-end
+//diff-add-end
 
 #[cfg_attr(not(feature = "library"), entry_point)]
 pub fn instantiate(
     ...
-//no-coverage    
+//diff-del    
 - ) -> Result<Response, StdError> {
-//with-coverage
+//diff-add
 + ) -> ContractResult {
     ...
 }
@@ -288,7 +288,7 @@ At this stage, you should have something similar to the [`improve-error-reportin
 You can already build with the `cargo build` command. How about building to WebAssembly? You need to add the WebAssembly compiling target for that, if it was not yet installed.
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         rustup target add wasm32-unknown-unknown
         ```
@@ -315,7 +315,7 @@ You can already build with the `cargo build` command. How about building to WebA
 With the target installed, you can compile to WebAssembly with:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         cargo build --release --target wasm32-unknown-unknown
         ```
@@ -347,7 +347,7 @@ wasm = "build --release --target wasm32-unknown-unknown"
 With this alias defined, you can now use `cargo wasm` instead of writing `cargo build --release --target wasm32-unknown-unknown`. Change your command to:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         cargo wasm
         ```
@@ -372,7 +372,7 @@ name = "my-nameservice"
 version = "0.1.0"
 edition = "2021"
 
-//with-coverage-start
+//diff-add-start
 + # Linkage options. More information: https://doc.rust-lang.org/reference/linkage.html
 + [lib]
 + crate-type = ["cdylib", "rlib"]
@@ -392,7 +392,7 @@ edition = "2021"
 + panic = 'abort'
 + incremental = false
 + overflow-checks = true
-//with-coverage-end
+//diff-add-end
 
 [dependencies]
 ...
@@ -453,7 +453,7 @@ Note how:
 With the test ready, you can run it with the following command:
 
 <Tabs groupId="local-docker">
-    <TabItem value="Local" active>
+    <TabItem value="Local" default>
         ```shell
         cargo test
         ```