Removed unnecessary setup section, duplicate

source/mainnet/conf.py

@@ -494,7 +494,6 @@
     ".smart-contracts/tutorials/nft-minting/build-smart-contract": "tutorials/nft-minting/build-smart-contract.html",
     "./smart-contracts/tutorials/nft-minting/mint-xfer": "tutorials/nft-minting/mint-xfer.html",
     "./smart-contracts/tutorials/sft-minting/index": "tutorials/sft-minting/index.html",
-    "./smart-contracts/tutorials/sft-minting/setup": "tutorials/sft-minting/setup.html",
     "./smart-contracts/tutorials/sft-minting/build-smart-contract": "tutorials/sft-minting/build-smart-contract.html",
     "./smart-contracts/tutorials/sft-minting/mint-xfer": "tutorials/sft-minting/mint-xfer.html",
     "./smart-contracts/tutorials/fungible-tokens/index": "tutorials/fungible-tokens/index.html",

source/mainnet/tutorials/sft-minting/build-smart-contract.rst

@@ -4,7 +4,7 @@
 Smart contract modifications
 ============================
 
-In this tutorial, you will use the example ``cis2-nft`` contract template from Concordium, which you can initialize using the cargo-concordium tool via the ``cargo concordium init`` command. In this tutorial you will add a couple of things and update some functions to give more flexibility to the template.
+In this tutorial, you will use the example ``cis2-multi`` contract template from Concordium, which can be found `here <https://github.com/Concordium/concordium-rust-smart-contracts/tree/main/examples/cis2-multi>`_ for further reading. In this tutorial you will add a couple of things and update some functions to give more flexibility to the template.
 
 First, you will add a new struct called ``TokenMetadata``. It needs to implement the ``Serialize`` and ``SchemaType`` traits. For those who are familiar with the Ethereum ecosystem, it's similar to the ABI.
 
@@ -57,7 +57,7 @@ When you have the ``TokenMetadata`` add one more line to the minting params stru
         tokens: collections::BTreeMap<ContractTokenId, (TokenMetadata, ContractTokenAmount)>,
     }
 
-Always remember, à blockchain itself is a state-keeping machine. If you send a transaction, you change the state. If you mint an NFT or transfer it, the state is changed again. Basically, if you make any change to the data structure, you change the state. So what is this state? Look at the code snippet below.
+Always remember, a blockchain itself is a state-keeping machine. If you send a transaction, you change the state. If you mint an NFT or transfer it, the state is changed again. Basically, if you make any change to the data structure, you change the state. So what is this state? Look at the code snippet below.
 
 .. code-block:: rust
 

source/mainnet/tutorials/sft-minting/index.rst

@@ -25,6 +25,5 @@ One of the best use cases of semi-fungible tokens is in gaming and the metaverse
    :maxdepth: 1
    :caption: Semi-fungible token minting
 
-   setup
    build-smart-contract
    mint-xfer