Add eosio.contracts documentation content to release/1.9.x

README.md

@@ -18,19 +18,7 @@ Dependencies:
 * [eosio.cdt v1.7.x](https://github.com/EOSIO/eosio.cdt/releases/tag/v1.7.0-rc1)
 * [eosio v2.0.x](https://github.com/EOSIO/eos/releases/tag/v2.0.0-rc1) (optional dependency only needed to build unit tests)
 
-To build contracts alone:
-1. Ensure an appropriate version of eosio.cdt is installed. Installing eosio.cdt from binaries is sufficient.
-2. Run the `build.sh` script in the top directory to build all the contracts.
-
-To build the contracts and unit tests:
-1. Ensure an appropriate version of eosio.cdt is installed. Installing eosio.cdt from binaries is sufficient.
-2. Ensure an appropriate version of eosio has been built from source and installed. Installing eosio from binaries is not sufficient.
-3. Run the `build.sh` script in the top directory with the `-t` flag to build all the contracts and the unit tests for these contracts.
-
-After build:
-* If the build was configured to also build unit tests, the unit tests executable is placed in the _build/tests_ folder and is named __unit_test__.
-* The contracts (both `.wasm` and `.abi` files) are built into their corresponding _build/contracts/\<contract name\>_ folder.
-* Finally, simply use __cleos__ to _set contract_ by pointing to the previously mentioned directory for the specific contract.
+To build the contracts follow the instructions in [`Compile and deploy` section](./docs/02_compile-and-deploy.md).
 
 ## Contributing
 

contracts/eosio.msig/include/eosio.msig/eosio.msig.hpp

@@ -6,6 +6,7 @@
 #include <eosio/transaction.hpp>
 
 namespace eosio {
+
    /**
     * @defgroup eosiomsig eosio.msig
     * @ingroup eosiocontracts
@@ -27,8 +28,7 @@ namespace eosio {
           * authorized by the provided keys and permissions, and if the proposal name doesn’t
           * already exist; if all validations pass the `proposal_name` and `trx` trasanction are
           * saved in the proposals table and the `requested` permission levels to the
-          * approvals table (for the `proposer` context).
-          * Storage changes are billed to `proposer`.
+          * approvals table (for the `proposer` context). Storage changes are billed to `proposer`.
           *
           * @param proposer - The account proposing a transaction
           * @param proposal_name - The name of the proposal (should be unique for proposer)
@@ -46,8 +46,7 @@ namespace eosio {
           * proposed by `proposer`. If the proposal's requested approval list contains the `level`
           * permission then the `level` permission is moved from internal `requested_approvals` list to
           * internal `provided_approvals` list of the proposal, thus persisting the approval for
-          * the `proposal_name` proposal.
-          * Storage changes are billed to `proposer`.
+          * the `proposal_name` proposal. Storage changes are billed to `proposer`.
           *
           * @param proposer - The account proposing a transaction
           * @param proposal_name - The name of the proposal (should be unique for proposer)