examples: wordsmith

README.md

@@ -95,7 +95,7 @@ If going with the week version then use ISO weeks as generated via `date +%g%V`
 ## Example: Go modules
 
 Per [https://go.dev/doc/modules/version-numbers](https://go.dev/doc/modules/version-numbers) Go tooling requires the use of semver.
-Furthermore Go MAJOR version bumps are disruptive because they require significant changes: v2+ versions must be in their own subdirectory, see [https://go.dev/blog/v2-go-modules](https://go.dev/blog/v2-go-modules) and [https://go.dev/doc/modules/release-workflow#breaking](https://go.dev/doc/modules/release-workflow#breaking).
+Furthermore MAJOR version bumps are disruptive because they require significant changes: v2+ versions must be in their own subdirectory, see [https://go.dev/blog/v2-go-modules](https://go.dev/blog/v2-go-modules) and [https://go.dev/doc/modules/release-workflow#breaking](https://go.dev/doc/modules/release-workflow#breaking).
 This is why a simple date based versioning scheme such as YY.MMDD.PATCH couldn't work for Go.
 But featver allows in-place evolution so a Go module could use v1 indefinitely.
 A featver Go module breaks Go module versioning commitments so tread carefully.