Four links point readers to connecting-to-base#vibenet for Vibenet connection details, but that page has no #vibenet anchor. The Vibenet connection details live in the Vibenet tab under the ## Network details heading, and Mint tabs are not addressable by their own fragment, so the current links land on the page without reaching the intended section.
This repoints the four links to connecting-to-base#network-details, the real heading anchor for the section that contains the Vibenet tab.
Affected links:
base-chain/network-information/native-account-abstraction.mdx (inline link + Connect to vibenet card)
#network-details is the closest working anchor, since the target is a <Tab> and tabs cannot be deep-linked by fragment. These were the only links to connecting-to-base in the docs, and all four used the non-existent #vibenet fragment.
How has it been tested?
Confirmed connecting-to-base.mdx has no #vibenet anchor and that ## Network details (anchor #network-details) is the section containing the Vibenet tab. Verified no connecting-to-base#vibenet references remain.
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
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?
Four links point readers to connecting-to-base#vibenet for Vibenet connection details, but that page has no #vibenet anchor. The Vibenet connection details live in the Vibenet tab under the ## Network details heading, and Mint tabs are not addressable by their own fragment, so the current links land on the page without reaching the intended section.
This repoints the four links to connecting-to-base#network-details, the real heading anchor for the section that contains the Vibenet tab.
Affected links:
Notes to reviewers
#network-details is the closest working anchor, since the target is a <Tab> and tabs cannot be deep-linked by fragment. These were the only links to connecting-to-base in the docs, and all four used the non-existent #vibenet fragment.
How has it been tested?
Confirmed connecting-to-base.mdx has no #vibenet anchor and that ## Network details (anchor #network-details) is the section containing the Vibenet tab. Verified no connecting-to-base#vibenet references remain.