Replace "IOTA tokens" -> "IOTA coins"

iotaledger · Oct 23, 2023 · 783f557 · 783f557
1 parent b55d6fd
commit 783f557
Showing 1 changed file with 9 additions and 8 deletions.
diff --git a/tips/TIP-0041/tip-0041.md b/tips/TIP-0041/tip-0041.md
@@ -17,23 +17,24 @@ replaces: TIP-18
 # Summary
 
 This document defines the Basic Output type and transaction validation rules for the IOTA protocol to support storage of
-IOTA tokens, native tokens and Mana as well as layer 2 smart contract requests, among other functionality. It was
+IOTA coins, native tokens and Mana as well as layer 2 smart contract requests, among other functionality. It was
 originally introduced in [TIP-18](../TIP-0018/tip-0018.md) and the functionality defined in this document is an
 extension of the Basic output of TIP-18.
 
 ## Summary of changes compared to TIP-18
 
 - Add `Mana` field.
-- Remove `Native Tokens` field and add `Native Token Feature` to the allowed features. See [TIP-38 (Native Token Migration)](../TIP-0038/tip-0038.md#native-token-migration) for migration details.
+- Remove `Native Tokens` field and add `Native Token Feature` to the allowed features. See
+ [TIP-38 (Native Token Migration)](../TIP-0038/tip-0038.md#native-token-migration) for migration details.
 
 # Motivation
 
-This TIP defines an output type for the support of basic ledger functionality. Such outputs can
-store IOTA tokens, native tokens and Mana. All unlock conditions and features defined in
-[TIP-38](../TIP-0038/tip-0038.md) are supported and can be composed to create spending restrictions, attach metadata or
-enable indexed data storage in the UTXO ledger. Layer 2 smart contract requests are enabled by posting requests through
-the Tangle. Such requests can be crafted by including commands in the metadata of Basic outputs. This output thus
-supports both the native tokenization on layer 1 as well as layer 2 smart contracts.
+This TIP defines an output type for the support of basic ledger functionality. Such outputs can store IOTA coins, native
+tokens and Mana. All unlock conditions and features defined in [TIP-38](../TIP-0038/tip-0038.md) are supported and can
+be composed to create spending restrictions, attach metadata or enable indexed data storage in the UTXO ledger. Layer 2
+smart contract requests are enabled by posting requests through the Tangle. Such requests can be crafted by including
+commands in the metadata of Basic outputs. This output thus supports both the native tokenization on layer 1 as well as
+layer 2 smart contracts.
 
 # Building Blocks