Merge pull request #1175 from Concordium/DOC301-ReviewSmartContracts

Finished review on What is a smart contract section

Author: dragosgd

source/mainnet/docs/smart-contracts/contract-instances.rst

@@ -91,7 +91,7 @@ transaction for attempting to create the instance is visible on-chain.
 
 .. seealso::
 
-   See :ref:`initialize-contract` guide for how to initialize a
+   See the :ref:`initialize-contract` guide for how to initialize a
    contract in practice. You can also watch a video about initializing smart contract instances.
 
    .. raw:: html

source/mainnet/docs/smart-contracts/contract-lifecycle.rst

@@ -8,6 +8,8 @@ A smart contract is first deployed to the chain as part of a :ref:`contract
 module <contract-module>`. After this a smart contract can be *initialized* to
 obtain a :ref:`smart contract instance <contract-instances>`. Finally a smart
 contract instance can be repeatedly updated according to its own logic.
+Before you can follow this guide, you need to :ref:`setup the development environment <setup-env>`.
+
 
 .. image:: images/smart-contract-lifecycle.png
     :width: 100%

source/mainnet/docs/smart-contracts/contract-module.rst

@@ -44,6 +44,7 @@ the code.
 Wasm is a low-level language and it is impractical to write by hand. Instead, you
 can write smart contracts in a more high-level language that is then
 compiled to Wasm. The best supported high-level language on Concordium is Rust.
+You can read :ref:`this article <writing-smart-contracts>` for more information regarding using Rust on Concordium.
 
 .. _wasm-limitations:
 
@@ -75,7 +76,7 @@ point values.
 Deployment
 ==========
 
-Deploying a module to the chain means submitting the module bytecode as a
+:ref:`Deploying <deploy-module>` a module to the chain means submitting the module bytecode as a
 transaction to the Concordium network. If *valid*, this transaction will be
 included in a block. This transaction, as every other transaction, has an
 associated cost. The cost is based on the size of the bytecode and is charged

source/mainnet/docs/smart-contracts/develop-contracts.rst

@@ -420,5 +420,5 @@ macro, e.g.: ``#[init(..., payable)]`` and ``#[receive(..., payable)]``.
 .. |StateMap| replace:: ``StateMap``
 .. _StateSet: https://docs.rs/concordium-std/latest/concordium_std/struct.StateSet.html
 .. |StateSet| replace:: ``StateSet``
-.. _payable: https://docs.rs/concordium-std-derive/latest/concordium_std_derive/attr.init.html#payable-make-function-accept-an-amount-of-ccd
+.. _payable: https://docs.rs/concordium-std/latest/concordium_std/attr.receive.html#payable-make-function-accept-an-amount-of-ccd
 .. |payable| replace:: ``payable``

source/mainnet/docs/smart-contracts/guides/build-contract.rst

@@ -14,8 +14,7 @@ Once you are familiar with smart contracts, it is a good idea to read the :ref:`
    To request CCDs for testing, use the buttons in the Concordium Wallets when running Testnet.
 
 
-Before you can start developing smart contracts, you need to setup the
-environment.
+Before you can start developing smart contracts, you need to :ref:`setup the development environment <setup-env>`.
 
 You can also watch a video about installing the smart contract tools.
 

source/mainnet/docs/smart-contracts/introduction.rst

@@ -11,7 +11,7 @@
 What is a smart contract
 ===============================
 
-Already know what smart contracts are? Go to the :ref:`quick guide<sc-quick-start>` to start building smart contracts on Concordium right away.
+Already know what smart contracts are? Go to the :ref:`quick start guide<sc-quick-start>` to start building smart contracts on Concordium right away.
 
 A :term:`smart contract` is a user-supplied piece of code submitted to the Concordium
 blockchain, used to define behavior that is not directly part of the core
@@ -81,7 +81,8 @@ does not fulfil their obligations. This will most likely mean that the contract
 needs to support some notion of proof that the seller has indeed fulfilled their
 obligation, or some way for the highest bidder to file a complaint. Smart
 contracts cannot resolve these real-world issues automatically, and the best
-solution is likely going to depend on the specifics of the auction.
+solution is likely going to depend on the specifics of the auction. You can find
+an example implementation of the auction contract on `this repository <https://github.com/Concordium/concordium-rust-smart-contracts/tree/main/examples/auction>`_
 
 Additional reading
 ------------------