Skip to content
This repository was archived by the owner on Jul 30, 2025. It is now read-only.

Commit 90de147

Browse files
nhandl3gregnazario
andauthored
Fix Resource docs' example: CoinStore, not Coin (#956)
CoinStore, not Coin Co-authored-by: Greg Nazario <[email protected]>
1 parent e4d649b commit 90de147

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

apps/nextra/pages/en/network/blockchain/resources.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ struct CustomCoinBox<phantom CoinType> has key {
3535

3636
## Define resources and objects
3737

38-
All instances and resources are defined within a module that is stored at an address. For example `0x1234::coin::Coin<0x1234::coin::SomeCoin>` would be represented as:
38+
All instances and resources are defined within a module that is stored at an address. For example `0x1234::coin::CoinStore<0x1234::coin::SomeCoin>` would be represented as:
3939

4040
```move
4141
module 0x1234::coin {
@@ -47,7 +47,7 @@ module 0x1234::coin {
4747
}
4848
```
4949

50-
In this example, `0x1234` is the address, `coin` is the module, `Coin` is a struct that can be stored as a resource, and `SomeCoin` is a struct that is unlikely to ever be represented as an instance. The use of the phantom type allows for there to exist many distinct types of `CoinStore` resources with different `CoinType` parameters.
50+
In this example, `0x1234` is the address, `coin` is the module, `CoinStore` is a struct that can be stored as a resource, and `SomeCoin` is a struct that is unlikely to ever be represented as an instance. The use of the phantom type allows for there to exist many distinct types of `CoinStore` resources with different `CoinType` parameters.
5151

5252
## Permissions of Instances including Resources
5353

0 commit comments

Comments
 (0)