Update value names in docs (#8983)

automerge
This commit is contained in:
Greg Fitzgerald 2020-03-20 10:22:02 -06:00 committed by GitHub
parent 5fa36bbab3
commit 8b0a7f6838
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 11 deletions

View File

@ -31,9 +31,9 @@ solana <COMMAND> --help
where you replace the text `<COMMAND>` with the name of the command you want
to learn more about.
The command's usage message will typically contain words such as `<NUMBER>`,
The command's usage message will typically contain words such as `<AMOUNT>`,
`<PUBKEY>` or `<KEYPAIR>`. Each word is a placeholder for the *type* of text
you can execute the command with. For example, you can replace `<NUMBER>`
you can execute the command with. For example, you can replace `<AMOUNT>`
with a number such as `42` or `100.42`. You can replace `<PUBKEY>` with the
base58 encoding of your public key. For `<KEYPAIR>`, it depends on what type
of wallet you chose. If you chose an fs wallet, that path might be
@ -50,16 +50,16 @@ Try and *airdrop* yourself some play tokens on the developer testnet, called
Devnet:
```bash
solana airdrop 10 <PUBKEY> --url http://devnet.solana.com
solana airdrop 10 <RECIPIENT_PUBKEY> --url http://devnet.solana.com
```
where you replace the text `<PUBKEY>` with your base58 public key.
where you replace the text `<RECIPIENT_PUBKEY>` with your base58 public key.
Confirm the airdrop was successful by checking the account's balance.
It should output `10 SOL`:
```bash
solana balance <PUBKEY> --url http://devnet.solana.com
solana balance <ACCOUNT_PUBKEY> --url http://devnet.solana.com
```
Next, prove that you own those tokens by transferring them. The Solana cluster
@ -83,16 +83,16 @@ pubkey: GKvqsuNcnwWqPzzuhLmGi4rzzh55FhJtGizkhHaEJqiV
```
```bash
solana transfer --keypair=<KEYPAIR> <PUBKEY> 5 --url http://devnet.solana.com
solana transfer --keypair=<SENDER_KEYPAIR> <RECIPIENT_PUBKEY> 5 --url http://devnet.solana.com
```
where you replace `<KEYPAIR>` with the path to a keypair in your wallet,
and replace `<PUBKEY>` with the output of `solana-keygen new` above.
where you replace `<SENDER_KEYPAIR>` with the path to a keypair in your wallet,
and replace `<RECIPIENT_PUBKEY>` with the output of `solana-keygen new` above.
Confirm the updated balances with `solana balance`:
```bash
solana balance <PUBKEY> --url http://devnet.solana.com
solana balance <ACCOUNT_PUBKEY> --url http://devnet.solana.com
```
where `<PUBKEY>` is either the public key from your keypair or the
@ -106,11 +106,11 @@ tokens to transfer. Once you have that collected, you can transfer tokens
with the `solana transfer` command:
```bash
solana transfer --keypair=<KEYPAIR> <PUBKEY> <NUMBER>
solana transfer --keypair=<SENDER_KEYPAIR> <RECIPIENT_PUBKEY> <AMOUNT>
```
Confirm the updated balances with `solana balance`:
```bash
solana balance <PUBKEY>
solana balance <ACCOUNT_PUBKEY>
```