Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: typos #170

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/instructions/create-app-xnft.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ The uploading of the metadata JSON blob and associated files (bundle code, icons
- The master mint will mint a total supply of `1` to the master token account with the xNFT PDA being the authority of the mint
- The metadata account will be populated with the relevant values as providing in the instruction arguments and primary sale happened

!> Instead of creating a master edition and reliquishing freeze and mint authority, the freeze and mint authority of the master mint is given to the xNFT PDA. This accomplishes the same effect of ensuring a supply of `1` with programmatic signing requirements without surrendering the authority to an external program.
!> Instead of creating a master edition and relinquishing freeze and mint authority, the freeze and mint authority of the master mint is given to the xNFT PDA. This accomplishes the same effect of ensuring a supply of `1` with programmatic signing requirements without surrendering the authority to an external program.

## Accounts

Expand Down
2 changes: 1 addition & 1 deletion docs/instructions/grant-access.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

[Source Code](https://github.com/coral-xyz/xnft/blob/master/programs/xnft/src/instructions/grant_access.rs)

This instruction allows an install authority of a "private" xNFT to delegate asychronous access to specific wallets to create installations on their own, similar to creating OAuth keys for an entity to act within a permissioned system. Once created, that wallet cause use their `Access` program account with [`create_permissioned_install`](/instructions/create-permissioned-install.md) to install the "private" xNFT themselves.
This instruction allows an install authority of a "private" xNFT to delegate asynchronous access to specific wallets to create installations on their own, similar to creating OAuth keys for an entity to act within a permissioned system. Once created, that wallet cause use their `Access` program account with [`create_permissioned_install`](/instructions/create-permissioned-install.md) to install the "private" xNFT themselves.

## Additional Constraints

Expand Down
2 changes: 1 addition & 1 deletion docs/instructions/set-curator-verification.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Invoked by a curator account in order to verify or unverify their assignment to

This process is initiated by the authority of the xNFT through the [`set_curator`](/instructions/set-curator.md) instruction to set the _unverified_ curator public key in the xNFT program account data.

!> The association with a curator on an xNFT should only be respected if the `verified` subfield of the `CuratorStatus` xNFT account field is `true` and has protocol-enforced implications on xNFT updates as defined in the the [Update an xNFT](/instructions/update-xnft.md) section.
!> The association with a curator on an xNFT should only be respected if the `verified` subfield of the `CuratorStatus` xNFT account field is `true` and has protocol-enforced implications on xNFT updates as defined in the [Update an xNFT](/instructions/update-xnft.md) section.

## Additional Constraints

Expand Down
2 changes: 1 addition & 1 deletion docs/instructions/transfer.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

[Source Code](https://github.com/coral-xyz/xnft/blob/master/programs/xnft/src/instructions/transfer.rs)

Transfers the xNFT master token between authorities. The instruction manages the thrawing and refreezing of the source and destination token accounts respectively in order to maintain the frozen state of the master token.
Transfers the xNFT master token between authorities. The instruction manages the thawing and refreezing of the source and destination token accounts respectively in order to maintain the frozen state of the master token.

The current authority that is signing for the instruction will pay for the initialization of the recipient's new associated token account, but will be a net `0 SOL` transaction (minus the transaction processing fee) since their own associated token account will be closed at the end of the instruction.

Expand Down
2 changes: 1 addition & 1 deletion docs/instructions/update-xnft.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Allows the authority of an xNFT to update certain values on the xNFT program acc
| Master Token | ❌ | ❌ | The master token account of the xNFT to verify ownership |
| Master Metadata | ❌ | ✅ | The MPL master metadata account of the xNFT master mint |
| Curation Authority | ❌ | ❌ | The account that acts as the xNFT's update gatekeeping authority - either the owner or the curator if assigned and verified |
| Updater | ✅ | ❌ | The owner of the xNFT and it's master token |
| Updater | ✅ | ❌ | The owner of the xNFT and its master token |
| Token Metadata Program | ❌ | ❌ | --- |

## Arguments
Expand Down
Loading