docs: fix broken reference links

[amahi1568]

Description

This pull request addresses a single documentation-related issue by fixing a minor typo / improving clarity in the existing documentation.

There are no functional or behavioral code changes included in this PR.
The change is limited strictly to documentation and does not impact runtime behavior.

Checklist

• Your pull request should address just one issue, without pulling in other changes.
• Write unit tests that match behavioral changes (not applicable for documentation-only changes).
• Run mvn verify (not required for documentation-only changes).
• You have run the Core IT (not applicable).

License Declaration

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[slawekjaranowski]

on master branch it is ok, we should change it on maven-4.0.x branch to something like ref/4.0-LATEST
@gnodet, @cstamas what do you think?

is is used to publish site candidate during release
https://maven.apache.org/components/ref/

maybe we should also add redirects to:
https://github.com/apache/maven-site/blob/master/content/filtered-resources/.htaccess

@gnodet, @cstamas what do you think?

[gnodet]

Claude Code on behalf of Guillaume Nodet

This change would actually break the site path rather than fix it.

• ref/4-LATEST resolves correctly (HTTP 200): https://maven.apache.org/ref/4-LATEST/
• ref/4.0.0 returns HTTP 404: https://maven.apache.org/ref/4.0.0/

The master branch is currently developing 4.1.0-SNAPSHOT. The 4-LATEST path is intentionally used so the generated site always points to the latest 4.x reference docs, regardless of the specific release version. Hardcoding 4.0.0 here would be incorrect.

[gnodet]

This change should not be made. 4-LATEST is the correct value — it's an intentional alias that always resolves to the latest 4.x release docs on the Maven site.

You can verify:

• https://maven.apache.org/ref/4-LATEST/ → HTTP 200 ✓
• https://maven.apache.org/ref/4.0.0/ → HTTP 404 ✗

Additionally, master is currently on 4.1.0-SNAPSHOT, so hardcoding 4.0.0 would be doubly wrong.

[gnodet]

This change would break the site links — ref/4-LATEST resolves correctly (HTTP 200) while ref/4.0.0 returns 404. The 4-LATEST path is intentionally used so generated docs always point to the latest 4.x reference, regardless of release version.

Claude Code on behalf of Guillaume Nodet