Brad Fitzpatrick 5fea2ccc77 all: single space after period. ... The tree's pretty inconsistent about single space vs double space after a period in documentation. Make it consistently a single space, per earlier decisions. This means contributors won't be confused by misleading precedence. This CL doesn't use go/doc to parse. It only addresses // comments. It was generated with: $ perl -i -npe 's,^(\s*// .+[a-z]\.) +([A-Z]),$1 $2,' $(git grep -l -E '^\s*//(.+\.) +([A-Z])') $ go test go/doc -update Change-Id: Iccdb99c37c797ef1f804a94b22ba5ee4b500c4f7 Reviewed-on: https://go-review.googlesource.com/20022 Reviewed-by: Rob Pike <r@golang.org> Reviewed-by: Dave Day <djd@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>		2016-03-02 00:13:47 +00:00
..
testdata	go/parser, go/types: report invalid else branch in if statements	2015-12-07 21:36:31 +00:00
doc.go	gofmt/doc: gofmt -s output may not be backward compatible	2015-02-08 05:13:00 +00:00
gofmt_test.go	cmd/gofmt: make test files self-describing	2014-08-21 17:25:13 -07:00
gofmt.go	cmd/gofmt: Ignore file not found errors.	2016-02-19 00:13:18 +00:00
internal.go	all: single space after period.	2016-03-02 00:13:47 +00:00
long_test.go	go/format, cmd/gofmt: avoid dependency on internal package format	2015-09-30 16:32:47 +00:00
rewrite.go	all: single space after period.	2016-03-02 00:13:47 +00:00
simplify.go	gofmt: -s flag simplifies "for _ = range x"	2014-07-17 09:40:27 -07:00