_content/doc/go1.24: reword VCS version stamping note

I struggled to map the old ones to the behavior described in
golang/go#50603: a pseudo-version will be generated even if a VCS tag is
available, but is not the latest commit.

Also, a link to BuildInfo.Main feels useful.

For golang/go#68545

Change-Id: Id2642c94a18e22ac56439728f20f01bf87d14a70
Reviewed-on: https://go-review.googlesource.com/c/website/+/635598
Reviewed-by: Sam Thanawalla <[email protected]>
LUCI-TryBot-Result: Go LUCI <[email protected]>
Auto-Submit: Sam Thanawalla <[email protected]>
Auto-Submit: Filippo Valsorda <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
Reviewed-by: Michael Matloob <[email protected]>

Author: FiloSottile

_content/doc/go1.24.md

@@ -71,10 +71,10 @@ private module fetches. See `go help goauth` for more information.
 
 <!-- go.dev/issue/50603 -->
 
-The `go build` command now includes versioning information in the compiled binary.
-If a local VCS tag is available, the main module's version will be set from that tag.
-If no local VCS tag is available, a pseudo-version will be generated.
-A +dirty suffix will be appended if there are uncommitted VCS changes present.
+The `go build` command now sets the
+[main module's version](/pkg/runtime/debug#BuildInfo.Main) in the compiled
+binary based on the version control system tag and/or commit.
+A `+dirty` suffix will be appended if there are uncommitted changes.
 Use the `-buildvcs=false` flag to omit version control information from the binary.
 
 <!-- go.dev/issue/63939 -->