Skip to content

Commit 6f04da0

Browse files
authored
Update fee-calculation.md
1 parent 199133e commit 6f04da0

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/v3/guidelines/smart-contracts/fee-calculation.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Use the `GETSTORAGEFEE` opcode with the following parameters:
2222
| bits | Number of contract bits |
2323
| is_mc | True if the source or destination is in the masterchain |
2424

25-
:::info Only unique hash cells are counted for storage and fwd fees i.e. 3 identical hash cells are counted as one.
25+
:::info Only unique hash cells are counted for storage and forward fees; for example, three identical hash cells are counted as one.
2626

2727
In particular, it deduplicates data: if there are several equivalent sub-cells referenced in different branches, their content is only stored once.
2828

@@ -31,7 +31,7 @@ In particular, it deduplicates data: if there are several equivalent sub-cells r
3131

3232
### Calculation Flow
3333

34-
Each contract has its balance. You can calculate how many TONs your contract requires to remain valid for a specified `seconds` time using the function:
34+
Each contract has its balance. You can calculate how many TONs your contract needs to remain valid for a given number of seconds using the following function:
3535

3636
```func
3737
int get_storage_fee(int workchain, int seconds, int bits, int cells) asm(cells bits seconds workchain) "GETSTORAGEFEE";
@@ -67,7 +67,7 @@ If `storage_fee` is hardcoded, **remember to update it** during contract update
6767

6868
### Overview
6969

70-
In most cases use the `GETGASFEE` opcode with the following parameters:
70+
In most cases, use the `GETGASFEE` opcode with the following parameters:
7171

7272
| Param | Description |
7373
|:-----------|:--------------------------------------------------------|
@@ -160,7 +160,7 @@ send_gas_fee = printTxGasStats("Jetton transfer", transferTx);
160160

161161
The forward fee is taken for outgoing messages.
162162

163-
Generally, there are three cases of forward fee processing:
163+
There are three general cases for processing forward fees:
164164

165165
1. The message structure is deterministic and you can predict the fee.
166166
2. The message structure depends a lot on the incoming message structure.

0 commit comments

Comments
 (0)