I had previously added 'go mod -sync' as a step for the 'Preparing a release' section. Given that, updated step #3 in 'Defining a module' section: rather than 'go mod -sync', say 'go build ./...', which seems more to be the norm (e.g., based on spot checking a couple recent rsc examples). Overall, this section could still be improved/clarified.
diff --git a/Modules.md b/Modules.md
index ed24d86..b9b3e14 100644
--- a/Modules.md
+++ b/Modules.md
@@ -103,13 +103,11 @@
$ go mod -init -module example.com/path/to/my/module/v2
```
-
-3. The `-sync` flag synchronizes the `go.mod` file with the source code in the module (filling in requirements for any missing or unconverted dependencies, and removing modules that are not needed to satisfy any imports):
+3. Build the module. This will automatically add missing or unconverted dependencies as needed to satisfy imports for this particular build invocation:
```
- $ go mod -sync
+ $ go build ./...
```
-
4. Test the module as configured to ensure that it works with the selected versions.
```
@@ -122,6 +120,8 @@
$ go test all
```
+Prior to tagging a release, see the [Preparing a release](https://github.com/golang/go/wiki/Modules#preparing-a-release) section below.
+
## Upgrading and Downgrading Dependencies
Day-to-day adding, removing, upgrading, and downgrading of dependencies should be done using 'go get', which will automatically update the `go.mod` file.
