diff --git a/tips/TIP-0040/tip-0040.md b/tips/TIP-0040/tip-0040.md
index 7358f4615..60927c052 100644
--- a/tips/TIP-0040/tip-0040.md
+++ b/tips/TIP-0040/tip-0040.md
@@ -16,8 +16,8 @@ requires: TIP-19, TIP-20, TIP-21 and TIP-22
# Summary
Staking and delegation are mechanisms by which users contribute to the network's security and for which they are
-rewarded. Stakers lock IOTA tokens to become eligible to be selected for the validator committee and consequently give
-weight to blocks and transactions. On the other hand, delegators delegate IOTA tokens (which does not imply locking
+rewarded. Stakers lock IOTA coins to become eligible to be selected for the validator committee and consequently give
+weight to blocks and transactions. On the other hand, delegators delegate IOTA coins (which does not imply locking
these tokens) to a validator, forming a validator pool. The weight that validators give to blocks is derived from the
total stake of the pool (i.e., from the locked tokens of the staker and the delegated tokens of all its delegators) and
the total combined stake among pools. If the validator of a pool performs its task well, the pool is rewarded with Mana.
@@ -82,9 +82,9 @@ The IOTA protocol accepts blocks and transactions after they reach a certain wei
selected validator committee. The following gives a high-level idea of the selection process, while the rest of the
section specifies its normative details.
-Stakers, or interchangeably called _registered validators_, must lock their IOTA tokens to stake them. By locking the
+Stakers, or interchangeably called _registered validators_, must lock their IOTA coins to stake them. By locking the
tokens, the stakers prove control over them, so the protocol assigns them a proportional amount of _stake_ in exchange.
-Other users - the so-called delegators - can _delegate_ their IOTA tokens to a staker to further increase their
+Other users - the so-called delegators - can _delegate_ their IOTA coins to a staker to further increase their
influence in the system. A staker plus all its delegators are called a _staking or validator pool_. Stakers are eligible
to be selected into a committee for a certain duration. Only the votes of those selected into the committee are
considered to determine the _Witness Weight_, used for the acceptance of blocks, and _Approval Weight_, used for
@@ -101,7 +101,7 @@ were expected to issue. This factor determines the amount of _Mana rewards_ the
After an epoch ends, the delegators of the pool can claim their rewards. The validator may continue to stake or end its
stake by going through an unbonding period of its locked tokens. After this period ends, the validator can unlock their
-IOTA tokens and claim their Mana rewards.
+IOTA coins and claim their Mana rewards.
## Registration
@@ -143,7 +143,7 @@ taken:
- `Block Slot Index <= Activity Window Slot(n)`.
- For any validator `i` in the set of _registered validators_ the pool stake is equal to `Stake_i + DelegatedStake_i` at
the end of the slot with index `Registration Slot(n)`, where:
- - `Stake_i` is the `Staked Amount` of IOTA tokens of the validator's _Staking Feature_.
+ - `Stake_i` is the `Staked Amount` of IOTA coins of the validator's _Staking Feature_.
- `DelegatedStake_i` is the sum of all _Delegation Output's_ `Amount` field where the value of the `Validator ID`
field is equal to `i`.
- The set of _registered validators_ who are active constitute the set of _eligible validators_, which is sorted by pool
@@ -163,7 +163,7 @@ affects the validator pool's Mana rewards.
# Delegation
-By delegating IOTA tokens, a user increases a validator's stake proportionally to the number of tokens they delegate
+By delegating IOTA coins, a user increases a validator's stake proportionally to the number of tokens they delegate
without becoming a validator themselves. To delegate, a _Delegation Output_ must be created. The following section
specifies how delegation is implemented.
@@ -176,7 +176,7 @@ Upon the creation of a Delegation Output, the protocol assigns to it a unique id
Delegation Output
- Describes a Delegation Output, which delegates its contained IOTA tokens to a validator.
+ Describes a Delegation Output, which delegates its contained IOTA coins to a validator.
Pool Stake | uint64 |
- The total amount of IOTA tokens staked by the validator and all its delegators. | +The total amount of IOTA coins staked by the validator and all its delegators. |
Pool Rewards | @@ -526,11 +526,11 @@ The following section specifies how to convert the slot-level data into epoch-le #### Input values -- Let `Validator Stake(i)` be the amount of IOTA tokens staked by the validator with Account ID `i`, i.e. the +- Let `Validator Stake(i)` be the amount of IOTA coins staked by the validator with Account ID `i`, i.e. the `Staked Amount` in the _Staking Feature_ of the validator at the end of the registration slot. -- Let `Pool Stake` be the total amount of delegated and staked IOTA tokens by the validator pool which was determined at +- Let `Pool Stake` be the total amount of delegated and staked IOTA coins by the validator pool which was determined at the time of the pool stake calculation, i.e. the end of the registration slot. -- Let `Total Stake` be the sum of all `Pool Stake` values, that is, the total amount of delegated and staked IOTA tokens +- Let `Total Stake` be the sum of all `Pool Stake` values, that is, the total amount of delegated and staked IOTA coins in the selected committee. - Let `Total Validator Stake` be the sum of `Validator Stake(i)` for each validator `i` in the selected committee.