fix(spellcheck): add missing project words so pnpm run lint passes - #661
Open
pucedoteth wants to merge 1 commit into
Open
fix(spellcheck): add missing project words so pnpm run lint passes#661pucedoteth wants to merge 1 commit into
pnpm run lint passes#661pucedoteth wants to merge 1 commit into
Conversation
`pnpm run lint` chains `spellcheck:lint`, but that gate currently fails on
`main` with 5 issues across 4 files:
src/pages/ink-builder-program/echo-program.mdx:20:27 - Unknown word (roadmaps)
src/pages/ink-builder-program/forge-program.mdx:6:88 - Unknown word (Inkworks)
src/pages/ink-builder-program/forge-program.mdx:150:119 - Unknown word (Inkworks)
src/pages/ink-builder-program/office-hours.mdx:49:17 - Unknown word (tokenomics)
src/pages/tools/rpc.mdx:78:83 - Unknown word (Matrixed)
None of these are typos, so the dictionary is the right place to fix them:
- `Inkworks` is the program that superseded Forge (ink.works)
- `Matrixed` is part of Matrixed.Link, the operator behind BoltRPC
- `roadmaps` and `tokenomics` are ordinary prose
The words drifted in unnoticed because the `spell-check` CI job in
`.github/workflows/cicd.yaml` is commented out, so nothing enforces the
dictionary on push -- only contributors who run the documented `pnpm run
lint` locally hit it, and it fails before their own changes are checked.
Appended to `cspell/project-words.txt` in the file's existing append order,
matching how `Uniblock` was added most recently.
After this change `pnpm run lint` exits 0 and cspell reports
"Files checked: 53, Issues found: 0 in 0 files".
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
pucedoteth
added a commit
to pucedoteth/docs-3
that referenced
this pull request
Aug 31, 2026
`AddNetworkButton` is parameterised by `network`, but its permalink anchor is
hardcoded:
<a href="#mainnet" id="mainnet" className="subheading-anchor" ... />
`general/connect-wallet.mdx` renders the component twice, once per network, so
both headings emit the same id. From the built page:
$ grep -o 'id="mainnet"' .next/server/pages/general/connect-wallet.html | wc -l
2
... Mainnet <a href="#mainnet" id="mainnet" class="subheading-anchor" ...
... Testnet (Sepolia) <a href="#mainnet" id="mainnet" class="subheading-anchor" ...
Three things follow. The document carries a duplicate id, which is invalid
HTML and makes `getElementById` and `:target` resolve to whichever comes
first. The permalink on "Testnet (Sepolia)" navigates to Mainnet, so the
control that exists to link to a section links to the wrong one. And the
testnet section has no anchor at all, so it cannot be linked to.
Derive both from the `network` prop. Mainnet keeps `#mainnet`, so any existing
link still resolves, and the testnet heading gets `#sepolia`.
After the change the built page has one of each, on the right heading:
... Mainnet <a href="#mainnet" id="mainnet" ...
... Testnet (Sepolia) <a href="#sepolia" id="sepolia" ...
`lint:js`, `lint:mdx` and `format:js:check` pass, and `pnpm run build`
succeeds. `spellcheck:lint` fails on main for unrelated reasons, covered in
inkonchain#661.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
kutluhaneth46
approved these changes
Sep 5, 2026
kutluhaneth46
left a comment
There was a problem hiding this comment.
Review
Straightforward cspell allowlist update so pnpm run lint / spellcheck stops failing on project vocabulary (roadmaps, Inkworks, tokenomics, Matrixed). No runtime impact.
LGTM.
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.
Problem
pnpm run lintfails onmain.The
lintscript chains four gates:The first three pass.
spellcheck:lintfails with 5 issues across 4 files:Because
lintis a&&chain andspellcheck:lintis last, a contributor who runs the documented lint command gets a red result caused entirely by pre-existing content, before any of their own work is evaluated.Why it went unnoticed
The
spell-checkjob in.github/workflows/cicd.yamlis commented out:js-lint,md-lint,formatandbuildall run in CI, so nothing else drifts. Spellcheck is the one gate with no CI enforcement, so new prose lands without the dictionary being updated alongside it, and the failures accumulate.Fix
None of the five flagged instances is a typo, so the dictionary is the correct place to resolve them rather than editing the prose:
Inkworksforge-program.mdxMatrixedroadmapsecho-program.mdxtokenomicsoffice-hours.mdxAdded to
cspell/project-words.txtin the file'"'"'s existing append order, matching howUniblockwas most recently added in #641.Verification
Before, on
main:After, on this branch:
All four gates (
lint:js,lint:mdx,format:js:check,spellcheck:lint) pass.Note
This only clears the backlog so the local gate is usable again. It does not re-enable the commented-out
spell-checkCI job — that looked like a deliberate call, and re-enabling it is your decision rather than something to slip into a content fix. Happy to send that as a follow-up if you would like it, now that the gate is green and it would pass.