docs: link canonical Solana terms to terminology page on first mention#30
Merged
mikemaccana merged 1 commit intoMay 14, 2026
Conversation
What - Walked every README in the repo and added a markdown link to https://solana.com/docs/terminology for the first prose mention of each canonical Solana term: program, instruction, instruction handler, account, PDA, mint / mint account, token account, ATA, rent, lamport, CPI / cross-program invocation, Token Extensions, onchain, Anchor, Classic Token Program. Why - Readers new to Solana can click straight from any example into the canonical definition of unfamiliar terms without leaving the repo. Rules followed - First prose mention only; subsequent mentions stay plain. - Code blocks, inline code, headers, and pre-existing markdown links untouched. - Case-preserving link text ("Programs" stays "Programs", "PDA" stays "PDA"). - "instruction handler" and "mint account" link once; their constituents ("instruction", "mint") are linked at their next standalone prose mention. - "program" is not linked inside compound proper nouns like "System Program", "Token Program", or "Classic Token Program" (would read oddly mid-name). Anchor corrections vs the original spec - program-derived address → #program-derived-address-pda (spec said #program-derived-account) - mint account / mint → #token-mint (spec said #mint-account) - associated token account → #associated-token-account-ata (spec said #associated-token-account) - Token Extensions → #token-extensions-program (spec said #token-extensions) - Classic Token Program → #token-program (the Solana terminology page uses the older shorter name "Token Program"; same concept — this is the classic SPL token program, as opposed to Token Extensions which has its own anchor). Deliberately unlinked - "signer" and "offchain" have no corresponding anchor on the Solana terminology page (it has #signature but not #signer; #onchain but not #offchain). Left unlinked rather than pointed at wrong/approximate targets.
5db6805 to
086d812
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Walked every README in the repo and added a markdown link to https://solana.com/docs/terminology for the first prose mention of each canonical Solana term:
program,instruction,instruction handler,account,PDA,mint/mint account,token account,ATA,rent,lamport,CPI/cross-program invocation,Token Extensions,onchain,Anchor,Classic Token Program.Why
Readers new to Solana can click straight from any example into the canonical definition of unfamiliar terms without leaving the repo.
Rules followed
Anchor corrections vs the original spec
Fetched https://solana.com/docs/terminology and verified every
id=heading. The following corrections were applied vs the originally-supplied anchor list:#program-derived-account#program-derived-address-pda#mint-account#token-mint#associated-token-account#associated-token-account-ata#token-extensions#token-extensions-program#token-programThe Solana terminology page uses the older shorter name "Token Program" under the
#token-programanchor; the concept is the same — this is the classic SPL token program, as opposed to Token Extensions, which has its own#token-extensions-programanchor.Deliberately unlinked
signer— the terminology page has#signaturebut no#signeranchor.offchain— the terminology page has#onchain(which explicitly notes "Onchain (no hyphen) is the preferred spelling") but no standalone#offchainanchor.These terms were left unlinked rather than pointed at wrong or approximate targets. This is an omission on the Solana terminology page itself, not an oversight in this PR.
Stats
Classic Token Programlinks).