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

Commit 682e914

Browse files
Fix doc typos (#1137)
* Fix typos * Wrap lines
1 parent 1f9bbfd commit 682e914

File tree

2 files changed

+17
-3
lines changed

2 files changed

+17
-3
lines changed

docs/src/associated-token-account.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,22 @@ the user's wallet address to the associated token accounts they hold.
77

88
## Motivation
99

10-
- A user may own arbitarily many token accounts belonging to the same mint which makes it difficult for other users to know which account they should send tokens to and introduces friction into many other aspects of token management. This program introduces a way to _deterministically_ derive a token account key from a user's main System account address and a token mint address, allowing the user to create a main token account for each token he owns. We call these accounts _Associated Token Accounts_.
11-
- In addition, it allows a user to send tokens to another user even if the beneficiary does not yet have a token account for that mint. Unlike a system transfer, for a token transfer to succeed the recipient must have a token account with the compatible mint already, and somebody needs to fund that token account. If the recipient must fund it first, it makes things like airdrop campaigns difficult and just generally increases the friction of token transfers. AToken allows the sender to create the associated token account for the receiver, so the token transfer just works.
10+
- A user may own arbitrarily many token accounts belonging to the same mint
11+
which makes it difficult for other users to know which account they should send
12+
tokens to and introduces friction into many other aspects of token management.
13+
This program introduces a way to _deterministically_ derive a token account key
14+
from a user's main System account address and a token mint address, allowing the
15+
user to create a main token account for each token he owns. We call these
16+
accounts _Associated Token Accounts_.
17+
18+
- In addition, it allows a user to send tokens to another user even if the
19+
beneficiary does not yet have a token account for that mint. Unlike a system
20+
transfer, for a token transfer to succeed the recipient must have a token
21+
account with the compatible mint already, and somebody needs to fund that token
22+
account. If the recipient must fund it first, it makes things like airdrop
23+
campaigns difficult and just generally increases the friction of token
24+
transfers. AToken allows the sender to create the associated token account for
25+
the receiver, so the token transfer just works.
1226

1327
See the [SPL Token](token.md) program for more information about tokens in
1428
general.

docs/src/token.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -337,7 +337,7 @@ Creating 2/3 multisig 46ed77fd4WTN144q62BwjU2B3ogX3Xmmc8PT5Z3Xc2re
337337
Signature: 2FN4KXnczAz33SAxwsuevqrD1BvikP6LUhLie5Lz4ETt594X8R7yvMZzZW2zjmFLPsLQNHsRuhQeumExHbnUGC9A
338338
```
339339

340-
Next create the token mint and recieving accounts
340+
Next create the token mint and receiving accounts
341341
[as previously described](#example-creating-your-own-fungible-token)
342342
```
343343
$ spl-token create-token

0 commit comments

Comments
 (0)