Merge pull request #154 from Supercolony-net/feature/upgradable-contract

Documentation about upgradable contracts

examples/diamond/README.md

@@ -2,8 +2,8 @@
 
 Contract module which provides am implementation of Diamond Standard pattern for upgradeable contracts.
 
-This module is used through the embedding of `DiamondData` and implementation of `Diamond` and
-`DiamondStorage` traits. It will allow us to update contract implementation via the Diamond Standard pattern.
+This module is used through the embedding of `diamond::Data` and implementation of `Diamond` and
+`Storage` traits. It will allow us to update contract implementation via the Diamond Standard pattern.
 We can add support for different facets (contracts) and their functions and remove or replace existing functions
 from the contract.
 

examples/ownable/README.md

@@ -4,8 +4,8 @@ Contract module which provides a basic access control mechanism, where
 there is an account (an owner) that can be granted exclusive access to
 specific functions.
 
-This module is used through the embedding of `OwnableData` and implementation of `Ownable` and
-`OwnableStorage` traits. It will make the modifier `only_owner` available, which can be applied
+This module is used through the embedding of `ownable::Data` and implementation of `Ownable` and
+`Storage` traits. It will make the modifier `only_owner` available, which can be applied
 to your functions to restrict their use to the owner.
 
 [See example](https://supercolony-net.github.io/openbrush-contracts/smart-contracts/ownable)

examples/pausable/README.md

@@ -3,8 +3,8 @@
 Contract module, which allows children to implement an emergency stop
 mechanism that an authorized account can trigger.
 
-This module is used through the embedding of `PausableData` and implementation of `Pausable` and
-`PausableStorage` traits. It will make available the modifier `when_not_paused` and `when_paused`,
+This module is used through the embedding of `pausable::Data` and implementation of `Pausable` and
+`Storage` traits. It will make available the modifier `when_not_paused` and `when_paused`,
 which can be applied to your functions to restrict their usage.
 
 [See example](https://supercolony-net.github.io/openbrush-contracts/smart-contracts/pausable)

examples/payment_splitter/README.md

@@ -12,10 +12,7 @@ accounts but kept in this contract, and the actual transfer is triggered as a se
 function. `release` pays out to only the provided address. If you will have many people to pay out, especially if often, you will likely
 want to use the `releaseAll` method instead to save you a lot of time.
 
-** Note **: In the substrate balance of contract decreases each block. Because it pays rent for the storage.
-So during `release`, each next user will get fewer native tokens.
-
-This module is used through embedding of `PaymentSplitterData` and implementation of `PaymentSplitter` and
-`PaymentSplitterStorage` traits.
+This module is used through embedding of `payment_splitter::Data` and implementation of `PaymentSplitter` and
+`Storage` traits.
 
 [See example](https://supercolony-net.github.io/openbrush-contracts/smart-contracts/payment-splitter)

examples/proxy/README.md

@@ -2,8 +2,8 @@
 
 Contract module which provides am implementation of Proxy pattern for upgradeable contracts.
 
-This module is used through the embedding of `ProxyData` and implementation of `Proxy` and
-`ProxyStorage` traits. It will allow us to update contract implementation via a Proxy pattern.
+This module is used through the embedding of `proxy::Data` and implementation of `Proxy` and
+`Storage` traits. It will allow us to update contract implementation via a Proxy pattern.
 We can get the current contract's implementation code hash or set the new implementation's code hash.
 To set a new code hash signer must be the owner of the Proxy.
 

examples/timelock_controller/README.md

@@ -12,8 +12,8 @@ is in charge of proposing (resp executing) operations. A common use case is
 to position this `TimelockController` as the owner of a smart contract, with
 a multisig or a DAO as the sole proposer.
 
-This module is used through embedding of `TimelockControllerData`, `AccessControlData` and
-implementation of `TimelockController`, `TimelockControllerStorage`, `AccessControl` and
-`AccessControlStorage` traits.
+This module is used through embedding of `timelock_controller::Data`, `access_control::Data` and
+implementation of `TimelockController`, `AccessControl` and
+`Storage` traits.
 
 [See example](https://supercolony-net.github.io/openbrush-contracts/smart-contracts/timelock-controller)