Uh oh!
There was an error while loading. Please reload this page.
[DOCS] all: onchain and offchain as one word inside code comments - #80
Merged
Conversation
Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
|
haimbj1force-pushed
the
docs/onchain-offchain-in-code-comments
branch
from
September 3, 2026 17:40
f72d0b8 to
baae160Comparehaimbj1force-pushed
the
docs/onchain-offchain-in-code-comments
branch
from
September 3, 2026 17:42
baae160 to
cc00552CompareUh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
STYLE.md fixes
onchainandoffchainas one word, andstyles/Fhenix/Terms.ymlenforces it at error level. The site already agreed almost everywhere: 286 one-word against 19 hyphenated.Those 19 survived because they sit inside code comments and fence titles, and Vale does not lint code. This sweeps all of them. Zero hyphenated occurrences remain site-wide.
Commit 1 — 19 occurrences, 14 files. Comments, two fence titles, one test description. No runnable code changed.
Commit 2 —
fherc20/operators.mdxcarried 17 pre-existing decorative-Unicode errors that commit 1 pulled into CI, becausedocs-style.ymllints every file a PR touches. They are now words, per STYLE.md: "In tables, use words". The bullets simply drop their marks, since the sentence above each list already states the verdict. The comparison table spells the meaning out, so a reader no longer decodes a symbol to learn something the text repeats.Lint, Vale and the version check are clean on all 14 files.