//
// Init accepts one optional argument, the module path for the new module. If the
// module path argument is omitted, init will attempt to infer the module path
-// using import comments in .go files, vendoring tool configuration files (like
-// Gopkg.lock), and the current directory (if in GOPATH).
+// using import comments in .go files and the current directory (if in GOPATH).
//
// See https://golang.org/ref/mod#go-mod-init for more about 'go mod init'.
//
Init accepts one optional argument, the module path for the new module. If the
module path argument is omitted, init will attempt to infer the module path
-using import comments in .go files, vendoring tool configuration files (like
-Gopkg.lock), and the current directory (if in GOPATH).
+using import comments in .go files and the current directory (if in GOPATH).
See https://golang.org/ref/mod#go-mod-init for more about 'go mod init'.
`,
// introduced, if a path p resolves using the pre-module "go get" lookup
// to the root of a source code repository without a go.mod file,
// that repository is treated as if it had a go.mod in its root directory
-// declaring module path p. (The go.mod is further considered to
-// contain requirements corresponding to any legacy version
-// tracking format such as Gopkg.lock, vendor/vendor.conf, and so on.)
+// declaring module path p.
//
// The presentation so far ignores the fact that a source code repository
// has many different versions of a file tree, and those versions may