-The most common way to run these programs is as a subcommand of the go
-program,
-for instance as "go fmt". Run like this, the command operates on complete
-packages of Go source code, with the go program invoking the underlying binary
-with arguments appropriate to package-level processing.
+The most common way to run these programs is as a subcommand of the go program,
+for instance as go fmt. Run like this, the command operates on
+complete packages of Go source code, with the go program invoking the
+underlying binary with arguments appropriate to package-level processing.
The programs can also be run as stand-alone binaries, with unmodified arguments,
-using the go tool subcommand, such as "go tool vet".
-This style of invocation allows, for instance, checking a single source file rather than
-an entire package: "go tool vet myprogram.go" as compared to
-"go vet mypackage".
-Some of the commands, such as prof and yacc, are accessible
-only through the go tool subcommand.
+using the go tool subcommand, such as go tool vet.
+This style of invocation allows, for instance, checking a single source file
+rather than an entire package: go tool vet myprogram.go as
+compared to go vet mypackage.
+Some of the commands, such as yacc, are accessible only through
+the go tool subcommand.
-Finally, two of the commands, fmt and
-doc, are also installed as regular binaries called
-gofmt and godoc
+Finally, two of the commands, fmt and doc, are also
+installed as regular binaries called gofmt and godoc
because they are so often referenced.