Commit 2b325f8d authored by Mark Rushakoff's avatar Mark Rushakoff Committed by Emmanuel Odeke

cmd/go: fix typo in "go help version" output

Change-Id: I38b22786aae3d7a08cf2863ef5d15e476fe30093
GitHub-Last-Rev: 57d07dd1c711029b965afd32e1d8a3c22560276f
GitHub-Pull-Request: golang/go#31711
Reviewed-on: https://go-review.googlesource.com/c/go/+/174086Reviewed-by: default avatarEmmanuel Odeke <emm.odeke@gmail.com>
parent 2177bfb3
...@@ -1373,7 +1373,7 @@ ...@@ -1373,7 +1373,7 @@
// during a directory scan. The -v flag causes it to report unrecognized files. // during a directory scan. The -v flag causes it to report unrecognized files.
// //
// The -m flag causes go version to print each executable's embedded // The -m flag causes go version to print each executable's embedded
// module version information, when available. In the output, the modul // module version information, when available. In the output, the module
// information consists of multiple lines following the version line, each // information consists of multiple lines following the version line, each
// indented by a leading tab character. // indented by a leading tab character.
// //
......
...@@ -34,7 +34,7 @@ By default, go version does not report unrecognized files found ...@@ -34,7 +34,7 @@ By default, go version does not report unrecognized files found
during a directory scan. The -v flag causes it to report unrecognized files. during a directory scan. The -v flag causes it to report unrecognized files.
The -m flag causes go version to print each executable's embedded The -m flag causes go version to print each executable's embedded
module version information, when available. In the output, the modul module version information, when available. In the output, the module
information consists of multiple lines following the version line, each information consists of multiple lines following the version line, each
indented by a leading tab character. indented by a leading tab character.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment