Skip to content

Commit a8af3c8

Browse files
committed
Update based on Bri's suggestions
1 parent 845848c commit a8af3c8

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/tokens/README.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,13 +34,13 @@ All assets issued on the Stellar ledger (by a `G…` address) are **Classic Stel
3434
### How they work
3535

3636
- For protocol-level behavior and trustline semantics, see [Asset Design Considerations](./control-asset-access.mdx).
37-
- Implemented at the protocol level, the **Stellar Asset Contract (SAC)** provides a smart contract interface that enables Stellar assets to interoperate seamlessly with Soroban smart contracts.
38-
- Transfers between accounts and contracts using SAC result in the same underlying trustline debit/credit.
37+
- Implemented at the protocol level, the **Stellar Asset Contract (SAC)** provides a smart contract interface that enables Stellar assets to interoperate seamlessly with Stellar smart contracts.
38+
- Transfers between accounts and contracts using SAC resolve to the same trustline balance updates the Stellar protocol has always used.
3939

4040
### Strengths
4141

4242
- Has the benefits of native Stellar assets (fast, low cost), making these great for remittances and micropayments.
43-
- Can be used in Soroban contracts via SAC with a [SEP-41][sep-41] interface.
43+
- Can be used in Stellar smart contracts via SAC with a [SEP-41][sep-41] interface.
4444
- Maintains issuer controls and trustline semantics even when used from contracts.
4545
- Wide ecosystem wallet and indexer support. Classic assets are compatible with Stellar ecosystem products (such as Stellar wallets) and other ecosystem products (such as exchanges).
4646
- Benefit from [anchors](../learn/fundamentals/anchors.mdx), the bridges between the Stellar network and traditional financial systems. Explore the global [Stellar anchor directory](https://anchors.stellar.org/) for further details.

0 commit comments

Comments
 (0)