_content/ref: modules, correct statement on recording build metadata

Fixes golang/go#64652

Change-Id: Ie258e109053258e3bf214f75809ce9e26ede3636
Reviewed-on: https://go-review.googlesource.com/c/website/+/553156
Reviewed-by: Michael Matloob <matloob@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>

_content/ref/mod.md

@@ -116,8 +116,8 @@ compatible with previous versions.
   the corresponding release versions. For example, `v1.2.3-pre` comes before
   `v1.2.3`.
 * The build metadata suffix is ignored for the purpose of comparing versions.
-  Tags with build metadata are ignored in version control repositories, but
-  build metadata is preserved in versions specified in `go.mod` files. The
+  The go command accepts versions with build metadata and converts them to
+  pseudo-versions to maintain the total ordering between versions. The special
   suffix `+incompatible` denotes a version released before migrating to modules
   version major version 2 or later (see [Compatibility with non-module
   repositories](#non-module-compat)).