Skip to content

Commit

Permalink
fix: typos
Browse files Browse the repository at this point in the history
Signed-off-by: omahs <[email protected]>
  • Loading branch information
omahs committed Aug 30, 2024
1 parent a60b85b commit 6d740b5
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 9 deletions.
2 changes: 1 addition & 1 deletion src/develop/smart-contracts/everdev.md
Original file line number Diff line number Diff line change
Expand Up @@ -371,4 +371,4 @@ Where
3. If you want to explore the GraphQL API more, [here is the documentation](https://docs.evercloud.dev/reference/graphql-api)!
4. If you are an exchange - check out our [exchange guide](https://docs.everos.dev/ever-sdk/add_to_exchange)!

We hope this guide was helpful to you! If you have any difficulties/questions/suggestions/etc. please write to out [telegram channel](https://t.me/ever_sdk).
We hope this guide was helpful to you! If you have any difficulties/questions/suggestions/etc. please write to our [telegram channel](https://t.me/ever_sdk).
4 changes: 2 additions & 2 deletions src/develop/smart-contracts/locklift-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ const config: LockliftConfig = {
// path: "/mnt/o/projects/broxus/TON-Solidity-Compiler/build/solc/solc",
// Or specify version of compiler
version: "0.62.0",
// Specify config for extarnal contracts as in exapmple
// Specify config for external contracts as in example
// externalContracts: {
// "node_modules/broxus-ton-tokens-contracts/build": ['TokenRoot', 'TokenWallet']
// }
Expand Down Expand Up @@ -174,7 +174,7 @@ npx locklift test -n local
## Invoke Scripts
There is a common practice to keep various scripts within the same environment where the samrt contracts and tests live. Such scripts may perform deployment, configuration, data collection or and smart-contract upgrade routines.
There is a common practice to keep various scripts within the same environment where the smart contracts and tests live. Such scripts may perform deployment, configuration, data collection or and smart-contract upgrade routines.
Let's run the sample deployment script within locklift environment (make sure your local node container is up and running)
Expand Down
12 changes: 6 additions & 6 deletions src/develop/smart-contracts/tokensale.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ contract Tokensale {
_rate = rate;
_supply = supply;
// fundamental mechanic of dapps working with tip3 - deploy it's own wallet to operate with. check tip3 specs for more info
// fundamental mechanic of dapps working with tip3 - deploy its own wallet to operate with. check tip3 specs for more info
ITokenRoot(distributedTokenRoot).deployWallet {
value: 0.2 ever,
flag: 1,
Expand Down Expand Up @@ -157,7 +157,7 @@ That's all. When we deploy the `Tokensale` contract, `deployWallet` will be call
ITokenWallet(_distributedTokenWallet).transfer{ value: 0, flag: 128 }(
purchase,
msg.sender,
0.1 ever, // this parameter allows to deploy wallet for user, if it's not deployed yet. (fee takes from message so will be payed by user)
0.1 ever, // this parameter allows to deploy wallet for user, if it's not deployed yet. (fee takes from message so will be paid by user)
msg.sender,
false,
empty
Expand All @@ -177,7 +177,7 @@ The next mechanic is already familiar to you. Tokensale just calls its own deplo
ITokenWallet(_distributedTokenWallet).transfer{ value: 0, flag: 128 }(
purchase,
msg.sender,
0.1 ever, // this parameter allows to deploy wallet for user, if it's not deployed yet. (fee takes from message so will be payed by user)
0.1 ever, // this parameter allows to deploy wallet for user, if it's not deployed yet. (fee takes from message so will be paid by user)
msg.sender,
false,
empty
Expand Down Expand Up @@ -220,7 +220,7 @@ contract Tokensale {
_rate = rate;
_supply = supply;
// fundamental mechanic of dapps working with tip3 - deploy it's own wallet to operate with. check tip3 specs for more info
// fundamental mechanic of dapps working with tip3 - deploy its own wallet to operate with. check tip3 specs for more info
ITokenRoot(distributedTokenRoot).deployWallet {
value: 0.2 ever,
flag: 1,
Expand Down Expand Up @@ -259,7 +259,7 @@ contract Tokensale {
ITokenWallet(_distributedTokenWallet).transfer{ value: 0, flag: 128 }(
purchase,
msg.sender,
0.1 ever, // this parameter allows to deploy wallet for user, if it's not deployed yet. (fee takes from message so will be payed by user)
0.1 ever, // this parameter allows to deploy wallet for user, if it's not deployed yet. (fee takes from message so will be paid by user)
msg.sender,
false,
empty
Expand All @@ -270,4 +270,4 @@ contract Tokensale {
}
```

All you need now is to write some tests with locklift support. There are some simple tests and deploy scripts available in the following [repo](https://github.com/venom-blockchain/guides/tree/master/tokensale-contracts).
All you need now is to write some tests with locklift support. There are some simple tests and deploy scripts available in the following [repo](https://github.com/venom-blockchain/guides/tree/master/tokensale-contracts).

0 comments on commit 6d740b5

Please sign in to comment.