docs: fix broken P256VERIFY anchor link in Fjord upgrade page - #1838
Open
devorun wants to merge 1 commit into
Open
docs: fix broken P256VERIFY anchor link in Fjord upgrade page#1838devorun wants to merge 1 commit into
devorun wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
Copy link
Copy Markdown
Collaborator
🟡 Heimdall Review Status
|
Sorry, something went wrong.
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
2 participants
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 changed? Why?
The Fjord upgrade page links to the P256VERIFY precompile section using an uppercase fragment:
Generated anchors are lowercased, so the heading ## P256VERIFY renders as #p256verify. Anchor matching is case-sensitive, so the current link does not scroll to the target section. This updates the fragment to #p256verify to match the generated anchor.
The other links in the same list on this page already use lowercase fragments (#fees, #l1-gas-usage-estimation), so this makes the P256VERIFY entry consistent with them.
Notes to reviewers
Single-character fragment change on one line (docs/base-chain/specs/upgrades/fjord/overview.mdx). The target heading ## P256VERIFY lives in docs/base-chain/specs/protocol/execution/evm/precompiles.mdx.
How has it been tested?
Verified the target heading exists and that its generated anchor is #p256verify, consistent with other cross-references in the docs that link to capitalized headings using lowercase fragments.