Skip to content

docs: fix duplicate anchor so Documentation TOC link resolves - #2720

Open
iacker wants to merge 1 commit into
NVIDIA:mainfrom
iacker:fix/contributing-doc-anchor
Open

docs: fix duplicate anchor so Documentation TOC link resolves#2720
iacker wants to merge 1 commit into
NVIDIA:mainfrom
iacker:fix/contributing-doc-anchor

Conversation

@iacker

@iacker iacker commented Aug 6, 2026

Copy link
Copy Markdown

What this PR does / why we need it:

The "Artifacts" table of contents in CONTRIBUTING.md links to [Documentation](#documentation), but the Documentation section reused the same anchor as the Source Code section directly above it:

### <a name="source-code"></a> Source Code
...
### <a name="source-code"></a> Documentation   <!-- duplicate anchor -->

Because the anchor was duplicated, the #documentation TOC entry did not resolve to its section. This renames the anchor to documentation so the TOC link points to the correct heading. The other three TOC anchors (source-code, container-images, helm-charts) already match their sections and are unchanged.

Which issue(s) this PR fixes:

N/A (trivial docs fix, no tracking issue)

Special notes for your reviewer:

Documentation-only, single-line change. Verified all five anchors in the file are now unique and that each of the four TOC links resolves to its section.

The Artifacts table of contents links to [Documentation](#documentation),
but the Documentation section reused the same <a name="source-code">
anchor as the Source Code section just above it. As a result the
Documentation TOC entry did not resolve to its section. Rename the
anchor to "documentation" to match the TOC link.

Signed-off-by: iacker <iacker@users.noreply.github.com>
@copy-pr-bot

copy-pr-bot Bot commented Aug 6, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant